You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Add an environment variable COLLECTOR_RUNNING_TASKS_HEALTHY_THRESHOLD and report the container as unhealthy if the number of running tasks (as tracked by Collector.running_tasks) exceeds the threshold.
Tasks:
Add the environment variable to base_collectors.config
Default value: 120. Rationale using the default config values: the collector starts max 30 tasks every 20 seconds that timeout after max 120 seconds so the theoretical maximum number of running tasks is (120/20) x 30 = 180. Use 2/3 of that. Add the rationale to the code and docs.
Change the Collector.record_health method to not update the timestamp when the number of running tasks exceeds the threshold.
The text was updated successfully, but these errors were encountered:
fniessink
changed the title
Report the collector container as unhealthy if the number of running tasks is high
Report the collector as unhealthy if the number of running tasks is high
Apr 16, 2024
Add an environment variable
COLLECTOR_RUNNING_TASKS_HEALTHY_THRESHOLD
and report the container as unhealthy if the number of running tasks (as tracked byCollector.running_tasks
) exceeds the threshold.Tasks:
base_collectors.config
Collector.record_health
method to not update the timestamp when the number of running tasks exceeds the threshold.The text was updated successfully, but these errors were encountered: