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

[ResponseOps][Task Manager] Task Manager is unhealthy, the assumedRequiredThroughputPerMinutePerKibana (NaN) >= ... #204467

Open
pmuellr opened this issue Dec 16, 2024 · 2 comments
Assignees
Labels
bug Fixes for quality problems that affect the customer experience Feature:Task Manager Team:ResponseOps Label for the ResponseOps team (formerly the Cases and Alerting teams)

Comments

@pmuellr
Copy link
Member

pmuellr commented Dec 16, 2024

Noticed a new pattern in our messages like Task Manager is unhealthy, the (some stat)(value) ... - the value was NaN!

An example full message is

Task Manager is unhealthy, the assumedRequiredThroughputPerMinutePerKibana (NaN) >= capacityPerMinutePerKibana (1200)

Easily found in overview via the filter: log.logger: "plugins.taskManager" AND message: "NaN".

@pmuellr pmuellr added bug Fixes for quality problems that affect the customer experience Feature:Task Manager Team:ResponseOps Label for the ResponseOps team (formerly the Cases and Alerting teams) labels Dec 16, 2024
@elasticmachine
Copy link
Contributor

Pinging @elastic/response-ops (Team:ResponseOps)

@cedricdv
Copy link

cedricdv commented Jan 2, 2025

Seeing the same behavior after having set xpack.task_manager.capacity in kibana.yml. Before it was unset, now I have set it to capacity: 50 and I see following error:

Task Manager is unhealthy, the assumedRequiredThroughputPerMinutePerKibana (NaN) >= capacityPerMinutePerKibana (6000)

@doakalexi doakalexi self-assigned this Jan 13, 2025
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 Feature:Task Manager Team:ResponseOps Label for the ResponseOps team (formerly the Cases and Alerting teams)
Projects
None yet
Development

No branches or pull requests

4 participants