InfluxDB 2.x: Task: Aggregation: Unterschied zwischen den Versionen
Aus Wiki-WebPerfect
Admin (Diskussion | Beiträge) |
Admin (Diskussion | Beiträge) |
||
| Zeile 1: | Zeile 1: | ||
Sometimes you want to aggregate a heavy amount of data, for example for a Grafana graph panel, but the query is very slow because of the amount of metrics (Over millions). <br> | Sometimes you want to aggregate a heavy amount of data, for example for a Grafana graph panel, but the query is very slow because of the amount of metrics (Over millions). <br> | ||
Then it is more efficient to create an InfluxDB Task that aggregates the data and save the results back to an bucket instead of calculate the result each time the query runs. | Then it is more efficient to create an InfluxDB Task that aggregates the data and save the results back to an bucket instead of calculate the result each time the query runs. | ||
| + | |||
| + | This is an example of such an aggregation task. | ||
| + | What I want: | ||
| + | *Create a graph panel that shows the sum of all used storage we have over time. | ||
| + | *Because the storage is shared, each node in the same cluster collects the same storage information's -> That's why I have to dedup the data (unique()). | ||
Version vom 30. Juni 2021, 13:27 Uhr
Sometimes you want to aggregate a heavy amount of data, for example for a Grafana graph panel, but the query is very slow because of the amount of metrics (Over millions).
Then it is more efficient to create an InfluxDB Task that aggregates the data and save the results back to an bucket instead of calculate the result each time the query runs.
This is an example of such an aggregation task. What I want:
- Create a graph panel that shows the sum of all used storage we have over time.
- Because the storage is shared, each node in the same cluster collects the same storage information's -> That's why I have to dedup the data (unique()).
