You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
We have replaced Graphite with VictoriaMetrics, and now some Graphs in our Dashboards no longer display correct values.
For example, the following Graphite query: aliasByNode(consolidateBy(scaleToSeconds(nonNegativeDerivative(stats.gauges.$instance.enterprise-app.ingest.intake.time.count), 60), 'sum'), 2) is producing all 0 data points.
Running something similar in MetricsQL produces a graph like this:
that is more likely expected.
We've checked the compatibility of the CarbonAPI functions and assume all should work.
To Reproduce
VictoriaMetrics is part of our installation (running as a container in a K8S cluster); the app uses GraphiteReporter to push metrics to VM. Unfortunately, this setup isn't easy to reproduce.
But here are the command line options we use to start the container:
--retentionPeriod=1
--storageDataPath=/opt/victoria-metrics
--envflag.enable=true
--envflag.prefix=VM_
--graphiteListenAddr=0.0.0.0:2003
--loggerFormat=json
It turned out that Storage-Step header on the Grafana datasource had to be aligned with our metrics system (the documented 10s weren't sufficient in our case)
Describe the bug
We have replaced Graphite with VictoriaMetrics, and now some Graphs in our Dashboards no longer display correct values.
For example, the following Graphite query:
aliasByNode(consolidateBy(scaleToSeconds(nonNegativeDerivative(stats.gauges.$instance.enterprise-app.ingest.intake.time.count), 60), 'sum'), 2)
is producing all 0 data points.Running something similar in MetricsQL produces a graph like this:
that is more likely expected.
We've checked the compatibility of the CarbonAPI functions and assume all should work.
To Reproduce
VictoriaMetrics is part of our installation (running as a container in a K8S cluster); the app uses GraphiteReporter to push metrics to VM. Unfortunately, this setup isn't easy to reproduce.
But here are the command line options we use to start the container:
--retentionPeriod=1
--storageDataPath=/opt/victoria-metrics
--envflag.enable=true
--envflag.prefix=VM_
--graphiteListenAddr=0.0.0.0:2003
--loggerFormat=json
Version
victoria-metrics-20240301-013626-tags-v1.99.0-0-g9cd4b0537
Logs
nothing related in the logs
Screenshots
No response
Used command-line flags
No response
Additional information
No response
The text was updated successfully, but these errors were encountered: