prometheus-community / prometheus-community/stackdriver_exporter
(0.14.1) https_request_count data does not match the data on GCP
Nobody has claimed this yet.
- Dominant language
- Go
- Stars
- 295
- Forks
- 117
- Avg merge
- 9d 14h
- Merged PRs (30d)
- 7
Description
Hello, today we've noticed that the data that is exported by this exporter doesn't match up with what GCP monitoring shows even if the queries are identical between both environments.
The metric in question is stackdriver_https_lb_rule_loadbalancing_googleapis_com_https_request_count and in Grafana the total value shows to be about 60% less than that is shown in GCP.
The discrepancy is (logically) more noticeable in resources that have a lot more requests going through them.
The full query used in both environments is:
sum by(response_code_class) (stackdriver_https_lb_rule_loadbalancing_googleapis_com_https_request_count{target_proxy_name="_REDACTED_"})
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 with the exporter’s handling of stackdriver_https_lb_rule_loadbalancing_googleapis_com_https_request_count and reproduce the reported query in both GCP Monitoring and Grafana. Trace how the exporter retrieves and aggregates this metric, then compare the response-code-class totals with GCP. Done means the exported totals match GCP for high-volume resources.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- gcp, go, prometheus
- Domain
- cloud, observability-sre
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100