prometheus-community / prometheus-community/stackdriver_exporter
Stackdriver can overlap different logs-based metrics
Nobody has claimed this yet.
- Dominant language
- Go
- Stars
- 295
- Forks
- 117
- Avg merge
- 9d 14h
- Merged PRs (30d)
- 7
Description
We had two logs-based metrics named ingestion-run-time and ingestionRunTime with different types and descriptions. The stackdriver exporter metrics endpoint was returning a 500 error saying that the help text didn't get what is was expecting to find. I believe the stackdriver exporter was trying to map those two different log-based metrics onto the same prometheus metric name.
We have since renamed our metrics to not overlap, but it would help if the error handling was better. There was no mention of the issue in the container logs. The error was only displayed on the /metrics endpoint.
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 at the exporter metrics endpoint and reproduce the failure with two logs-based metrics whose names differ only by case, such as ingestion-run-time and ingestionRunTime. Trace how their names, types, and descriptions become Prometheus metrics; done means the endpoint no longer returns an opaque 500 and the failure is visible in container logs.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go, google-cloud
- Domain
- observability
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100