-
Notifications
You must be signed in to change notification settings - Fork 515
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
Kibana does not remove index template for removed data streams on integrations upgrade #13181
Comments
We can unblock ourselves by increasing the priority of the templates in the apm-data plugin: #11529 (comment) Not ideal, but I think that's likely the most expedient approach. We should still go ahead with removing the data streams from the integration package, the existing templates just won't be removed. If need be, we could add some code to Kibana to remove them for APM specifically. |
We moved forward with increasing the priorities in elastic/elasticsearch#108885 I'd keep this issue open to track this Kibana behavior which may still affect the migration (es removing old templates is a manual step). |
When we will migrate from
apm
integration package toapm-data
ES plugin we will need to trigger a removal of index templates created by the integration, which by default are created with a higher priority than the one created by the ES plugin.To ensure this steps works I run a test to verify if Kibana removes index template when upgrading an integration where installed data streams have been removed. I tested these steps:
apm
integration package (tested with8.15.0-SNAPSHOT
but any current version should lead to same results)apm
integration package where all data streams except one (traces
- due to howelastic-package
works is not possible to package an integration without at least 1 data stream; this is not relevant for this test but should be investigated to proceed further with the migration) have been removedThe test showed that Index Templates are not removed. This is a blocker for #11529 as templates from the plugin would be overridden by the integration package templates.
Assets difference between packages
Assets with normal integration package:
![2024-05-16_16-06](https://private-user-images.githubusercontent.com/526307/331507448-1c366629-20be-4577-a4a3-a3311fa387d1.png?jwt=eyJhbGciOiJIUzI1NiIsInR5cCI6IkpXVCJ9.eyJpc3MiOiJnaXRodWIuY29tIiwiYXVkIjoicmF3LmdpdGh1YnVzZXJjb250ZW50LmNvbSIsImtleSI6ImtleTUiLCJleHAiOjE3MjIzODUyNjIsIm5iZiI6MTcyMjM4NDk2MiwicGF0aCI6Ii81MjYzMDcvMzMxNTA3NDQ4LTFjMzY2NjI5LTIwYmUtNDU3Ny1hNGEzLWEzMzExZmEzODdkMS5wbmc_WC1BbXotQWxnb3JpdGhtPUFXUzQtSE1BQy1TSEEyNTYmWC1BbXotQ3JlZGVudGlhbD1BS0lBVkNPRFlMU0E1M1BRSzRaQSUyRjIwMjQwNzMxJTJGdXMtZWFzdC0xJTJGczMlMkZhd3M0X3JlcXVlc3QmWC1BbXotRGF0ZT0yMDI0MDczMVQwMDE2MDJaJlgtQW16LUV4cGlyZXM9MzAwJlgtQW16LVNpZ25hdHVyZT04MDBjYjBjZjU2Y2IzZjQ4ZDFiMjY3ZTg4ZjZmYWU0YjI2NGQyODEyODQ2MzFiNTdmZDVmZTJkODNiYmM5ZDc4JlgtQW16LVNpZ25lZEhlYWRlcnM9aG9zdCZhY3Rvcl9pZD0wJmtleV9pZD0wJnJlcG9faWQ9MCJ9.7pwBPSap_rH-kevBOaCl7HPk_WfVquvMz4OK-EWp3bo)
Assets with custom integration package:
![2024-05-16_16-08](https://private-user-images.githubusercontent.com/526307/331507491-63fcaafd-7a17-4ede-b7f1-9ac19c9dfb3a.png?jwt=eyJhbGciOiJIUzI1NiIsInR5cCI6IkpXVCJ9.eyJpc3MiOiJnaXRodWIuY29tIiwiYXVkIjoicmF3LmdpdGh1YnVzZXJjb250ZW50LmNvbSIsImtleSI6ImtleTUiLCJleHAiOjE3MjIzODUyNjIsIm5iZiI6MTcyMjM4NDk2MiwicGF0aCI6Ii81MjYzMDcvMzMxNTA3NDkxLTYzZmNhYWZkLTdhMTctNGVkZS1iN2YxLTlhYzE5YzlkZmIzYS5wbmc_WC1BbXotQWxnb3JpdGhtPUFXUzQtSE1BQy1TSEEyNTYmWC1BbXotQ3JlZGVudGlhbD1BS0lBVkNPRFlMU0E1M1BRSzRaQSUyRjIwMjQwNzMxJTJGdXMtZWFzdC0xJTJGczMlMkZhd3M0X3JlcXVlc3QmWC1BbXotRGF0ZT0yMDI0MDczMVQwMDE2MDJaJlgtQW16LUV4cGlyZXM9MzAwJlgtQW16LVNpZ25hdHVyZT01M2UxZjBhNGJjNWZjZDlmY2JkZjRjYTNmNWU5Y2Y4ODhmNTNmZjQyOTE4ZTg2MmQ1MDE2MmViYTAwZDk5NjU0JlgtQW16LVNpZ25lZEhlYWRlcnM9aG9zdCZhY3Rvcl9pZD0wJmtleV9pZD0wJnJlcG9faWQ9MCJ9.04kv4T5eh7uWwVw0TqeW_etJRlI8o7DKAkV5LL__0Rk)
Index templates before installing custom version
Index templates after installing custom version
The text was updated successfully, but these errors were encountered: