{"id":46679,"date":"2021-12-16T00:00:00","date_gmt":"2021-12-16T08:00:00","guid":{"rendered":"https:\/\/griddb-linux-hte8hndjf8cka8ht.westus-01.azurewebsites.net\/blog\/using-griddb-cloud-version-1-2\/"},"modified":"2025-11-13T12:55:44","modified_gmt":"2025-11-13T20:55:44","slug":"using-griddb-cloud-version-1-2","status":"publish","type":"post","link":"https:\/\/www.griddb.net\/en\/blog\/using-griddb-cloud-version-1-2\/","title":{"rendered":"Using GridDB Cloud Version 1.2"},"content":{"rendered":"

This article will serve as a continuation of our previous blog featuring the new GridDB Cloud service; you can read about the basics of the Cloud service in our first blog: An Introduction to GridDB Cloud<\/a>. With the introduction out of the way, we will focus on new features brought upon us by version 1.2 of the Cloud service.<\/p>\n

With the release of the new version of GridDB, there is now an available GridDB Web API<\/a> baked right into the GridDB Cloud; you can learn the basics of using the WebAPI here<\/a>. The main benefits of the Web API are that you can use HTTP Requests to create containers and to push data directly into your database. This opens up using other services like Telegraf<\/a> to record metrics and other data into your GridDB database.<\/p>\n

In this article, we will showcase some simple Web API commands using curl<\/code>. And then we will show you how to install and use Telegraf with your Cloud service.<\/p>\n

GridDB Web API With Cloud<\/h2>\n

Using Web API is very straightforward. When you sign up for your GridDB Cloud Service, you are given your unique URL to the dashboard itself, and then another URL to the specific Web API Endpoint which you will use as your base to build your HTTP Requests.<\/p>\n

Creating GridDB User<\/h3>\n

To start, first create a new GridDB User<\/code>. This user and password will be used when making your HTTP Web API Requests. For this example, we will use User: test & Password: test.<\/p>\n

\"\"<\/a><\/p>\n

\"\"<\/a><\/p>\n

Creating A Container<\/h3>\n

And now let’s create our first Request. To start, let’s create a container called point01<\/code>.<\/p>\n

The Request will need to set the content type to application\/json; charset=UTF-8<\/code> and have a Basic Authorization header with your username and password encoded to base64. This is what a Request using curl would look like, for example:<\/p>\n

\n
curl --location --request POST 'https:\/\/cloud1.griddb.com\/trial002\/griddb\/v2\/gs_clustertrial002\/dbs\/public\/containers' \n--header 'Authorization: Basic dGVzdDp0ZXN0Cg==' \n--header 'Content-Type: application\/json; charset=UTF-8' \n--data '{\n    \"container_name\": \"point01\",\n    \"container_type\": \"TIME_SERIES\",\n    \"rowkey\": true,\n    \"columns\": [\n        {\n            \"name\": \"timestamp\",\n            \"type\": \"TIMESTAMP\"\n        },\n        {\n            \"name\": \"active\",\n            \"type\": \"BOOL\"\n        },\n        {\n            \"name\": \"voltage\",\n            \"type\": \"DOUBLE\"\n        }\n    ]\n}'<\/code><\/pre>\n<\/div>\n
So, first we use your given GridDB Cloud Web API URL as our endpoint. We build out the Endpoint using this “formula”: \/<clusterName<\/dbs\/public\/containers<\/p>\n
As for the Authorization line, we simply encode our username and password into base64 as a single entity like so: test:test<\/code>.<\/p>\n
The data column is simply a json<\/code> of the schema of the container we would like to create. In this case, we are creating a TIME_SERIES container called point01 with 3 columns. Once sent, you should received back a HTTP Response Code of 201 (Created).<\/p>\n
Registering a Row<\/h3>\n
To register a row, we again use a simple formula to build out our endpoint: \/dbs\/public\/containers\/\/rows. Let’s send some data to our newly formed container (and please note we are using the HTTP Request for PUT<\/code>, not POST<\/code>):<\/containername><\/baseurl><\/p>\n
\n
curl --location --request PUT 'https:\/\/cloud1.griddb.com\/trial002\/griddb\/v2\/gs_clustertrial002\/dbs\/public\/containers\/point03\/rows' --header 'Authorization: Basic dGVzdDp0ZXN0Cg==' --header 'Content-Type: application\/json;charset=UTF-8' -d '[[\"2021-06-28T10:30:00.000Z\", false, \"100\"]]''<\/code><\/pre>\n<\/div>\n
This will add some generic values to your GridDB Cloud point03<\/code> container.<\/p>\n
Obtaining A Row<\/h3>\n
To Obtain a row, we use the same Endpoint as registering a row, except instead of a PUT, we use POST. We will also send with our Request a different body.<\/p>\n
And to change things up, if you are not comfortable with using curl (or a command line), you can also simply use the VS Code<\/code> REST Client extension<\/a>. Here’s what a Request looks like using VS Code to obtain a row of data:<\/p>\n
\n
POST https:\/\/cloud1.griddb.com\/trial002\/griddb\/v2\/gs_clustertrial002\/dbs\/public\/containers\/point03\/rows HTTP\/1.1\nHost: cloud1.griddb.com\nAuthorization: Basic dGVzdDp0ZXN0Cg==\nContent-Type: application\/json\nContent-Length: 93\n \n{\n  \"limit\"  : 100,\n  \"condition\" : \"timestamp >= TIMESTAMP('2021-06-28T04:30:00.000Z')\"\n}<\/code><\/pre>\n<\/div>\n
And of course, if you would like an even easier method for making HTTP Requests, you can also use Postman<\/a><\/p>\n
Those are the basics of using the Web API with GridDB Cloud. Next, let’s try using InfluxDB and Telegraf<\/p>\n
Telegraf<\/h2>\n
Telegraf is an “open source server agent to help you collect metrics from your stacks, sensors and systems”. To put simply, we will be using the newly released GridDB Output plugin for Telegraf, in conjunction with the GridDB Web API, to send data to our GridDB Cloud using HTTP.<\/p>\n
First, let’s install all of the necessary requirements.<\/p>\n
Installation<\/h3>\n
The requirements for this are:<\/p>\n