[TW#25595] Suggestion: Task watchdog to log timestamp since boot

[nkolban]

This is a suggestion issue for discussion and/or potential enhancement.

While looking at the logging messages from the task watchdog (here are a few):

Task watchdog got triggered. The following tasks did not reset the watchdog in time:
 - IDLE (CPU 0)
 - My Task (CPU 0/1)
Tasks currently running:
CPU 0: Hard Loop
Task watchdog got triggered. The following tasks did not reset the watchdog in time:
 - IDLE (CPU 0)
 - My Task (CPU 0/1)
Tasks currently running:
CPU 0: Hard Loop
Task watchdog got triggered. The following tasks did not reset the watchdog in time:
 - IDLE (CPU 0)
 - My Task (CPU 0/1)
Tasks currently running:
CPU 0: Hard Loop

It suddenly dawned on me that we aren't logging the time of detection. Thinking this through, if I am diagnosing a puzzle, it may be useful to be able to correlate watchdog events being logged with the time that those events are detected. I realize we might not know wall clock times but even seeing that watchdogs are firing for a period of 1 minute every 30 minutes might be useful information during diagnosis. If it would be possible, might we consider adding a timestamp to the watchdog emission messages? Perhaps we could expose a user customizable function that is called when a watchdog event occurs where we could log our own custom state and messages?