-
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
[Stack Monitoring] Rename "APM & Fleet Server" to "Integrations Server" #128574
[Stack Monitoring] Rename "APM & Fleet Server" to "Integrations Server" #128574
Conversation
Not sure if I should update or remove them, but the translation seemed straightforward enough, so I just went for it.
Pinging @elastic/infra-monitoring-ui (Team:Infra Monitoring UI) |
This reverts commit 670aafe.
@elasticmachine merge upstream |
💚 Build SucceededMetrics [docs]Async chunks
History
To update your PR or re-run it, just comment with: cc @matschaffer |
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 (will test with the snapshot on cloud once it is available)
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
💔 All backports failed
Manual backportTo create the backport manually run:
Questions ?Please refer to the Backport tool documentation |
Friendly reminder: Looks like this PR hasn’t been backported yet. |
1 similar comment
Friendly reminder: Looks like this PR hasn’t been backported yet. |
…r" (elastic#128574) (cherry picked from commit 437adb5) # Conflicts: # x-pack/plugins/monitoring/dev_docs/how_to/running_components_from_source.md
…r" (elastic#128574) (cherry picked from commit 437adb5) # Conflicts: # x-pack/plugins/monitoring/dev_docs/how_to/running_components_from_source.md
Summary
Replaces any "APM & Fleet Server" with "Integrations Server"
Fixes #123898
Checklist
Delete any items that are not applicable to this PR.
Notes to reviewers
It wasn't clear to me from https://github.com/elastic/kibana/blob/main/packages/kbn-i18n/GUIDELINE.md what the protocol was to handled translations for an update case. The change seemed fairly simple so I just did the translation on my own.
If that's incorrect, please let me know what the appropriate handling for updating translated strings is. Thanks!