prometheus-community / prometheus-community/stackdriver_exporter

project_id is not working for stackdriver workspace with multiple attached projects.

Open
#117 3 comments 4 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Dominant language
Go
Stars
295
Forks
117
Avg merge
9d 14h
Merged PRs (30d)
7

Description

Hi !

first, thanks for your work !

We have an issue with project_id and workspace with multiple attached projects.

Here is our configuration

  • main project is fsociety-prod, we created stackdriver workspace from this project
  • secondary project is fsociety-preprod. When we create stackdriver workspace, we attached this project to previous workspace, instead of creating a new one.

Recently, we installed stackdriver-exporter.

When testing with project_id = fsociety-preprod, we collected metrics from fsociety-preprod project only. We were quite happy 👍

But when we deploy with project_id = fsociety-prod, we discovered that, with this conf, we collected all metrics from stackdriver workspace : metrics from two projects : fsociety-prod and fsociety-preprod.

How could we limit metrics from main project only ?

Thanks in advance !

Have a nice day

cc : @nlamirault

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start by reproducing the stackdriver-exporter configuration with a workspace containing fsociety-prod and fsociety-preprod, comparing project_id behavior for each value. Trace how project_id is applied to workspace metric collection; done means selecting fsociety-prod returns metrics from the main project only, without metrics from the attached project.

Written by the indexing model from the issue text.

Assessment

Tech stack
go, google-cloud, prometheus
Domain
cloud, observability
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
25/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.