![Streaming aggregation: Why?
- name: 5m-cpu-metrics
interval: 5m
aggregations:
- match: "node_cpu_.*"
aggregate_on_labels: ["instance_id"]
aggregate_outputs: ["min", "max", "avg"]
- name: 30m-cpu-metrics
interval: 30m
aggregations:
- match: "node_cpu_.*"
aggregate_on_labels: ["instance_id"]
aggregate_outputs: ["min", "max", "avg"]
-retentionFilter='{__name__=~"5m-.*"}:10d'
-retentionFilter='{__name__=~"30m-.*"}:90d'
vmagent:
VictoriaMetrics:](https://image.slidesharecdn.com/victoriametricsroadmap2023-221216141318-7a9e353f/75/VictoriaMetrics-2023-Roadmap-11-2048.jpg)
Uploaded byVictoriaMetrics
VictoriaMetrics 2023 Roadmap
The document outlines the 2023 roadmap for VictoriaMetrics, highlighting the development of a Grafana datasource plugin and the introduction of OpenTelemetry ingestion protocol support. It discusses various features like streaming aggregation and a vmalert UI for rules management, emphasizing the benefits of these additions, including improved metrics aggregation and user-friendly interfaces. The document also poses questions regarding the stakeholders involved in these developments.
More Related Content
VictoriaMetrics 2023 Roadmap
- 1.
- 2.
- 3.
- 4.
- 5.
- 6. OpenTelemetry ingestion protocolsupport VictoriaMetrics/pull/2570
- 7.
- 8.
- 9.
- 10. Streaming aggregation: Why? ●Metrics aggregation on the edge ● Resource usage isolation ● Per-client configuration instead of global ● Smart "downsampling" ● More flexibility with retentionFilter
- 11. Streaming aggregation: Why? -name: 5m-cpu-metrics interval: 5m aggregations: - match: "node_cpu_.*" aggregate_on_labels: ["instance_id"] aggregate_outputs: ["min", "max", "avg"] - name: 30m-cpu-metrics interval: 30m aggregations: - match: "node_cpu_.*" aggregate_on_labels: ["instance_id"] aggregate_outputs: ["min", "max", "avg"] -retentionFilter='{__name__=~"5m-.*"}:10d' -retentionFilter='{__name__=~"30m-.*"}:90d' vmagent: VictoriaMetrics:
- 12. Streaming aggregation: Who? Wehaven't decided yet :-)
- 13. vmalert: UI forrules management
- 14. vmalert: UI forrules management: Why? ● People get used to UI management ● UI provides additional features: ○ Testing rules before submitting ○ Templating validation and preview ○ Change history ● Grafana alerting?
- 15. vmalert: UI forrules management: Who?
- 16.
- 17.
- 18.
- 19.
- 20. vmui explore tab:Why? ● Simplify metrics exploration ● Look for anomalies and correlations during incidents
- 21.
- 22.
- 23.
- 24.
- 25. The map isnot the territory!
- 26.