-
Notifications
You must be signed in to change notification settings - Fork 485
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
Feedback about inactive components #3253
Comments
@netchild: Thanks for opening an issue, it is currently awaiting triage. In the meantime, you can:
DetailsI 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. |
@netchild: There are no 'kind' label on this issue. You need a 'kind' label to start the triage process.
DetailsI 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. |
/kind feature |
This is on the roadmap to be implemented shortly, you should be able to see "integrations" under the settings tab for your personal or organization. These will be the current providers we will support, so if you have a suggestion please come here and submit an integration. Classing as completed as this is the CrowdSec repository and we are tracking the task internally at CrowdSecurity. |
What would you like to be added?
/kind feature
Please add an indicator to the cloud UI and/or an email notification, if a component is inactive above a specific threshold.
Why is this needed?
My firewall bouncer was inactive for more than a month until I noticed it. Marco Mariani helped me to fix this. As I was new to crowdsec, it took me a while until I noticed the issue. Only after looking at the engine -> remediation component I was able to see that it was listed as inactive since a month.
If it was displayed prominently at login above the line "Security Engines Blocklists ...", or send as a notification via email after it was detected to be inactive for 1h, or 1 day, or whatever, it could have been detected much faster.
The text was updated successfully, but these errors were encountered: