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.

Sign up for GitHub

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

Jump to bottom

Update Elastic Glossary to reflect new Alerting terminology #93970

Closed
gmmorris opened this issue Mar 8, 2021 · 1 comment · Fixed by #94447
Closed

Update Elastic Glossary to reflect new Alerting terminology #93970

gmmorris opened this issue Mar 8, 2021 · 1 comment · Fixed by #94447
Assignees
@ymao1
Labels
Feature:Alerting Project:UnifiedAlertingArchitectureAndExperience Alerting team project for developing a unified alerting experience. Team:ResponseOps Label for the ResponseOps team (formerly the Cases and Alerting teams)
Projects
Kibana Alerting

Comments

@gmmorris
Copy link
Contributor

gmmorris commented Mar 8, 2021

This is part of #90375, which summarizes the new terminology to use in Kibana alerting.

This issue covers the update to the Elastic Glossary: https://www.elastic.co/guide/en/elastic-stack-glossary/current/terms.html.

We'll ned to update:

  1. alert (rename to rule, though it might be worth syncing with ml as I can also see a term custom rules which could be confused with these)
  2. Alerts and Actions (rename to match changes made in Relabel UI and Documentation to use new terminology #92166)
@gmmorris gmmorris mentioned this issue Mar 8, 2021
Open
17 tasks
@gmmorris gmmorris added Feature:Alerting Project:UnifiedAlertingArchitectureAndExperience Alerting team project for developing a unified alerting experience. Team:ResponseOps Label for the ResponseOps team (formerly the Cases and Alerting teams) labels Mar 8, 2021
@elasticmachine
Copy link
Contributor

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

@gmmorris gmmorris added this to To-Do (Ordered by priority) in Kibana Alerting Mar 10, 2021
@ymao1 ymao1 self-assigned this Mar 11, 2021
@ymao1 ymao1 moved this from To-Do (Ordered by priority) to In Progress in Kibana Alerting Mar 11, 2021
@ymao1 ymao1 mentioned this issue Mar 11, 2021
Merged
@ymao1 ymao1 moved this from In Progress to In Review in Kibana Alerting Mar 15, 2021
Kibana Alerting automation moved this from In Review to Done (Ordered by most recent) Mar 16, 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
Assignees

@ymao1 ymao1

Labels
Feature:Alerting Project:UnifiedAlertingArchitectureAndExperience Alerting team project for developing a unified alerting experience. Team:ResponseOps Label for the ResponseOps team (formerly the Cases and Alerting teams)
Projects
No open projects
Kibana Alerting
Done (Ordered by most recent)
Milestone
No milestone
Development

Successfully merging a pull request may close this issue.

[Alerting][Docs] Updating glossary with new terminology ymao1/kibana
4 participants
@gmmorris @kobelb @ymao1 @elasticmachine