[LMI-0001] Add Component-Based Metrics & Dynamic Label Support #1
+101
−71
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This PR introduces the ability to track metric by component (e.g., Kafka, Prometheus). It replaces static metrics with dynamic labels, enabling granular insights into trends across different components.
Key Changes
component
label (e.g.,jira_deployments_weekly{component="Kafka"}
).GaugeVec
to support dynamic labels.Issue
,Component
,JiraResponse
) for structured data handling.goto
statements and improved error logging.config.yaml
(setcomponent: ""
to enable).Usage Example
After deploying, the following metrics will be exposed: