prometheus / prometheus/docs

Prometheus.yml to make it dynamic.

Open
#3,003 1 comment 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Dominant language
TypeScript
Stars
717
Forks
1.2k
Avg merge
3d 15h
Merged PRs (30d)
19

Description

Hi everyone, can anyone help me with making prometheus.yml dynamic so that Prometheus automatically picks only the components/services that are currently present on the server or cluster?

Is there any way to achieve this dynamically instead of manually adding targets in prometheus.yml every time? Any suggestions or best practices would be helpful.

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 with prometheus.yml and review the existing documentation for dynamic target or service discovery. Determine whether the requested behavior needs new guidance or clarification; done means documenting a clear, supported approach for discovering current server or cluster components instead of manually adding targets.

Written by the indexing model from the issue text.

Assessment

Tech stack
prometheus
Domain
devops, documentation
Issue type
Documentation
Difficulty
5/5
Estimated time
Over a week
Activity status
Quiet
Clarity
Needs clarification
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.