I everyone, I have just published an article about this: https://www.influxdata.com/blog/influxdb-latest-tag-updated-in-docker-hub/
It offers a couple of ways forward if your deployment was unexpectedly upgrade to InfluxDB 2.0, either upgrading your data to work with it or rolling back to 1.8. It also explains what happened to cause this, and how to avoid it in the future.
Hi! I’d start with the docs here: https://docs.influxdata.com/chronograf/v1.9/introduction/getting-started/
And for Grafana, check out this guide: https://grafana.com/docs/grafana/latest/getting-started/getting-started-influxdb/
There’s a good slack community and forums linked to on the Influx docs - stop by and say hello if you need a hand!
This article may be helpful in your quest:
​
https://www.influxdata.com/blog/influxdbs-checks-and-notifications-system/
Influx ram usage scales with the cardinality of your data, unless you use the TSI storage engine
https://www.influxdata.com/blog/how-to-overcome-memory-usage-challenges-with-the-time-series-index/
Flux supports months. If you're on InfluxDB 1.7 or InfluxDB 2 - you can do this.
​
https://www.influxdata.com/blog/aggregating-by-months-or-years-in-flux/
Their docs are really good and they have a self pace "University" on their site that is full of good videos and posts. The videos are good to use to get a high level feel. https://www.influxdata.com/university/
Those are all free and then their stack is free and easy to start trying things on a Linux VM (also free).
Can you give me some more detail about your schema? If each temperature is in different measurements, you'll have to use Flux to do joins across measurements. Then you can do math across measurements. https://www.influxdata.com/blog/influxdb-how-to-do-joins-math-across-measurements/
You should be able to use flux on v1.7.6, That will allow you to do a join.
Here are some examples.
https://www.influxdata.com/blog/influxdb-how-to-do-joins-math-across-measurements/
TimeShift is possible with Chronograph:
https://www.influxdata.com/blog/release-announcement-chronograf-1-4-0-telegraf-1-5-1/
Basic arithmetic is available on timestamps:
https://docs.influxdata.com/influxdb/v1.7/query_language/data_exploration/#time-syntax
So you can do timestamp - time()
to calculate the difference.
You could SUM
those differences together.
Flux will make a lot of this easier, over time 😃
Is "rain_total" your measurement in this case? You have it listed as entity_id which I assumed is a tag. Generally the SELECT
statement within the CQ follows the below format:
SELECT <function[s]> INTO <destination_measurement> FROM <measurement> [WHERE <stuff>] GROUP BY time(<interval>)[,<tag_key[s]>]
Check out the documentation for more details. Alternatively, if you don't want to use CQs to downsample your data, you can also create a task in Kapacitor to handle that. This post talks more about using continuous queries or Kapacitor tasks.
Influxdb is a database. The "InfluxQL" query language superficially looks like SQL, but it is not. Do not assume that everything you know about SQL will apply; it will not, and there will be tears.
You need something else to send the data to the database. It could be a script you write, or an existing program. Telegraf is one such program. There's also a way to directly ingest CSV data into Influx, and can be found in the InfluxDB docs (I didn't know it could do this; learn something new every day).
Use Grafana to plot the data and make pretty pictures.