Add beholder.config.info metric #1769
Conversation
|
👋 kirqz23, thanks for creating this pull request! To help reviewers, please consider creating future PRs as drafts first. This allows you to self-review and make any final changes before notifying the team. Once you're ready, you can mark it as "Ready for review" to request feedback. Thanks! |
✅ API Diff Results - No breaking changes |
There was a problem hiding this comment.
Pull request overview
This PR adds a new beholder.config.info metric to track Beholder SDK configuration settings. The metric records configuration as attributes, making it easier to monitor which nodes are using specific features like log streaming.
Changes:
- Added
beholderConfigMetricfunction that creates an Int64Gauge metric to record Beholder configuration - Integrated the config metric recording during client initialization
- Exposed configuration settings for logging, message emitter, tracing, and metrics as metric attributes
💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.
Co-authored-by: Jordan Krage <jmank88@gmail.com>
There was a problem hiding this comment.
Pull request overview
Copilot reviewed 1 out of 1 changed files in this pull request and generated 1 comment.
💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.
4 participants
This introduces
beholder.config.infometric that aggregates beholder settings as attributes and allows to track app configurationThis feature especially will help us understand which nodes are using logs streaming. Currently both custom events and logs are processed through the same intrumentation and gRPC built-in metrics with LogExporter are not specific.