-
Notifications
You must be signed in to change notification settings - Fork 60
Doc: APM setup in Kibana #359
Copy link
Copy link
Open
Labels
bugIncorrect or broken documentation, rendering, tooling, or automationIncorrect or broken documentation, rendering, tooling, or automationneeds infoMore information is required before the issue can be acted onMore information is required before the issue can be acted on
Description
Activity
Metadata
Metadata
Assignees
Labels
bugIncorrect or broken documentation, rendering, tooling, or automationIncorrect or broken documentation, rendering, tooling, or automationneeds infoMore information is required before the issue can be acted onMore information is required before the issue can be acted on
Type
Projects
- StatusShow more project fieldsNo status
Checking for existing issue
Describe the content you'd like to see
The issue
On new Elastic add-on creation, with Kibana and APM activated, Kibana UI won't load the connected services in the APM menu. It will rather ask the user to "Install APM" on Kibana. The configuration wizard will then launch and offer a set of options, that don't actually matter at all: clicking on next and finishing the "installation" is enough to finally launch the list of connected services monitored by the APM server.
The solution
Until this behavior changes, this needs to be documented in the Elastic pages, to avoid getting users lost when they try Elastic x APM for the first time.