-
Notifications
You must be signed in to change notification settings - Fork 23
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Show appropriate status message via self monitor if a target is close to scrape limit #1037
Comments
This issue has been automatically marked as stale due to the lack of recent activity. It will soon be closed if no further activity occurs. |
This issue has been automatically closed due to the lack of recent activity. |
This issue has been automatically marked as stale due to the lack of recent activity. It will soon be closed if no further activity occurs. |
This issue has been automatically marked as stale due to the lack of recent activity. It will soon be closed if no further activity occurs. |
Description
As part of #976 the metric-agent should expose under a dedicated port the diagnostic metrics relevant for scraping metric targets via the prometheusreceiver. The new port should be protected by a networkpolicy so that user cannot reach it. For now the plain exposure is enough in order to enable operational diagnostic.
Criterias
Implementation details
Example configuration for metrics agent
Probably we should not expose just all metrics but also filter out business metrics. So instead we should use a new dedicated pipeline having the same receivers as input, but doing a specialized filtering and exporting
The text was updated successfully, but these errors were encountered: