[GH-ISSUE #712] Average execution time #512

New issue

Open

opened 2026-02-25 23:42:43 +03:00 by kerem · 1 comment

kerem commented

2026-02-25 23:42:43 +03:00

Owner

Originally created by @BeyondVertical on GitHub (Oct 5, 2022).
Original GitHub issue: https://github.com/healthchecks/healthchecks/issues/712

I would like to add an idea, that would be helpful for me:
In the detail page of a check an option to display the average execution time would be very helpful. Maybe even a graph that displays the execution time? Also a minimum or maximum value could be helpful.
This would help especially when adding new features to a script to see if it is not consuming too much time.
Thanks for your consideration and your work!

Originally created by @BeyondVertical on GitHub (Oct 5, 2022). Original GitHub issue: https://github.com/healthchecks/healthchecks/issues/712 I would like to add an idea, that would be helpful for me: In the detail page of a check an option to display the average execution time would be very helpful. Maybe even a graph that displays the execution time? Also a minimum or maximum value could be helpful. This would help especially when adding new features to a script to see if it is not consuming too much time. Thanks for your consideration and your work!

kerem added the

feature

label

2026-02-25 23:42:43 +03:00

kerem commented

2026-02-25 23:42:43 +03:00

Author

Owner

@ravench commented on GitHub (Jul 8, 2024):

I'd like to expand on the graph idea:
I just wanted to open a feature request for a execution time graph per check, similar to the system metrics on https://status.healthchecks.io/en/.

This would allow to easily see patterns and tendencies in execution times.
We use Healthchecks for backups a lot, there this would allow ud to easily spot:

Execution times growing over time
Reoccurring patterns (eg. certain weekdays' jobs taking longer/shorter than others)
Drops in execution times, indicating uncaught errors
How changes in our scripts affect performance

This helps improve our code, but also allows us to more easily set the correct grace period.

Currently, we manually check the execution times in the events log for each check. This works but is cumbersome.

@ravench commented on GitHub (Jul 8, 2024): I'd like to expand on the graph idea: I just wanted to open a feature request for a execution time graph per check, similar to the system metrics on <https://status.healthchecks.io/en/>. This would allow to easily see patterns and tendencies in execution times. We use Healthchecks for backups a lot, there this would allow ud to easily spot: - Execution times growing over time - Reoccurring patterns (eg. certain weekdays' jobs taking longer/shorter than others) - Drops in execution times, indicating uncaught errors - How changes in our scripts affect performance This helps improve our code, but also allows us to more easily set the correct grace period. Currently, we manually check the execution times in the events log for each check. This works but is cumbersome.