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 UI to reflect new terminology #93597

Merged
merged 36 commits into from
Mar 15, 2021

Conversation

ymao1
Copy link
Contributor

@ymao1 ymao1 commented Mar 4, 2021

Resolves #92166

Summary

  • Renamed Alerts -> Rules and Actions -> Connectors in UI
  • Renamed routes from /alerts and /alert/{alertId} to /rules and /rule/{ruleId} and added redirect to make sure old URLs redirect to new URLs
  • Updated docs to reflect new terminology and updated screenshots in docs to show updated UI.

Updated docs (these are the entry points to all the updated doc pages)

https://kibana_93597.docs-preview.app.elstc.co/guide/en/kibana/master/managing-alerts-and-actions.html
https://kibana_93597.docs-preview.app.elstc.co/guide/en/kibana/master/alerting-getting-started.html

Checklist

Delete any items that are not applicable to this PR.

@ymao1 ymao1 requested a review from a team as a code owner March 9, 2021 17:01
@elasticmachine
Copy link
Contributor

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

@ymao1
Copy link
Contributor Author

ymao1 commented Mar 9, 2021

jenkins retest this please

Copy link
Contributor

@darnautov darnautov left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

ML changes LGTM

@gmmorris gmmorris self-requested a review March 10, 2021 11:05
@@ -0,0 +1,58 @@
[role="xpack"]
[[alert-management]]
=== Managing Rules
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Should we be referring to these as "Alerting Rules" here? 🤔

I'm not 100% sure when we should use the whole term rather than just "Rules"...

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Since this is under the Rules and Connectors page and there's a sibling page called Managing Connectors, I think Managing Rules is ok here? I'll let @gchaps be the final judge :)

@gmmorris
Copy link
Contributor

Should this dropdown be relabeled?
I'm actually ok with it staying "action" here, as it is the action that's attached to the rule, rather than the connector, but it can be confusing how we use both "Connector Type" and "Action Type" interchangeably 🤔

Not sure... so just floating the question.

Screenshot 2021-03-10 at 11 29 01

@gmmorris
Copy link
Contributor

gmmorris commented Mar 10, 2021

The Alerting Example app still uses the legacy terminology.
Should we take this opportunity to update it as well?

I know I'm moving the goal posts here as I forgot about it 😆 sorry about that.

Screenshot 2021-03-10 at 11 49 39

Screenshot 2021-03-10 at 11 52 53

Copy link
Contributor

@gmmorris gmmorris left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I've looked through the docs and UI, and it all looks spot on :)

Asked a couple of questions, but broadly, looks like all bases have been covered 😄

@ymao1
Copy link
Contributor Author

ymao1 commented Mar 10, 2021

Should this dropdown be relabeled?

I debated this as well and kept it for the same reason you mentioned: it is specifically referencing the action in the context of a rule.

@ymao1
Copy link
Contributor Author

ymao1 commented Mar 10, 2021

The Alerting Example app still uses the legacy terminology.
Should we take this opportunity to update it as well?

Updated!

Copy link
Contributor

@YulNaumenko YulNaumenko left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM

@ymao1
Copy link
Contributor Author

ymao1 commented Mar 15, 2021

@elasticmachine merge upstream

@kibanamachine
Copy link
Contributor

💚 Build Succeeded

Metrics [docs]

Async chunks

Total size of all lazy-loaded chunks that will be downloaded as the user navigates the app

id before after diff
triggersActionsUi 1.5MB 1.5MB +1.8KB

Page load bundle

Size of the bundles that are downloaded on every page load. Target size is below 100kb

id before after diff
triggersActionsUi 104.2KB 104.3KB +171.0B

History

To update your PR or re-run it, just comment with:
@elasticmachine merge upstream

cc @ymao1

@ymao1 ymao1 added the auto-backport Deprecated: Automatically backport this PR after it's merged label Mar 15, 2021
@ymao1
Copy link
Contributor Author

ymao1 commented Mar 15, 2021

@gchaps I am merging this PR because it contains a lot of changed files and I want to avoid too many conflicts. I will address any docs feedback you have separately.

@ymao1 ymao1 merged commit a7c9d3f into elastic:master Mar 15, 2021
kibanamachine added a commit to kibanamachine/kibana that referenced this pull request Mar 15, 2021
* Renaming alerts to rules

* Updating formatted messages

* Updating i18n labels

* Completed renaming in UI

* Updating client routes including redirect

* wip docs update

* Reverting title changes for now

* Fixing types check

* Fixing unit tests

* Fixing functional test

* Fixing functional test

* docs wip

* wip docs update

* Finished first run through docs

* docs docs docs

* Fixing bad merge

* Fixing functional test

* Docs cleanup

* Cleaning up i18n labels

* Fixing functional test

* Updating screenshots

* Updating screenshots

* Updating screenshots

* Updating terminology in alerting examples

* Updating terminology in alerting examples

Co-authored-by: Kibana Machine <42973632+kibanamachine@users.noreply.github.com>
@kibanamachine
Copy link
Contributor

💚 Backport successful

7.x / #94572

Successful backport PRs will be merged automatically after passing CI.

kibanamachine added a commit that referenced this pull request Mar 15, 2021
* Renaming alerts to rules

* Updating formatted messages

* Updating i18n labels

* Completed renaming in UI

* Updating client routes including redirect

* wip docs update

* Reverting title changes for now

* Fixing types check

* Fixing unit tests

* Fixing functional test

* Fixing functional test

* docs wip

* wip docs update

* Finished first run through docs

* docs docs docs

* Fixing bad merge

* Fixing functional test

* Docs cleanup

* Cleaning up i18n labels

* Fixing functional test

* Updating screenshots

* Updating screenshots

* Updating screenshots

* Updating terminology in alerting examples

* Updating terminology in alerting examples

Co-authored-by: Kibana Machine <42973632+kibanamachine@users.noreply.github.com>

Co-authored-by: ymao1 <ying.mao@elastic.co>
@ymao1 ymao1 deleted the alerting/rename-ui branch March 25, 2021 14:41
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
auto-backport Deprecated: Automatically backport this PR after it's merged Feature:Alerting release_note:skip Skip the PR/issue when compiling release notes Team:ResponseOps Label for the ResponseOps team (formerly the Cases and Alerting teams) v7.13.0 v8.0.0
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Relabel UI and Documentation to use new terminology
6 participants