prometheus-community / prometheus-community/stackdriver_exporter
(0.14.1) https_total_latencies_bucket value discrepancy between Grafana and GCP
Nobody has claimed this yet.
- Dominant language
- Go
- Stars
- 295
- Forks
- 117
- Avg merge
- 9d 14h
- Merged PRs (30d)
- 7
Description
Hello, recently we noticed that values exported by the exporter and the ones in GCP don't match, the metric labels (including bucket lengths) match but the values themselves don't, even when identical queries are used within GCP.
Visually the graphs sometimes match (even with wrong values exported) when there are spikes but the data itself still isn't correct.
Query used in Grafana:
histogram_quantile(0.99,sum by (le)(increase(stackdriver_https_lb_rule_loadbalancing_googleapis_com_https_total_latencies_bucket{target_proxy_name=~"**REDACTED**"}[1m])))
Query used in GCP:
histogram_quantile(0.99,sum by **(le)(increase(loadbalancing_googleapis_com:https_total_latencies_bucket{target_proxy_name=~"REDACTED"}[1m])))
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reproducing the discrepancy with the Grafana and GCP queries included in the issue, then trace the exporter path for https_total_latencies_bucket values. Compare exported bucket values with the corresponding GCP results and document or fix the conversion point so identical queries produce matching data.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- gcp, go
- Domain
- cloud, observability
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100