elastic / elastic/beats

Introduce a trace/debug mode for Prometheus input

Open
#45,165 3 comments 0 reactions 0 assignees View on GitHub
enhancement prometheus Stalled Team:obs-ds-hosted-services
Dominant language
Go
Stars
12.7k
Forks
5k
Avg merge
2d 15m
Merged PRs (30d)
385

Description

**Describe the enhancement:**

It would be interesting to have a tracing/debug mode for the Prometheus module for all the 3 modes

**Describe a specific use case for the enhancement or feature:**

Can help trobuleshoting issues with Prometheus. It should be an applicative tracing mode to be exposed and log in debug on demand (not just a debug log, or it would pollute the logs).

Contributor guide

Open the contributing guide

Research direction

Start by locating the Prometheus input implementation and identifying its three modes. Review how on-demand debug logging is exposed, then determine how an applicative trace can be enabled without polluting normal logs. Done means all three modes provide the requested troubleshooting trace through a clearly defined on-demand mechanism.

Written by the indexing model from the issue text.

Assessment

Tech stack
go, prometheus
Domain
observability
Issue type
Feature
Difficulty
4/5
Estimated time
3-5 days
Activity status
Quiet
Clarity
Needs clarification
Newbie friendliness
45/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.