InfluxDB - Revision history

Leo: /* Pushing network counters to InfluxDB using curl */

2023-12-11T17:27:46Z

Pushing network counters to InfluxDB using curl

← Older revision		Revision as of 17:27, 11 December 2023
Line 332:		Line 332:
	cat /proc/net/dev {{!}} tail -n+3 {{!}} tr -d : \		cat /proc/net/dev {{!}} tail -n+3 {{!}} tr -d : \
	{{!}} while read interface rx_bytes rx_packets rx_errors rx_drops foo foo foo foo tx_bytes tx_packets tx_errors tx_drops foo ; do		{{!}} while read interface rx_bytes rx_packets rx_errors rx_drops foo foo foo foo tx_bytes tx_packets tx_errors tx_drops foo ; do
	echo "net,host=$HOSTNAME,interface=$interface bytes_recv=${rx_bytes}i,packets_recv=${rx_packets}i,bytes_sent=${tx_bytes}i,packets_sent=${tx_packets}i"		echo "net,host=$HOSTNAME,interface=$interface bytes_recv=${rx_bytes}i,packets_recv=${rx_packets}i,drop_in=${rx_drops}i,err_in=${rx_errors}i,bytes_sent=${tx_bytes}i,packets_sent=${tx_packets}i,drop_out=${tx_drops}i,err_out=${tx_errors}i"
	done {{!}} curl_to_influx		done {{!}} curl_to_influx
	\| lang = terminal		\| lang = terminal

Leo: /* Pushing network counters to InfluxDB using curl */

2023-12-03T21:49:02Z

Pushing network counters to InfluxDB using curl

← Older revision		Revision as of 21:49, 3 December 2023
Line 331:		Line 331:

	cat /proc/net/dev {{!}} tail -n+3 {{!}} tr -d : \		cat /proc/net/dev {{!}} tail -n+3 {{!}} tr -d : \
	\| while read interface rx_bytes rx_packets rx_errors rx_drops foo foo foo foo tx_bytes tx_packets tx_errors tx_drops foo ; do		{{!}} while read interface rx_bytes rx_packets rx_errors rx_drops foo foo foo foo tx_bytes tx_packets tx_errors tx_drops foo ; do
	echo "net,host=$HOSTNAME,interface=$interface bytes_recv=${rx_bytes}i,packets_recv=${rx_packets}i,bytes_sent=${tx_bytes}i,packets_sent=${tx_packets}i"		echo "net,host=$HOSTNAME,interface=$interface bytes_recv=${rx_bytes}i,packets_recv=${rx_packets}i,bytes_sent=${tx_bytes}i,packets_sent=${tx_packets}i"
	done {{!}} curl_to_influx		done {{!}} curl_to_influx

Leo at 21:48, 3 December 2023

2023-12-03T21:48:36Z

@@ Line 310: / Line 310: @@
 To give a series an appropriate name, use <code>set</code> or <code>map</code> to assign an appropriate name to a field. For example, I could add   <code>|> set(key: "name", value: "1 to 5 hours")</code>. This adds a new field to the data which we can tell Grafana to use as the series' name. In Grafana, apply a transformation under 'Labels to fields' and assign your custom field as the label for the series. In my example, set 'name' as the field to use.
-{{Navbox Linux}}
+=== Pushing network counters to InfluxDB using curl ===
 [[Category:Linux]]
 [[Category:LinuxUtilities]]

Leo: /* Tasks */

2023-11-17T01:36:11Z

Tasks

← Older revision		Revision as of 01:36, 17 November 2023
Line 207:		Line 207:

	==Tasks==		==Tasks==

			=== Recovering access tokens ===
			If you have access to the InfluxDB web interface but have lost the API access key, you can recover the access keys by:

			# Log in to the web interface
			# Generate a new 'all access' API key. This will be used temporarily. Copy it.
			# Log in to the InfluxDB server or enter the InfluxDB container and then run: {{Highlight
			\| code = # influx auth list -t $newly-generated-token
			\| lang = terminal
			}}

			You should be able to see all the tokens that have been generated including the secret.

			Once you're done, you can delete the newly generated API key.

	===Importing data from one bucket to another===		===Importing data from one bucket to another===
Line 226:		Line 240:

	=== Deleting data between a time range ===		=== Deleting data between a time range ===
	Use <code>influx delete</code> to delete data. You can specify the range you want to delete as well as the predicate to limit what measurement gets deleted.		Use <code>influx delete</code> to delete data. You can specify the range you want to delete as well as the predicate to limit what measurement gets deleted. The following will delete everything from the swap measurement between July 10, 2023 till the current time.
	{{Highlight		{{Highlight
	\| code = # influx delete \		\| code = # influx delete \
	--org ~~RCS~~ \		--org $OrganizationName \
	-t token \		-t $token$ \
	--bucket "arc-telegraf-longtermtesttest" \		--bucket "arc-telegraf-longtermtesttest" \
	--start '2023-07-10T00:00:00Z' \		--start '2023-07-10T00:00:00Z' \

Leo at 16:26, 12 September 2023

2023-09-12T16:26:19Z

← Older revision		Revision as of 16:26, 12 September 2023
Line 152:		Line 152:
	\|-		\|-
	\|Pivot data		\|Pivot data
	\|Pivoting can be used to make values into columns. This is useful if you have 2 measurement values (eg. CPU used and CPU available) which you want ~~to turn into fields in order~~ to do math on.		\|Pivoting can be used to make multiple values into columns. This is useful if you have 2 or more measurement values (eg. CPU used and CPU available) which you want to do math on into another field.
	<code>\|> pivot(rowKey: ["_time"], columnKey: ["_field"], valueColumn: "_value")</code>		<code>\|> pivot(rowKey: ["_time"], columnKey: ["_field"], valueColumn: "_value")</code>
	\|-		\|-
Line 177:		Line 177:
	\| lang = text		\| lang = text
	}}		}}
			\|-
			\|Histogram
			\|Creates a cumulative histogram. You must specify the bins manually:
			<code>\|> histogram(bins: [0.0, 0.016666667, 0.25, 0.5, 1.0, 3.0, 6.0, 12.0, 24.0, 48.0, 99999.0])</code>
			To change this into a non-cumulative histogram (such as if you're trying to graph Flux data on Grafana), you can pass the histogram data through <code>difference()</code>.
	\|}		\|}

Leo at 17:40, 19 July 2023

2023-07-19T17:40:53Z

← Older revision		Revision as of 17:40, 19 July 2023
Line 210:		Line 210:
	<nowiki>\|</nowiki>> to(bucket: "collectd/autogen")		<nowiki>\|</nowiki>> to(bucket: "collectd/autogen")
	\| lang = text		\| lang = text
	}}However, I ran into this error: input field "free" on measurement "disk" is type integer, already exists as type float dropped. As a workaround, I made a filter which converted values to floats for this particular measurement:		}}However, I ran into this error: <code>input field "free" on measurement "disk" is type integer, already exists as type float dropped</code>. As a workaround, I made a filter which converted values to floats for this particular measurement:
	{{Highlight		{{Highlight
	\| code = from(bucket: "telegraf/autogen")		\| code = from(bucket: "telegraf/autogen")
Line 217:		Line 217:
	<nowiki>\|</nowiki>> map(fn:(r) => ({ r with x: float(v: r.x) }))		<nowiki>\|</nowiki>> map(fn:(r) => ({ r with x: float(v: r.x) }))
	<nowiki>\|</nowiki>> to(bucket: "collectd/autogen")		<nowiki>\|</nowiki>> to(bucket: "collectd/autogen")
			\| lang = terminal
			}}

			=== Deleting data between a time range ===
			Use <code>influx delete</code> to delete data. You can specify the range you want to delete as well as the predicate to limit what measurement gets deleted.
			{{Highlight
			\| code = # influx delete \
			--org RCS \
			-t token \
			--bucket "arc-telegraf-longtermtesttest" \
			--start '2023-07-10T00:00:00Z' \
			--stop $(date +"%Y-%m-%dT%H:%M:%SZ") \
			--predicate '_measurement="swap"'
	\| lang = terminal		\| lang = terminal
	}}		}}

Leo at 20:33, 10 July 2023

2023-07-10T20:33:22Z

@@ Line 217: / Line 217: @@
    <nowiki>|</nowiki>> map(fn:(r) => ({ r with x: float(v: r.x) }))
    <nowiki>|</nowiki>> to(bucket: "collectd/autogen")
 | lang = terminal
 }}

Leo at 18:29, 21 April 2023

2023-04-21T18:29:29Z

@@ Line 188: / Line 188: @@
    <nowiki>|</nowiki>> keep(columns: ["_value"])
    <nowiki>|</nowiki>> group()
 | lang = text
 }}

Leo at 17:38, 22 November 2022

2022-11-22T17:38:27Z

← Older revision		Revision as of 17:38, 22 November 2022
Line 41:		Line 41:
	}}		}}
	Once the migration is complete, you can remove the INIT environment variables and the old influxdb volume.		Once the migration is complete, you can remove the INIT environment variables and the old influxdb volume.

			=== Continuous queries to tasks ===
			If you use continuous queries to down-sample older data, you will have to covert these into tasks using Flux.

			See: https://docs.influxdata.com/influxdb/v2.0/upgrade/v1-to-v2/migrate-cqs/

	== Flux ==		== Flux ==

Leo: /* Cheat sheet */

2022-09-29T17:46:51Z

Cheat sheet

← Older revision		Revision as of 17:46, 29 September 2022
Line 127:		Line 127:
	}}		}}
	\|-		\|-
	\|~~Display~~ data		\|Yielding data
	\|Use <code>yield()</code> to ~~return~~ the data. If you ~~need to rename~~ the ~~value~~, ~~use something like <~~code>yield(name: "~~mean~~")~~</code>~~.		\|Use <code>yield()</code> to yield the data. This is a fancy way of labeling the data you have so far in the pipe so that you can reference it later on. For simple queries using a single pipe, this likely isn't very useful. It will still name the resulting table output, however.{{Highlight
	~~'''TODO''': Uhh~~... ~~Can I verify this? It doesn't seem to really have an effect~~.		\| code = ... get data ...
			\|> min()
			\|> yield(name: "min")

			... get data ...
			\|> max()
			\|> yield(name: "max")
			\| lang = terminal
			}}
	\|-		\|-
	\|Windowing data		\|Windowing data