fix(dashboard): align Grafana panel queries with OTel metric names - #103
Merged
Conversation
docs/dashboard.json queried metric names from an older export scheme and
rendered no data. Update every panel expr, template variable, and the
default ${prefix} to match current OpenTelemetry -> Prometheus output:
- prefix default stroppy_k6_tpcc_ -> stroppy_ (scenario is now a label)
- label filter service.name -> job (otelcol mapping)
- counters tx_count/run_query_count -> _total suffix
- duration histograms _bucket -> _milliseconds_bucket
- data_received/data_sent -> _bytes_total
- rate metrics X.total -> X_total
- load-phase insert-rate panels filter event="progress" to track the
live cumulative counter, not the flat final-value series
Refs #87.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
What
docs/dashboard.jsonrendered no data — its panel queries referenced metric names from an older export scheme. Updates every panel expr, template variable, and the default${prefix}to match what stroppy actually emits through OpenTelemetry -> Prometheus.Closes #87.
Why the dashboard was empty
${prefix}=stroppy_k6_tpcc_stroppy_(scenario is now a label, not in the name)service.name=~"$job"job="stroppy"(otelcol mapsservice.name->job)tx_count(counter)tx_count_totalrun_query_count(counter)run_query_count_total..._duration_bucket..._duration_milliseconds_bucketdata_received/data_sentdata_received_bytes_total/data_sent_bytes_total{__name__="${prefix}X.total", condition="nonzero"}X_total+condition="nonzero"labelVerification
Spun up a local stack (postgres + otelcol + VictoriaMetrics + Grafana) and ran real loads through it:
Every panel returns real numbers after the rename. The load-phase "Insert rows/s" panels additionally filter
event="progress"so they track the live cumulative row counter instead of the flatcompleted/confirmedfinal-value series (which would otherwise dilute the rate to ~0).Notes
_total,_milliseconds_bucket,_bytes_total) are applied by the OTel -> Prometheus translation (otelcolprometheusremotewrite), not by stroppy directly — stroppy registers the base names (tx_count,run_query_duration, ...). The dashboard must speak the post-translation names.condition="nonzero"rate-metric encoding (tx_error_rate,insert_error_rate) is preserved; only the.total->_totalname form changed.