Kibana: [APM] Remove "Load Kibana objects" from APM getting started instructions

[nreese]

Opening the APM application automatically creates a kibana index pattern with the id index-pattern:apm_static_index_pattern_id.

Conflicting with this is the APM getting started instructions, https://www.elastic.co/guide/en/kibana/7.6/apm-getting-started.html. These instructions tell users to click Load Kibana objects. This loads another kibana index pattern with the id index-pattern:apm-*. This additional kibana index pattern is not needed now that APM automatically creates a kibana index pattern when opened.

[elasticmachine]

Pinging @elastic/apm-ui (Team:apm)

[elasticmachine]

Pinging @elastic/kibana-docs (Team:Docs)

[bmorelli25]

This sounds partially like a docs issue, but it also sounds like the Load Kibana objects button on the APM Add data page might not be necessary anymore?

Edit: Nevermind, I guess it's still necessary for users that don't use the APM app. I'll update the docs to reflect this.

[formgeist]

@bmorelli25 Agreed, if the index is created automatically and we're referring to the contribs repository for users to add dashboards, I don't think the button does anything else. @sqren is that right?

[sqren]

@nreese uncovered a bug where the "Load Kibana objects" button in the getting started guide actually creates the wrong index pattern. So we should either fix the button or remove it.

I was of the impression that we could simply remove the button because the index pattern is loaded automatically in APM app. But as @bmorelli25 points out the users on OSS still need an easy way to create APM index pattern. This is required to use Discover and the upcoming Maps feature and I don't think it's reasonable to ask users to go to the contrib repo to use those features.

So I think we'll have to fix it.

[formgeist]

I just wanted to also add that we have another bug related to this option in the backlog https://github.com/elastic/kibana/issues/61378

[sqren]

@formgeist Ah, that is exactly it! Clicking the button doesn't actually load two index patterns but if you also visit the APM app you'll end up with two because the APM app creates another one automatically.

I'll create a fix now and get this over with.