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

Remove default request looking for logstash-* on pattern creation page #7638

Closed
mostolog opened this issue Jul 6, 2016 · 3 comments
Closed

Comments

@mostolog
Copy link

mostolog commented Jul 6, 2016

Hi

When browsing to /app/kibana#/settings/indices, on page load, Kibana tries to find logstash-* index-pattern, making a request to _/elasticsearch/logstash-/mapping/field/ which results on 404.

As we are monitoring requests, this is adding some garbage that - IMHO- could be avoided.

Wouldn't be greater if that request its only made when Kibana doesn't have any indexes?

Regards

@Bargs
Copy link
Contributor

Bargs commented Jul 6, 2016

I'd actually like to remove the default logstash-* value completely.

@Bargs Bargs changed the title Kibana request looking for logstash-* Remove default request looking for logstash-* on pattern creation page Jul 6, 2016
@bohyun-e
Copy link

bohyun-e commented Jul 7, 2016

I'm ++ on @Bargs suggestion on removing the default value. But I think that users will benefit from having a default value. When I first installed Kibana (first time ever) it was nice to have something rather than nothing... even though it didn't help me a ton.

I'd like to give my personal preference as an idea. I have developed a habit of typing * because it's what I typed when I didn't have much understanding of Kibana in general. I think that it's a generally well-known concept that * will fetch any index pattern and it gives users more context on what Configuring an index pattern page is about since we don't offer auto complete or anything like that. At least this way, they will see something, and be able to create an index that will allow them to move forward. I realize this might have its own downsides such as we might not want to encourage users to create this pattern as they might have some enormous amount of data.

@jbudz
Copy link
Member

jbudz commented Nov 8, 2017

Resolved by #13454

@jbudz jbudz closed this as completed Nov 8, 2017
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

5 participants