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

Add support for alias in Kibana index pattern generation #10013

Closed
ruflin opened this issue Jan 11, 2019 · 1 comment
Closed

Add support for alias in Kibana index pattern generation #10013

ruflin opened this issue Jan 11, 2019 · 1 comment
Assignees
Labels
libbeat Team:Integrations Label for the Integrations team v7.0.0-beta1

Comments

@ruflin
Copy link
Contributor

ruflin commented Jan 11, 2019

Beats automatically generates the index pattern for Kibana based on the fields.yml. Currently all fields marked as type: alias are skipped.

The type that should be loaded into Kibana is the same as the original field. Unfortunately there is no type: alias concept in Kibana. This means we need to look up the generation of the type in our own fields based on the path.

This feature is needed to have the alias also listed in the fields when migration.enabled: true is used.

Note: It seems at the moment if there is 6.x and 7.x data with migration alias enabled things work as expected as the fields are already defined in the template and Kibana as mentioned above does not make a difference if it's an original field or not.

@ruflin
Copy link
Contributor Author

ruflin commented Feb 5, 2019

Closing as this was introduced in #9805

@ruflin ruflin closed this as completed Feb 5, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
libbeat Team:Integrations Label for the Integrations team v7.0.0-beta1
Projects
None yet
Development

No branches or pull requests

3 participants