Skip to content
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

Prometheus: expose machine_id in alert metrics #3125

Open
seamus-45 opened this issue Jul 12, 2024 · 3 comments
Open

Prometheus: expose machine_id in alert metrics #3125

seamus-45 opened this issue Jul 12, 2024 · 3 comments
Labels
kind/enhancement New feature or request needs/triage

Comments

@seamus-45
Copy link

seamus-45 commented Jul 12, 2024

What would you like to be added?

Add some context for alert metrics like machine name. This will allow to better see the attack vector on Grafana dashboards.

Current query is sum(cs_alerts{instance="$instance"}) on Crowdsec Details per instance dashboard and it display 0 alerts on agent nodes when local DB is disabled. When I change it to sum(cs_alerts{}) then all alerts from all instances is displayed. It would be better if we could see the source for alerts like sum(cs_alerts{}) by (alert_source) if such data were available.

Why is this needed?

Prometheus alert metrics become useless when the engine switched to the agent mode (with centralized LAPI) as they comes from the local DB even if local LAPI server is disabled.

Copy link

@seamus-45: Thanks for opening an issue, it is currently awaiting triage.

In the meantime, you can:

  1. Check Crowdsec Documentation to see if your issue can be self resolved.
  2. You can also join our Discord.
  3. Check Releases to make sure your agent is on the latest version.
Details

I am a bot created to help the crowdsecurity developers manage community feedback and contributions. You can check out my manifest file to understand my behavior and what I can do. If you want to use this for your project, you can check out the BirthdayResearch/oss-governance-bot repository.

Copy link

@seamus-45: There are no 'kind' label on this issue. You need a 'kind' label to start the triage process.

  • /kind feature
  • /kind enhancement
  • /kind refactoring
  • /kind bug
  • /kind packaging
Details

I am a bot created to help the crowdsecurity developers manage community feedback and contributions. You can check out my manifest file to understand my behavior and what I can do. If you want to use this for your project, you can check out the BirthdayResearch/oss-governance-bot repository.

@seamus-45
Copy link
Author

/kind enhancement

@github-actions github-actions bot added kind/enhancement New feature or request and removed needs/kind labels Jul 12, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
kind/enhancement New feature or request needs/triage
Projects
None yet
Development

No branches or pull requests

1 participant