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

Add Remediation Steps for each event to Alerts page #19354

Open
rich-graylog opened this issue May 15, 2024 · 1 comment
Open

Add Remediation Steps for each event to Alerts page #19354

rich-graylog opened this issue May 15, 2024 · 1 comment

Comments

@rich-graylog
Copy link

rich-graylog commented May 15, 2024

Relates to Graylog2/support#47

What?

Graylog 6.0 introduced Remediation steps to Event Definitions, but in the frontend this is only displayed in the Security perspective, and not the General perspective. Given that this is an open feature for Event Definitions, it should be displayed in the General perspective as well.

Why?

Open/Enterprise users can define Remediation Steps in Event Definitions, but are not able to view them when an event fires (this is only available for users with a Security license currently)

This will likely need to be an expandable/collapsible section within the details of an alert that has fired, but should work with UI design to come up with a solution for how it should be displayed on the page.

@coffee-squirrel
Copy link

coffee-squirrel commented May 15, 2024

Related to our case 486, it seems. I didn't realize this was an Open feature, since it was only mentioned in the Enterprise/Security changelog (and the event definitions documentation).

I'd ask that this be extended to enable including remediation steps in notification templates. Specifically: it'd be nice to have one or more new metadata fields for the remediation steps, with plaintext notifications having the raw markdown and HTML notifications having the HTML representation of the markdown.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants