Python logging and exit status in a scheduled job
A complete Python example sends the result to stdout, records an exception once and returns the failure status its scheduler needs.
Guides, news and explanations about AI and reliable systems.
Not sure where to begin? Choose a short reading path, or browse at your own pace.
A complete Python example sends the result to stdout, records an exception once and returns the failure status its scheduler needs.
A misrouted support ticket shows how automated decisions affect customers and what a usable correction path requires from the people responsible.
A worker restart shows how AIOps can select a repair, reconcile a lost response and check whether customer work recovers.
Run a complete JSON-to-JSON Python example, then distinguish a measured error rate from an incomplete regional collection.
An unfinished worker operation connects event fields, collection loss and search permissions to the responder’s next retry decision.
Faster incident-update drafts can save time or move work into review. The business case depends on the cost of the accepted update.
Primary shifts, specialist help, absence coverage and recovery time all contribute to the service an on-call calendar promises.
A downloadable Markdown template and a worked database-connection investigation show how observations lead to mitigation and recovery checks.
Images package processes and Kubernetes reconciles their deployment. Probes, resource settings and completed jobs reveal different stages of the service.
A backup-failure alert illustrates the gap between shipping a postmortem action and giving its recipient the access needed to respond.
A vacation backup who can receive pages but cannot perform recovery shows why coverage must transfer access, knowledge and workload together.
Repeated night work affects the next day’s capacity. Immediate relief and repairs to recurring demand have different jobs in a sustainable rotation.