-
Notifications
You must be signed in to change notification settings - Fork 625
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
Custom severity levels for alerts and cases #363
Comments
+1, We have a P0-P3 scheme and would like the additional support for defining custom severity/priority levels |
We also need custom / more severity levels 👍 |
Same for us ! |
Custom severity 👍 |
I think allow users to display their own metrics in the cases list and allow them to sort the cases by the metrics would fix the need just fine. |
Is being able to customize severity levels still being pursued? |
Yes, please! |
This would be great! |
#939 adds Critical severity :) |
4.0.0-RC1 has already added a Any thoughts? |
I think introducing critical as 4th severity is very helpfull. |
I know this issue has been closed but I would still like to be able to customize the labels (four are enough). Our workflow is this:
I think that being able to make the names/labels match the different organizational vocabularies and cultures is fairly important when talking about incident response. |
Request Type
Feature Request
Problem Description
Currently, the severity level of alerts and cases is hardcoded to the values Low, Medium and High. We would love to have these customizable because our current SOC processes support more than those three values (i.e. there is also "Info only" and "Critical").
The text was updated successfully, but these errors were encountered: