Track info about successful executions of reload tasks #870
Closed
mountaindude
started this conversation in
Ideas
Replies: 1 comment
-
|
Released as part of 9.3.0. |
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
So far Butler has only tracked failed reloads.
These are probably (hopefully!) a lot more rate than successful reloads and often also motivate immediate attention/investigation.
Successful reloads are however also interesting.
For example, by tracking start- and end-time for successful reloads, we can create real-time distribution charts showing how long the reload task needed for each of its execution.
Having access to the time when apps finish reloading can also be used for schedule monitoring, i.e. monitoring requirements such as "App X should be reloaded no later than 09.00 on weekdays".
The scheduler logs contain a fair bit of INFO level data around scheduled reloads.
The full set of entries look like this:
The
Entering execute of reload sequence using EngineConnectionHandle...message could be used to track the start time for a reload. Using this message would let us capture the time when the app starting reloading in the engine, excluding time spent in queue.The message
Task finishedcould be used to track reload end time.As a first step, capture
Task finishedto get a notification when a task is finished reloading, then get details about the last execution from the QRS API, using the reload task ID from the reload-finished-event.Beta Was this translation helpful? Give feedback.
All reactions