[FEATURE] Add frequency of Cleanuparr health checks in settings #79

New Issue

giteasync · 2025-10-09T16:57:55-05:00

giteasync commented

2025-10-09 16:57:55 -05:00

Originally created by @nibble4bits on GitHub.

What would you like to see implemented next?

In 2.0.0 - it is doing a Cleanuparr health check once per minute and there is no way to change this in the settings. Can you add an option to customize the frequency of doing the health checks so the log is not completely filled with health checks? Thanks!

Originally created by @nibble4bits on GitHub. ### What would you like to see implemented next? In 2.0.0 - it is doing a Cleanuparr health check once per minute and there is no way to change this in the settings. Can you add an option to customize the frequency of doing the health checks so the log is not completely filled with health checks? Thanks!

giteasync added the

enhancement

planned

labels 2025-10-09 16:57:56 -05:00

giteasync commented

2025-10-09 16:57:56 -05:00

@Flaminel commented on GitHub:

While this has not been fully addressed yet, v2.2.0 improves this by:

increasing the interval to 5min up from 1min
decreasing the log level to Debug down from Info for successful health checks; failed health checks will show up as warnings

@Flaminel commented on GitHub: While this has not been fully addressed yet, `v2.2.0` improves this by: - increasing the interval to 5min up from 1min - decreasing the log level to `Debug` down from `Info` for successful health checks; failed health checks will show up as warnings

giteasync commented

2025-10-09 16:57:56 -05:00

@Flaminel commented on GitHub:

@rmcgirr83 The health check endpoint has nothing to do with how often the download client health checks are performed. What you are using is an aggregated status coming from both Cleanuparr itself and the current status of the download clients, so it return the current status and does not trigger a re-check. Checking the download client might take a long time, while the health check endpoint should be quite fast.

@Flaminel commented on GitHub: @rmcgirr83 The health check endpoint has nothing to do with how often the download client health checks are performed. What you are using is an aggregated status coming from both Cleanuparr itself and the current status of the download clients, so it return the current status and does not trigger a re-check. Checking the download client might take a long time, while the health check endpoint should be quite fast.

giteasync commented

2025-10-09 16:57:56 -05:00

@rmcgirr83 commented on GitHub:

Seems docker healthcheck is being ignored? I have it set for 10 minutes in my compose but the healthcheck still triggers every minute.
healthcheck: test: ["CMD", "curl", "-f", "http://localhost:11011/health"] interval: 10m # Check every 10 Minutes timeout: 10s # Allow up to 10 seconds for response start_period: 30s # Wait 30 seconds before first check retries: 3 # Mark unhealthy after 3 consecutive failures

@rmcgirr83 commented on GitHub: Seems docker healthcheck is being ignored? I have it set for 10 minutes in my compose but the healthcheck still triggers every minute. `healthcheck: test: ["CMD", "curl", "-f", "http://localhost:11011/health"] interval: 10m # Check every 10 Minutes timeout: 10s # Allow up to 10 seconds for response start_period: 30s # Wait 30 seconds before first check retries: 3 # Mark unhealthy after 3 consecutive failures`

giteasync referenced this issue

2025-10-09 17:00:42 -05:00

[PR #79] [MERGED] Add option to ignore specific downloads #266

Sign in to join this conversation.

1 Participants

Notifications

Due Date

No due date set.

Dependencies

No dependencies set.

Reference: starred/Cleanuparr#79