Skip to content
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

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

Closed
Tracked by #166175
matschaffer opened this issue Jun 1, 2022 · 7 comments
Closed
Tracked by #166175

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

matschaffer opened this issue Jun 1, 2022 · 7 comments
Labels
Feature:Data Views Data Views code and UI - index patterns before 8.0 Icebox impact:low Addressing this issue will have a low level of impact on the quality/strength of our product. loe:needs-research This issue requires some research before it can be worked on or estimated Team:DataDiscovery Discover, search (e.g. data plugin and KQL), data views, saved searches. For ES|QL, use Team:ES|QL. Team:SharedUX Team label for AppEx-SharedUX (formerly Global Experience)

Comments

@matschaffer
Copy link
Contributor

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

Screen Shot 2022-06-01 at 16 19 21

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.

Screen Shot 2022-06-01 at 16 49 59

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" }

Screen Shot 2022-06-01 at 16 50 37

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
@matschaffer matschaffer added the bug Fixes for quality problems that affect the customer experience label Jun 1, 2022
@botelastic botelastic bot added the needs-team Issues missing a team label label Jun 1, 2022
@matschaffer matschaffer removed the bug Fixes for quality problems that affect the customer experience label Jun 1, 2022
@majagrubic
Copy link
Contributor

majagrubic commented Jun 1, 2022

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?

@majagrubic majagrubic added the Team:SharedUX Team label for AppEx-SharedUX (formerly Global Experience) label Jun 1, 2022
@botelastic botelastic bot removed the needs-team Issues missing a team label label Jun 1, 2022
@elasticmachine
Copy link
Contributor

elasticmachine commented Jun 1, 2022

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

@matschaffer
Copy link
Contributor Author

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
Copy link
Contributor

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
Copy link
Contributor

majagrubic commented Jun 3, 2022

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?

@exalate-issue-sync exalate-issue-sync bot added the impact:needs-assessment Product and/or Engineering needs to evaluate the impact of the change. label Jul 28, 2022
@petrklapka petrklapka added Feature:Data Views Data Views code and UI - index patterns before 8.0 Team:DataDiscovery Discover, search (e.g. data plugin and KQL), data views, saved searches. For ES|QL, use Team:ES|QL. and removed Team:AppServicesSv labels Nov 28, 2022
@elasticmachine
Copy link
Contributor

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

@kertal kertal added impact:low Addressing this issue will have a low level of impact on the quality/strength of our product. and removed impact:needs-assessment Product and/or Engineering needs to evaluate the impact of the change. labels Feb 28, 2023
@davismcphee davismcphee added the loe:needs-research This issue requires some research before it can be worked on or estimated label Sep 8, 2023
@kertal kertal added the Icebox label Oct 23, 2023
@kertal
Copy link
Member

kertal commented Oct 23, 2023

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.

@kertal kertal closed this as completed Oct 23, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Feature:Data Views Data Views code and UI - index patterns before 8.0 Icebox impact:low Addressing this issue will have a low level of impact on the quality/strength of our product. loe:needs-research This issue requires some research before it can be worked on or estimated Team:DataDiscovery Discover, search (e.g. data plugin and KQL), data views, saved searches. For ES|QL, use Team:ES|QL. Team:SharedUX Team label for AppEx-SharedUX (formerly Global Experience)
Projects
None yet
Development

No branches or pull requests

6 participants