Finding scheduled events with no playback evidence.
Help operators notice when playback needs attention.
Where this work fits
The schedule said what should play. Reporting needed to know what did play, including when a device lost its connection or a prayer interrupted a track. Sending each record immediately was not always possible.
I built monitoring that compared expected playback with device records. It had to account for delayed evidence and interruptions before identifying a missed event. Reusing device lookups within a monitoring run also avoided repeating the same query for each check.
Notice when expected activity never arrives
Playback evidence found.
The observed event falls inside the configured window.
Keep the record until delivery succeeds.
Removing a record when sending started could lose it on failure. I retained unsent records on the device and removed the sent batch after success. Monitoring had a related timing problem: it needed to allow for delayed evidence before treating an expected event as missing.
The skills behind the work
- Scheduled jobs
- Run time-based work without waiting for a person to open the application.
- SQL
- Query and update relational data, with clear rules about which records a result represents.
- Monitoring
- Compare observed activity with expectations and surface conditions that need attention.
Unsent playback records could survive a restart and travel when connectivity returned. Monitoring made missed activity easier to investigate, with alert outcomes recorded separately from the detection itself.