-
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] Move APM index pattern creation from Kibana startup #37499
Comments
Pinging @elastic/apm-ui |
@ogupte Perhaps this would make sense for you to look at since you implemented the automatic index pattern creation? |
ogupte
added a commit
to ogupte/kibana
that referenced
this issue
Jun 5, 2019
…er startup to savedObject request for the index pattern. It first checks if the index pattern is saved, if not it creates it.
ogupte
added a commit
to ogupte/kibana
that referenced
this issue
Jun 6, 2019
* [APM] Closes elastic#37499 by moving the APM index creation from server startup to savedObject request for the index pattern. It first checks if the index pattern is saved, if not it creates it. * [APM] provide more meaninful status codes in the default error handler
ogupte
added a commit
that referenced
this issue
Jun 6, 2019
* [APM] Closes #37499 by moving the APM index creation from server startup to savedObject request for the index pattern. It first checks if the index pattern is saved, if not it creates it. * [APM] provide more meaninful status codes in the default error handler
ogupte
added a commit
to ogupte/kibana
that referenced
this issue
Jun 6, 2019
* [APM] Closes elastic#37499 by moving the APM index creation from server startup to savedObject request for the index pattern. It first checks if the index pattern is saved, if not it creates it. * [APM] provide more meaninful status codes in the default error handler
ogupte
added a commit
that referenced
this issue
Jun 6, 2019
* [APM] Closes #37499 by moving the APM index creation from server startup to savedObject request for the index pattern. It first checks if the index pattern is saved, if not it creates it. * [APM] provide more meaninful status codes in the default error handler
ogupte
added a commit
that referenced
this issue
Jun 6, 2019
* [APM] Closes #37499 by moving the APM index creation from server startup to savedObject request for the index pattern. It first checks if the index pattern is saved, if not it creates it. * [APM] provide more meaninful status codes in the default error handler
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
This issue proposes a quick fix for #35898 while waiting for a proper solution like #37498
Currently the APM index pattern is created when Kibana starts up:
kibana/x-pack/plugins/apm/server/new-platform/plugin.ts
Line 27 in e2ae24d
This causes the Kibana Home Welcome screen to not show up, since it is only displayed if no index patterns exist:
https://github.com/elastic/kibana/blob/master/src/legacy/core_plugins/kibana/public/home/components/home.js#L89
To ensure that the very first user is able to see the welcome screen we should move the APM index pattern creation to the APM UI where we already fetch the index pattern:
https://github.com/sqren/kibana/blob/9ebba02e5c36db72faf5f3ee10308b588442eb43/x-pack/plugins/apm/public/services/rest/savedObjects.ts#L23-L41
The text was updated successfully, but these errors were encountered: