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] Problems with non-uniform enablement #120995

Closed
tsullivan opened this issue Dec 9, 2021 · 3 comments
Closed

[Reporting] Problems with non-uniform enablement #120995

tsullivan opened this issue Dec 9, 2021 · 3 comments
Labels
bug Fixes for quality problems that affect the customer experience (Deprecated) Feature:Reporting Use Reporting:Screenshot, Reporting:CSV, or Reporting:Framework instead impact:high Addressing this issue will have a high level of impact on the quality/strength of our product. loe:small Small Level of Effort needs-team Issues missing a team label

Comments

@tsullivan
Copy link
Member

tsullivan commented Dec 9, 2021 •
edited
Loading

Replaces: #119914

Problem: Reporting in Kibana breaks down when the Reporting plugin is disabled on some instances but enabled on others. This is an unsupported configuration, but unfortunately it seems the user realizes that it's unsupported after their report task instances are are deactivated - Task Manager marks the stored task instance as unrecognized.

The Diagnostic tool should check the status of the reporting tasks in Task Manager and make sure they are not unrecognized.
@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
This was referenced Dec 9, 2021
Closed
Closed
@elasticmachine
Copy link
Contributor

Pinging @elastic/kibana-reporting-services (Team:Reporting Services)

@elasticmachine
Copy link
Contributor

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

@botelastic botelastic bot removed the needs-team Issues missing a team label label Dec 9, 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:high Addressing this issue will have a high 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 9, 2021
This was referenced Dec 9, 2021
Closed
Closed
@tsullivan tsullivan changed the title [Reporting] Problems with Multi-Tenancy [Reporting] Problems with non-uniform enablement Dec 13, 2021
@lukeelmers lukeelmers mentioned this issue Jan 13, 2022
Open
@mikecote mikecote mentioned this issue Jan 17, 2022
Closed
@tsullivan tsullivan mentioned this issue Feb 17, 2022
Merged
1 task
@tsullivan
Copy link
Member Author

Resolved by #123963 (comment)

@sophiec20 sophiec20 added the (Deprecated) Feature:Reporting Use Reporting:Screenshot, Reporting:CSV, or Reporting:Framework instead label Aug 21, 2024
@botelastic botelastic bot added the needs-team Issues missing a team label label Aug 21, 2024
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 (Deprecated) Feature:Reporting Use Reporting:Screenshot, Reporting:CSV, or Reporting:Framework instead impact:high Addressing this issue will have a high level of impact on the quality/strength of our product. loe:small Small Level of Effort needs-team Issues missing a team label
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
3 participants
@tsullivan @sophiec20 @elasticmachine