prometheus-community / prometheus-community/stackdriver_exporter
stackdriver_consumed_api_serviceruntime_googleapis_com_api_request_count doesn't seem like a counter
Nobody has claimed this yet.
- Dominant language
- Go
- Stars
- 295
- Forks
- 117
- Avg merge
- 9d 14h
- Merged PRs (30d)
- 7
Description
Using the same query in gcp and grafana shows different results. In Grafana, this metric seems like it isn't a counter like in gcp, so rate doesn't show the same values as in gcp.
stackdriver_consumed_api_serviceruntime_googleapis_com_api_request_count{service="compute.googleapis.com",response_code="404"}
in grafana shows horizontal line while
serviceruntime_googleapis_com:api_request_count{monitored_resource="consumed_api",response_code="404",service="compute.googleapis.com"}
in gcp shows increasing values like a counter
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 tracing how the Stackdriver metric serviceruntime.googleapis.com:api_request_count is exported as stackdriver_consumed_api_serviceruntime_googleapis_com_api_request_count. Compare the exporter’s result with the GCP and Grafana queries shown; done means the exported metric has counter behavior and rate produces consistent values.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- gcp, go, prometheus
- Domain
- cloud, observability
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100