Can't view discover or viz without some non-dotted index present

[matschaffer]

Kibana version: main

Elasticsearch version: snapshot

Server OS version: macOS

Browser version: Chrome

Browser OS version: latest

Original install method (e.g. download page, yum, from source, etc.): source

Description of the problem including expected versus actual behavior:

If you attempt to load discover or vizualize on a fresh ES/kibana you get greeted with this screen. This is

Previously I would have expected to create a data view to get access to discover. But I work on stack monitoring mostly, so I tend to create a .monitoring-* data view.

Now doing so doesn't get past the "add integrations".

What seems to work is if I write a non-dotted index

PUT mat-2022.06.01/_doc/1
{ "some": "stuff" }

Steps to reproduce:

1. Stand up ES/kibana
2. Enable stack monitoring
3. Add a .monitoring-* data view
4. Try to get to discover/viz

[majagrubic]

We have intentionally added a check for user-created indices and the assumption was that all indices prefixed with a dot are system created ones, which is also the case here. Before we decide on the further action items on this, I would like to understand a use-case for this a bit better. Is it expected from the end user to create a data view on the .monitoring index and explore it? Or is this something you primarily do as a developer?

[elasticmachine]

cc @elastic/kibana-app-services (Team:AppServicesSv) as they own the service, so to be in the loop of these conversations

[matschaffer]

Is it expected from the end user to create a data view on the .monitoring index and explore it? Or is this something you primarily do as a developer?

We have cases where end users will explore the data available (there's more there than what's graphed). But it's not a recommended practice. As such I'd say it's mainly a developer confusion case.

[majagrubic]

I think the best course of action here then is to bypass this check in dev environments. I'll have a look into what's the best way to accomplish that

[majagrubic]

I've added this check for Discover for now. But since this is used across many apps, how about adding this check to the service directly, @elastic/kibana-app-services?

[elasticmachine]

Pinging @elastic/kibana-data-discovery (Team:DataDiscovery)

[kertal]

Closing this because it's not planned to be resolved in the foreseeable future. It will be tracked in our Icebox and will be re-opened if our priorities change. Feel free to re-open if you think it should be melted sooner.