If you've ever been oncall for a production system, your number one wish is probably to not get paged in the middle of the night. For me it's the contrary, I seek the thrill.
Handling incidents is one of the quickest ways to deepdive into the entirety of a system. You get pulled into random group chats, you're up alone at 3 am squinting through obfuscated logs that make zero sense, you slide into a rabbithole of code history and try to find who to reach out to.
At my previous job, I was oncall for a system used in the US but maintained by a team in EU. I had no prior knowledge of the system but I volunteered cause I thought it would be fun. The team onboarded me and the first few days were challenging; denied access here and there, unfamiliarity on who to ping when things go wrong (it's a big company), trials and errors for different thresholds for the monitoring alerts. There would be at least 2-3 pages a day.
On the last day of my 5-day rotation, things were finally calm. They must've fixed everything in EU time, I thought. But it was a little too quiet. I checked our monitoring dashboard to peek on the server error rates. There were small spikes here and there but I didn't get paged. Huh, that was atypical. So I checked the dashboard for any user complaints. No reports.
That was too good to be true.
I played around with the system, nothing seemed odd. Then I tried filing a feedback from the system. Bingo. Our feedback reporting tool was broken.
Had I not been suspicious of the silence, it would've stayed broken, and we would've missed a few incidents that day.
If your infant is crying, it's business as usual. If they suddenly stop crying, check in on them. Silence is a strong signal, act on it.