-
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
[APM] Implementation of runtime UI index configuration #45247
Comments
Pinging @elastic/apm-ui |
@katrin-freihofner When clicking "Settings" which should be the landingpage? UI Indices page or Agent configuration page? |
My idea was the UI indices - that's also shown in the prototype. |
Ah, my bad 👍 |
sorenlouv
added
[zube]: (7.5) Planned for release
and removed
[zube]: Impl Backlog
labels
Sep 18, 2019
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
As described in #39741 this new APM settings page should allow users to configure UI indices. These settings override the kibana.yml settings.
The
Settings
button in the APM home screen should lead to a new settings page. This page is responsible for configuring the following UI indices:Prototype:
https://www.figma.com/proto/yeugPdG4YlLNJK6iGPdExu/39741-APM-config?node-id=19%3A1045&viewport=699%2C811%2C0.25&scaling=min-zoom
Additional notes:
Apply changes
button is disabled until the inputs are actually changed.problem toast
) https://elastic.github.io/eui/#/guidelines/toastsThe
Agent configuration
that is currently visible when clickingSettings
should move to a separate page which is reachable via the menu on the left.Text:
The APM UI uses index patterns to query your APM indices. If you've customized the index names that APM Server writes events to, you may need to update these patterns for the APM UI to work. Settings here take precedence over those set in
kibana.yml
.The text was updated successfully, but these errors were encountered: