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.

Sign up for GitHub

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

Jump to bottom

[Reporting] Document that disabling Reporting completely isn't recommended #120996

Closed
tsullivan opened this issue Dec 9, 2021 · 1 comment · Fixed by #125175
Closed

[Reporting] Document that disabling Reporting completely isn't recommended #120996

tsullivan opened this issue Dec 9, 2021 · 1 comment · Fixed by #125175
Labels
bug Fixes for quality problems that affect the customer experience impact:medium Addressing this issue will have a medium level of impact on the quality/strength of our product. loe:medium Medium Level of Effort

Comments

@tsullivan
Copy link
Member

See #120995

When a user sets xpack.reporting.enabled: false in the kibana.yml, it creates a risk for Reporting to break down in other instances that have the Reporting plugin enabled.

The documentation on Reporting settings should state that instead of setting xpack.reporting.enabled: false, they should consider setting xpack.reporting.queue.pollEnabled: false instead.

It's required to use xpack.reporting.queue.pollEnabled: false on the instances where Reporting should be disabled, if there are other instances that have Reporting enabled.

#120995 will make Kibana instances fail to start up if they have Reporting disabled in an environment where other instances have Reporting enabled.
@tsullivan tsullivan added the bug Fixes for quality problems that affect the customer experience label Dec 9, 2021
@botelastic botelastic bot added the needs-team Issues missing a team label label Dec 9, 2021
@elasticmachine
Copy link
Contributor

Pinging @elastic/kibana-app-services (Team:AppServicesSv)

@botelastic botelastic bot removed the needs-team Issues missing a team label label Dec 15, 2021
@exalate-issue-sync exalate-issue-sync bot added impact:needs-assessment Product and/or Engineering needs to evaluate the impact of the change. loe:small Small Level of Effort impact:medium Addressing this issue will have a medium level of impact on the quality/strength of our product. and removed impact:needs-assessment Product and/or Engineering needs to evaluate the impact of the change. labels Dec 16, 2021
@exalate-issue-sync exalate-issue-sync bot added loe:medium Medium Level of Effort and removed loe:small Small Level of Effort labels Feb 3, 2022
@tsullivan tsullivan mentioned this issue Feb 10, 2022
Merged
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
bug Fixes for quality problems that affect the customer experience impact:medium Addressing this issue will have a medium level of impact on the quality/strength of our product. loe:medium Medium Level of Effort
Projects
None yet
Milestone
No milestone
Development

Successfully merging a pull request may close this issue.

[Reporting/Docs] Add clarity to reporting concepts tsullivan/kibana
3 participants
@kertal @tsullivan @elasticmachine