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

+IndexPattern API pull #541

Closed
wants to merge 1 commit into from

Conversation

stefnestor
Copy link
Contributor

👋🏼 I would like to recommend automating pulling Kibana's Index Pattern list for your consideration. While the feature fits better under Kibana, I've figured out to pull it via Elasticsearch API & therefore have put it under that code area. Thanks in advance!

Key investigation benefits

  • are user requests for index / index pattern
  • what timeFieldName is used
  • answering column differences between index mappings & why user thinks "works sometimes & not others" aka. based on time range back

image

@stefnestor stefnestor requested a review from a team as a code owner October 2, 2021 02:21
Copy link
Member

@pickypg pickypg left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I do not think that we can / should do this. We currently tell our users that the ES diagnostic does not read their data, and this would invalidate that statement.

Separately, the Kibana diagnostic should help with some of this.

@stefnestor
Copy link
Contributor Author

Noting for self, Kibana does have an endpoint for this, but it's space deliminated requiring #578

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants