-
Notifications
You must be signed in to change notification settings - Fork 8.3k
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
[Alerting] Updating audit event terminology #102263
[Alerting] Updating audit event terminology #102263
Conversation
@legrego This PR updates the terminology of audit events coming from the alerting framework as related to rules CRUD, based on this conversation in the alerts-as-data RBAC PR. Just verifying again that this change is ok since audit events for the |
Awesome, thanks!
Yes, I'm ok with this divergence - I think this change is actually more consistent from an end-user's perspective, as they think of these as "rules" rather than "alerts". Yes, let's mark this as a breaking change so that auditors know that we've changed the event types |
Pinging @elastic/kibana-alerting-services (Team:Alerting Services) |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Nice work here!
What about this file? https://github.com/elastic/kibana/blob/master/docs/user/security/audit-logging.asciidoc
…ing/audit-events-new-terminology
@chrisronline Thanks for pointing this out! Updated the docs. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM!
@elasticmachine merge upstream |
💚 Build Succeeded
Metrics [docs]
History
To update your PR or re-run it, just comment with: cc @ymao1 |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM!
* Updating audit terminology * Fixing unit tests * Updating audit docs Co-authored-by: Kibana Machine <42973632+kibanamachine@users.noreply.github.com>
💚 Backport successful
This backport PR will be merged automatically after passing CI. |
Resolves #101476
Summary
This PR updates the terminology for audit events logged by the alerting framework alerts client when CRUD operations are performed on rules.
The following audit actions have been renamed:
alert_create
has been renamed torule_create
alert_get
has been renamed torule_get
alert_update
has been renamed torule_update
alert_update_api_key
has been renamed torule_update_api_key
alert_enable
has been renamed torule_enable
alert_disable
has been renamed torule_disable
alert_delete
has been renamed torule_delete
alert_find
has been renamed torule_find
alert_mute
has been renamed torule_mute
alert_unmute
has been renamed torule_unmute
alert_instance_mute
has been renamed torule_alert_mute
alert_instance_unmute
has been renamed torule_alert_unmute
In addition, the terminology inside the audit messages has been update to reference
rules
instead of `alerts. For example:User is creating alert [id=${ruleId}]
will now readUser is creating rule [id=${ruleId}]
Checklist
Delete any items that are not applicable to this PR.