InfluxDB 1.x - Revision history

Leo at 21:03, 1 August 2021

2021-08-01T21:03:51Z

← Older revision		Revision as of 21:03, 1 August 2021
Line 1:		Line 1:
	InfluxDB ~~is a time series database written in Go~~.		The contents on this page is specific to InfluxDB 1.x. For information on 2.x, see the main [[InfluxDB]] article.

	==Using the InfluxDB command line==		==Using the InfluxDB command line==
Line 10:		Line 10:
	> show databases}}		> show databases}}

	=== Cheat Sheet ===		===Cheat Sheet===
	{\| class="wikitable"		{\| class="wikitable"
	!Action		!Action
Line 199:		Line 199:
	This type of query is great when generating dashboard variables in Grafana.		This type of query is great when generating dashboard variables in Grafana.

	~~<br />~~		==Writing data==

	== Writing data ==
	The schema of a InfluxDB database is based on the very first initial data types added. Adding additional data with a different type will be rejected.		The schema of a InfluxDB database is based on the very first initial data types added. Adding additional data with a different type will be rejected.

Line 207:		Line 205:
	*https://www.influxdata.com/blog/how-to-send-sensor-data-to-influxdb-from-an-arduino-uno/		*https://www.influxdata.com/blog/how-to-send-sensor-data-to-influxdb-from-an-arduino-uno/

	===With Curl===		===With Curl using the line protocol===
	Using {{code\|curl}}, you can POST values to a particular database using the line protocol. For more information, see https://docs.influxdata.com/influxdb/v0.9/write_protocols/line/		Using {{code\|curl}}, you can POST values to a particular database using the line protocol. For more information, see https://docs.influxdata.com/influxdb/v0.9/write_protocols/line/
	{{highlight\|lang=terminal\|code=		{{highlight\|lang=terminal\|code=

Leo: Leo moved page InfluxDB to InfluxDB 1.x without leaving a redirect: Most of the content here are specific to InfluxDB 1.x with 2.x being completely different

2021-08-01T21:01:24Z

Leo moved page InfluxDB to InfluxDB 1.x without leaving a redirect: Most of the content here are specific to InfluxDB 1.x with 2.x being completely different

← Older revision		Revision as of 21:01, 1 August 2021
(No difference)

Leo at 23:12, 13 November 2020

2020-11-13T23:12:53Z

@@ Line 1: / Line 1: @@
 InfluxDB is a time series database written in Go.
-==Writing data==
+==Using the InfluxDB command line==
-The schema of a InfluxDB database is based on the very first initial data types added. Adding additional data with a different type will be rejected.
+Get started with the InfluxDB command line. If using a docker container, you can connect to localhost without credentials on the default port. You can execute queries either by entering it to the influx shell or by piping it to <code>influx</code>.{{highlight|lang=terminal|code=
+# echo "show databases" {{!}} influx -host localhost
 # influx -host localhost
 Connected to http://localhost:8086 version 1.7.10
 InfluxDB shell version: 1.7.10
->}}
+> show databases}}
 {| class="wikitable"
 !Action
@@ Line 88: / Line 51: @@
 |Copy data to another measurement/database
 |<code>select * INTO newdb.autogen.cpu FROM olddb.autogen.cpu WHERE host = 'arc' GROUP BY *</code>
 |}
@@ Line 128: / Line 97: @@
 }}
-===Downsampling Data===
+===Down-sampling Data===
 See: https://docs.influxdata.com/influxdb/v1.8/guides/downsample_and_retain/
-You need to have a separate measurement for the downsampled data. Use a continuous query (CQ) to push data from the non-downsampled measurement into the downsampled measurement.
+You need to have a separate measurement for the down sampled data. Use a continuous query (CQ) to push data from the non-down sampled measurement into the down sampled measurement.
 Eg:
@@ Line 230: / Line 199: @@
 This type of query is great when generating dashboard variables in Grafana.
 ==Migrating from Prometheus==
 There is a go utility called <code>prom2influx</code> (https://github.com/zhyon404/prom2influx). More information documented at: https://docs.tibco.com/pub/ftl/5.4.0/doc/html/GUID-BAE2C630-90B2-47FC-A7D6-97AB16065A0C.html

Leo at 22:59, 13 November 2020

2020-11-13T22:59:28Z

← Older revision		Revision as of 22:59, 13 November 2020
Line 25:		Line 25:
	==Backing up data==		==Backing up data==

	===~~With Curl~~===		=== Influxd ===
	~~You can select all the data into a JSON format using Curl~~:		With Influxd, to backup:
	{{Highlight		{{Highlight
			\| code = # influxd backup -portable -database telegraftwo /tmp/backup
			\| lang = terminal
			}}
			To restore, copy the generated files to the host you want to restore to and run:
			{{Highlight
			\| code = # influxd restore -portable -database telegraftwo /tmp/backup
			\| lang = terminal
			}}

			=== Curl ===
			There is no easy way to restore the JSON output that's generated using this method. However, it's in a readable format for other purposes.{{Highlight
	\| code = $ curl "http://influxdb/query?db=slurm-metrics&" --data-urlencode "q=SELECT * FROM $series;" > series		\| code = $ curl "http://influxdb/query?db=slurm-metrics&" --data-urlencode "q=SELECT * FROM $series;" > series
	\| lang = terminal		\| lang = terminal
	}}~~<br />~~		}}
	==Using the InfluxDB command line==		==Using the InfluxDB command line==
	Get started with the InfluxDB command line. If using a docker container, you can connect to localhost without credentials on the default port:{{highlight\|lang=terminal\|code=		Get started with the InfluxDB command line. If using a docker container, you can connect to localhost without credentials on the default port:{{highlight\|lang=terminal\|code=
Line 76:		Line 87:
	\|-		\|-
	\|Copy data to another measurement/database		\|Copy data to another measurement/database
	\|<code>select * INTO newdb.autogen.cpu FROM olddb.autogen.cpu WHERE host = 'arc' GROUP BY *</code>		\|<code>select * INTO newdb.autogen.cpu FROM olddb.autogen.cpu WHERE host = 'arc' GROUP BY *</code>
	\|}		\|}

Line 107:		Line 118:
	Deleting a series will not drop any fields even if the field no longer has any values. See the next section on dropping a field.		Deleting a series will not drop any fields even if the field no longer has any values. See the next section on dropping a field.

	=== Copy measurements to another database ===		===Copy measurements to another database===
	You can copy a measurement to another database by using the <code>SELECT * INTO</code> type query. This might be desirable if you wish to make a backup of the data for only a specific set of measurements based on a tag. For example, to copy data from the source database <code>olddb</code> to the destination database <code>newdb</code>, but only for measurements where the tag <code>host</code> is <code>arc</code>:		You can copy a measurement to another database by using the <code>SELECT * INTO</code> type query. This might be desirable if you wish to make a backup of the data for only a specific set of measurements based on a tag. For example, to copy data from the source database <code>olddb</code> to the destination database <code>newdb</code>, but only for measurements where the tag <code>host</code> is <code>arc</code>:
	{{Highlight		{{Highlight
Line 117:		Line 128:
	}}		}}

	=== Downsampling Data ===		===Downsampling Data===
	See: https://docs.influxdata.com/influxdb/v1.8/guides/downsample_and_retain/		See: https://docs.influxdata.com/influxdb/v1.8/guides/downsample_and_retain/

Leo: /* Downsampling Data */

2020-11-13T21:51:11Z

Downsampling Data

← Older revision		Revision as of 21:51, 13 November 2020
Line 124:		Line 124:
	Eg:		Eg:
	{{Highlight		{{Highlight
	\| code = CREATE CONTINUOUS QUERY "30m_telegraf_cpu" ON telegraf		\| code =
			CREATE RETENTION POLICY "longterm" ON telegraf DURATION 1825d REPLICATION 1

			CREATE CONTINUOUS QUERY "30m_telegraf_cpu" ON telegraf
	BEGIN		BEGIN
	SELECT		SELECT

Leo at 21:50, 13 November 2020

2020-11-13T21:50:55Z

@@ Line 25: / Line 25: @@
 ==Backing up data==
-=== With Curl ===
+===With Curl===
 You can select all the data into a JSON format using Curl:
 {{Highlight
@@ Line 74: / Line 74: @@
 |Show all tags
 |<code>show tag keys from "$measurement"</code>
 |}
@@ Line 103: / Line 106: @@
 Deleting a series will not drop any fields even if the field no longer has any values. See the next section on dropping a field.
 ===Drop a Field===

Leo at 03:23, 9 November 2020

2020-11-09T03:23:43Z

← Older revision		Revision as of 03:23, 9 November 2020
Line 1:		Line 1:
	InfluxDB is a time series database written in Go.		InfluxDB is a time series database written in Go.

	==Writing ~~Data~~==		==Writing data==
	The schema of a InfluxDB database is based on the very first initial data types added. Adding additional data with a different type will be rejected.		The schema of a InfluxDB database is based on the very first initial data types added. Adding additional data with a different type will be rejected.

Line 7:		Line 7:
	*https://www.influxdata.com/blog/how-to-send-sensor-data-to-influxdb-from-an-arduino-uno/		*https://www.influxdata.com/blog/how-to-send-sensor-data-to-influxdb-from-an-arduino-uno/

	===Curl===		===With Curl===
	Using {{code\|curl}}, you can POST values to a particular database using the line protocol. For more information, see https://docs.influxdata.com/influxdb/v0.9/write_protocols/line/		Using {{code\|curl}}, you can POST values to a particular database using the line protocol. For more information, see https://docs.influxdata.com/influxdb/v0.9/write_protocols/line/
	{{highlight\|lang=terminal\|code=		{{highlight\|lang=terminal\|code=
Line 23:		Line 23:
	}}		}}

	==Backing ~~Up Data~~==		==Backing up data==
	With Curl~~, run~~:
			=== With Curl ===
			You can select all the data into a JSON format using Curl:
	{{Highlight		{{Highlight
	\| code = $ curl "http://influxdb/query?db=slurm-metrics&" --data-urlencode "q=SELECT * FROM $series;" > series		\| code = $ curl "http://influxdb/query?db=slurm-metrics&" --data-urlencode "q=SELECT * FROM $series;" > series
	\| lang = terminal		\| lang = terminal
	}}		}}<br />
			==Using the InfluxDB command line==
	== Using the InfluxDB command line ==
	Get started with the InfluxDB command line. If using a docker container, you can connect to localhost without credentials on the default port:{{highlight\|lang=terminal\|code=		Get started with the InfluxDB command line. If using a docker container, you can connect to localhost without credentials on the default port:{{highlight\|lang=terminal\|code=
	# influx -host localhost		# influx -host localhost

Leo at 03:21, 9 November 2020

2020-11-09T03:21:34Z

@@ Line 30: / Line 30: @@
 }}
-==Deleting Measurement==
+== Using the InfluxDB command line ==
 To delete an entire measurement, you must enter the influx command line, set the database and then run {{code|DROP MEASUREMENT}}. You cannot do this from Chronograf.
@@ Line 44: / Line 89: @@
 >}}
-==Delete a Series==
+===Delete a Series===
 To delete a specific series based on tag values, use the {{code|DELETE FROM }} query from the influx command line.
@@ Line 58: / Line 103: @@
 Deleting a series will not drop any fields even if the field no longer has any values. See the next section on dropping a field.
-==Drop a Field==
+===Drop a Field===
 There is no capability to drop a field in InfluxDB. There is a feature request for it at https://github.com/influxdata/influxdb/issues/6150.
@@ Line 100: / Line 145: @@
 Because you are re-copying the data again, this might not be a good solution for extremely large measurements.
-==Show unique tag values==
+===Show unique tag values===
 To show all tag values that are in a measurement (such as the 'jobs' measurement in the example below), use the <code>SHOW TAG VALUES</code> query. More information can be found from the [https://docs.influxdata.com/influxdb/v1.8/query_language/explore-schema/#show-tag-values InfluxDB documentation].

Leo at 00:55, 30 October 2020

2020-10-30T00:55:16Z

← Older revision		Revision as of 00:55, 30 October 2020
Line 155:		Line 155:
	}}		}}

	=== Dealing with ~~duplicate records and~~ sum aggregate ===		===Dealing with non-periodic measurements with the sum aggregate===
	~~Use~~ a ~~nested query~~ to ~~select~~ the ~~last~~ sum.		For certain measurements, a sum aggregate needs to be used. However, this requires measurements to occur on a specific time interval or else the summed measurement would be incorrect. In a sense, what we really need is to sum the measurements on a small time interval and then average the results.

	Eg:		This can be accomplished using nested queries. One of the metrics I wanted to graph which was logged every 24 hours used:{{Highlight
	{{Highlight		\| code = SELECT avg("x") FROM
	\| code = SELECT ~~last~~("x") FROM
	(SELECT sum("usage") as x FROM "storage_usage" WHERE "partition" = 'work' AND $timeFilter GROUP BY time(1h) )		(SELECT sum("usage") as x FROM "storage_usage" WHERE "partition" = 'work' AND $timeFilter GROUP BY time(1h) )
	GROUP BY time($__interval) fill(null)		GROUP BY time($__interval) fill(null)
	\| lang = text		\| lang = text
	}}{{Navbox Linux}}		}}Measurements taken more frequently than 24 hours but less frequent than 1 hour won't cause the result to be incorrect.{{Navbox Linux}}
	[[Category:Linux]]		[[Category:Linux]]
	[[Category:LinuxUtilities]]		[[Category:LinuxUtilities]]

Leo at 19:21, 29 October 2020

2020-10-29T19:21:51Z

← Older revision		Revision as of 19:21, 29 October 2020
Line 155:		Line 155:
	}}		}}

	{{Navbox Linux}}		=== Dealing with duplicate records and sum aggregate ===
			Use a nested query to select the last sum.

			Eg:
			{{Highlight
			\| code = SELECT last("x") FROM
			(SELECT sum("usage") as x FROM "storage_usage" WHERE "partition" = 'work' AND $timeFilter GROUP BY time(1h) )
			GROUP BY time($__interval) fill(null)
			\| lang = text
			}}{{Navbox Linux}}
	[[Category:Linux]]		[[Category:Linux]]
	[[Category:LinuxUtilities]]		[[Category:LinuxUtilities]]