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

Reporting feature does not work when setting stack.templates.enabled: false in Elasticsearch #201281

Open
tsullivan opened this issue Nov 21, 2024 · 4 comments
Assignees
Labels
bug Fixes for quality problems that affect the customer experience Team:SharedUX Team label for AppEx-SharedUX (formerly Global Experience)

Comments

@tsullivan
Copy link
Member

tsullivan commented Nov 21, 2024

Since we have begun leveraging Elasticsearch to create a data stream for Reporting, we have begun depending on Elasticsearch to also install the mapping template for the reporting data. See #176022 and elastic/elasticsearch#97765.

Elasticsearch has a setting called stack.templates.enabled. If disabled, the mapping templates for Reporting, and other features, will not be installed.

This issue is to decide what the expected behavior is for Reporting when the setting is disabled.

@tsullivan tsullivan added the Team:SharedUX Team label for AppEx-SharedUX (formerly Global Experience) label Nov 21, 2024
@elasticmachine
Copy link
Contributor

Pinging @elastic/appex-sharedux (Team:SharedUX)

@tsullivan tsullivan added the bug Fixes for quality problems that affect the customer experience label Nov 21, 2024
@tsullivan
Copy link
Member Author

tsullivan commented Nov 21, 2024

Ping @dakrone The mapping templates were installed in elastic/elasticsearch#97765.

What is the typical expectation for features that depend on system mapping templates, when Elasticsearch is configured with stack.templates.enabled: false ?

@jsevidal13
Copy link

In case 01786448, the customer upgraded from 8.14 to 8.15.4, and stack.templates.enabled was set to true. They were unable to run reports because a new .kibana-reporting index kept recreating itself.

They ended up resolving the issue by deleting the .kibana-reporting index, but then ALSO had to recreate the .kibana-reporting index template. In this case, it did not get created automatically even with stack.templates.enabled set to true.

Just documenting here for reference.

@tsullivan
Copy link
Member Author

tsullivan commented Nov 25, 2024

We should update the documentation of Reporting requirements to state that Reporting depends on that setting to be enabled in Elasticsearch.

Likewise, we should also update documentation in https://www.elastic.co/guide/en/elasticsearch/reference/current/index-management-settings.html#stack-templates-enabled to state that modifying the setting affects Reporting's templates.


the customer upgraded from 8.14 to 8.15.4, and stack.templates.enabled was set to true. They were unable to run reports because a new .kibana-reporting index kept recreating itself.

We should retroactively document this change for Reporting in Kibana's changelog of releases.


cc @jsevidal13 @dakrone

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Fixes for quality problems that affect the customer experience Team:SharedUX Team label for AppEx-SharedUX (formerly Global Experience)
Projects
None yet
Development

No branches or pull requests

3 participants