InfluxDB - Writing Data with the HTTP API
来源:互联网 发布:python 字典迭代器 编辑:程序博客网 时间:2024/06/06 18:38
There are many ways to write data into InfluxDB including the command line interface, client libraries and plugins for common data formats such as Graphite. Here we’ll show you how to create a database and write data to it using the built-in HTTP API.
Creating a database using the HTTP API
To create a database send a POST
request to the /query
endpoint and set the URL parameter q
to CREATE DATABASE <new_database_name>
. The example below sends a request to InfluxDB running on localhost
and creates the database mydb
:
curl -i -XPOST http://localhost:8086/query --data-urlencode "q=CREATE DATABASE mydb"
Writing data using the HTTP API
The HTTP API is the primary means of writing data into InfluxDB, by sending POST
requests to the /write
endpoint. The example below writes a single point to the mydb
database. The data consist of the measurement cpu_load_short
, the tag keys host
and region
with the tag valuesserver01
and us-west
, the field key value
with a field value of 0.64
, and the timestamp 1434055562000000000
.
curl -i -XPOST 'http://localhost:8086/write?db=mydb' --data-binary 'cpu_load_short,host=server01,region=us-west value=0.64 1434055562000000000'
When writing points, you must specify an existing database in the db
query parameter. See the API Reference documentation for a complete list of the available query parameters.
The body of the POST - we call this the Line Protocol - contains the time-series data that you wish to store. They consist of a measurement, tags, fields, and a timestamp. InfluxDB requires a measurement name. Strictly speaking, tags are optional but most series include tags to differentiate data sources and to make querying both easy and efficient. Both tag keys and tag values are strings. Field keys are required and are always strings, and, by default, field values are floats. The timestamp - supplied at the end of the line in Unix time in nanoseconds since January 1, 1970 UTC - is optional. If you do not specify a timestamp InfluxDB uses the server’s local nanosecond timestamp in Unix epoch. Anything that has to do with time in InfluxDB is always UTC.
Writing multiple points
Post multiple points to multiple series at the same time by separating each point with a new line. Batching points in this manner results in much higher performance.
The following example writes three points to the database mydb
. The first point belongs to the series with the measurement cpu_load_short
and tag set host=server02
and has the server’s local timestamp. The second point belongs to the series with the measurement cpu_load_short
and tag set host=server02,region=us-west
and has the specified timestamp 1422568543702900257
. The third point has the same specified timestamp as the second point, but it is written to the series with the measurement cpu_load_short
and tag set direction=in,host=server01,region=us-west
.
curl -i -XPOST 'http://localhost:8086/write?db=mydb' --data-binary 'cpu_load_short,host=server02 value=0.67cpu_load_short,host=server02,region=us-west value=0.55 1422568543702900257cpu_load_short,direction=in,host=server01,region=us-west value=2.0 1422568543702900257'
Writing points from a file
Write points from a file by passing @filename
to curl
. The data in the file should follow InfluxDB’s line protocol syntax.
Example of a properly-formatted file (cpu_data.txt
):
cpu_load_short,host=server02 value=0.67cpu_load_short,host=server02,region=us-west value=0.55 1422568543702900257cpu_load_short,direction=in,host=server01,region=us-west value=2.0 1422568543702900257
Write the data in cpu_data.txt
to the mydb
database with:curl -i -XPOST 'http://localhost:8086/write?db=mydb' --data-binary @cpu_data.txt
Note: If your data file has more than 5,000 points, it may be necessary to split that file into several files in order to write your data in batches to InfluxDB. By default, the HTTP request times out after five seconds. InfluxDB will still attempt to write the points after that time out but there will be no confirmation that they were successfully written.
Schemaless Design
InfluxDB is a schemaless database. You can add new measurements, tags, and fields at any time. Note that if you attempt to write data with a different type than previously used (for example, writing a string to a field that previously accepted integers), InfluxDB will reject those data.
A note on REST…
InfluxDB uses HTTP solely as a convenient and widely supported data transfer protocol.
Modern web APIs have settled on REST because it addresses a common need. As the number of endpoints grows the need for an organizing system becomes pressing. REST is the industry agreed style for organizing large numbers of endpoints. This consistency is good for those developing and consuming the API: everyone involved knows what to expect.
REST, however, is a convention. InfluxDB makes do with three API endpoints. This simple, easy to understand system uses HTTP as a transfer method for InfluxQL. The InfluxDB API makes no attempt to be RESTful.
HTTP response summary
- 2xx: If your write request received
HTTP 204 No Content
, it was a success! If it’sHTTP 200 OK
, InfluxDB understood the request but couldn’t complete it. The body of the response will contain additional error information. - 4xx: InfluxDB could not understand the request.
- 5xx: The system is overloaded or significantly impaired.
Examples of error responses:
- Writing a float to a field that previously accepted booleans:
curl -i -XPOST 'http://localhost:8086/write?db=hamlet' --data-binary 'tobeornottobe booleanonly=true' curl -i -XPOST 'http://localhost:8086/write?db=hamlet' --data-binary 'tobeornottobe booleanonly=5'
returns:
HTTP/1.1 400 Bad Request[...]write failed: field type conflict: input field "booleanonly" on measurement "tobeornottobe" is type float64, already exists as type boolean
- Writing a point to a database that doesn’t exist:
curl -i -XPOST 'http://localhost:8086/write?db=atlantis' --data-binary 'liters value=10'
returns:
HTTP/1.1 404 Not Found[...]database not found: "atlantis"
Next steps
Now that you know how to write data with the built-in HTTP API discover how to query them with the Querying Data guide!
- InfluxDB - Writing Data with the HTTP API
- [PHP] Http API with JSON data
- 通过HTTP API 向InfluxDB传入数据
- Writing MySQL Scripts with Python DB-API
- Writing MySQL Scripts with Python DB-API
- Writing MySQL Scripts with Python DB-API
- Excel writing and reading with pure c API
- Using Google Visualization API with own data soure(转http://www.jansipke.nl/using-google-visualization-api-with-own-data-source)
- Reading Data with the SqlDataReader
- Writing Stored Procedures with Microsoft SQL Server: The Authoritative Solution
- [转]Writing Installs With The Windows Installer Is A Pain!
- The Tracking HTTP API
- 配置 influxDB 鉴权及 HTTP API 写数据的方法
- Editing with the geodatabase API
- opentsdb Writing Data
- Integration with the XML Data Type
- The differentiation program with abstract data
- The Data Scientist Guide with Links
- hdu5922
- js jquery 生成二维码 jquery.qrcode.js,并在中间添加logo图片
- Hibernate框架基础——映射集合属性
- mysql 添加外键约束报错 1452
- 创建第二个 vlan network "vlan101" - 每天5分钟玩转 OpenStack(96)
- InfluxDB - Writing Data with the HTTP API
- hdu5925Coconuts
- Retrofit使用教程(一)- Retrofit入门详解
- 路过—马上就赚钱的学习工具
- HDU1166 用树状数组重做以前线段树做的单点更新
- 1090. Highest Price in Supply Chain
- 一种芯片测试装置
- 你好,世界!
- Minimum’s Revenge(弱校联盟十一专场)