prometheus-community / prometheus-community/stackdriver_exporter
Error during metric collection with 2 instances of a GAE service running
Nobody has claimed this yet.
- Dominant language
- Go
- Stars
- 295
- Forks
- 117
- Avg merge
- 9d 14h
- Merged PRs (30d)
- 7
Description
Collecting this metric (stackdriver_gae_app_appengine_googleapis_com_system_memory_usage) works fine as long as there is only 1 instance of the GAE service running. As soon as we scale to 2 instances running, StackDriver_Exporter begins to fail and throws the following error when accessing metrics at the /metrics url. I have changed the module_id and project_id to generic values before creating this post.
An error has occurred during metrics collection:
collected metric stackdriver_gae_app_appengine_googleapis_com_system_memory_usage
label:<name:"module_id" value:"service-name" >
label:<name:"project_id" value:"project-name" >
label:<name:"unit" value:"By" >
label:<name:"version_id" value:"v0-39-0" > gauge:<value:9.87049984e+08 >
was collected before with the same name and label values
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 failure at the /metrics endpoint with two instances of the GAE service and the stackdriver_gae_app_appengine_googleapis_com_system_memory_usage metric. Trace why the same metric and label values are collected twice; done means metric collection succeeds without the duplicate-collection error when both instances are running.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go, google-cloud
- Domain
- cloud, observability
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100