prometheus-community / prometheus-community/stackdriver_exporter

continuously poll new projects based on filters

Open
#318 0 comments 0 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

Problem Statement
We have GCP projects that are created dynamically and need to be discovered by the stackdriver exporter,
but currently that aren't, since the exporter fetches the projects only at startup.utilize.

Desired State
The stackdriver exporter fetches the projects it needs to scrape (google.projects.filter arg) on some configurable interval,
that's way we can auto discover new projects and scrape their metrics.

Solution Proposal

  • Utilize mutex and keep the prometheus registry & project list in order to register/unregister projects in a separate subroutine.
  • Create a continuous update for GCP projects using the filters,
  • The update mechanism can and should be editable to both disable the behavior as well as increasing/decreasing the time between polls

we already created a working POC,
which just needs a bit more polishing

@SuperQ
please let me know what do you think so we can start working on it.

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 at the startup path where the exporter fetches projects and review the existing working POC mentioned in the issue. Define how filtered projects are polled and registered or unregistered, with configurable polling and a disabled mode; done means newly created matching projects are discovered and scraped without restarting.

Written by the indexing model from the issue text.

Assessment

Tech stack
go, google-cloud, prometheus
Domain
cloud, observability-sre
Issue type
Feature
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.