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

[Alerting] Update alerts client audit events to new terminology #101476

Closed
ymao1 opened this issue Jun 7, 2021 · 1 comment · Fixed by #102263
Closed

[Alerting] Update alerts client audit events to new terminology #101476

ymao1 opened this issue Jun 7, 2021 · 1 comment · Fixed by #102263
Assignees
Labels
Feature:Alerting Team:ResponseOps Label for the ResponseOps team (formerly the Cases and Alerting teams)

Comments

@ymao1
Copy link
Contributor

ymao1 commented Jun 7, 2021

Currently, the audit messages generated by the alerts client all use some form of alert_. With this PR, the RAC effort will be adding an alerts client for accessing alerts as data an also generating audit events with the alert_ prefix. There was a question of whether the audit events needs to match the saved object type (which for alerting is currently still alert) but based on this comment, this doesn't seem to be an issue, so we should update our audit events to use rule_ to be consistent with the new terminology and to avoid confusion.

@ymao1 ymao1 added Feature:Alerting Team:ResponseOps Label for the ResponseOps team (formerly the Cases and Alerting teams) labels Jun 7, 2021
@elasticmachine
Copy link
Contributor

Pinging @elastic/kibana-alerting-services (Team:Alerting Services)

@ymao1 ymao1 self-assigned this Jun 15, 2021
@kobelb kobelb added the needs-team Issues missing a team label label Jan 31, 2022
@botelastic botelastic bot removed the needs-team Issues missing a team label label Jan 31, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Feature:Alerting Team:ResponseOps Label for the ResponseOps team (formerly the Cases and Alerting teams)
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants