I'd like to be made aware of when a process was manually started and finished. I believe this info is available in logs, but if I must request to every user's endpoint, it would be good to know when the requests are done. Also adding in a failsafe so that incomplete requests are also notifications - so if a sync request has 14 users, 12 are fulfilled and 2 endpoints are unreachable, it would be interesting to know about it. This way admin and users can be made aware.
Desired Behavior
Add Notification Types so that all running jobs can be selected manually and individually into a list of notifications (grouped if the jobs start or finish at the same time).
Add a button so that incomplete jobs, once reported to Overseer, are established as "done, incomplete" so that if a job such as "Plex Watchlist Sync" must interrogate multiple user endpoints, if some cannot be interrogated they will fail after a predetermined timeout. The notification can then be issued saying "Done, incomplete (2 users not synced)".
Description
I'd like to be made aware of when a process was manually started and finished. I believe this info is available in logs, but if I must request to every user's endpoint, it would be good to know when the requests are done. Also adding in a failsafe so that incomplete requests are also notifications - so if a sync request has 14 users, 12 are fulfilled and 2 endpoints are unreachable, it would be interesting to know about it. This way admin and users can be made aware.
Desired Behavior
Add Notification Types so that all running jobs can be selected manually and individually into a list of notifications (grouped if the jobs start or finish at the same time). Add a button so that incomplete jobs, once reported to Overseer, are established as "done, incomplete" so that if a job such as "Plex Watchlist Sync" must interrogate multiple user endpoints, if some cannot be interrogated they will fail after a predetermined timeout. The notification can then be issued saying "Done, incomplete (2 users not synced)".
Additional Context
No response
Code of Conduct