Documentation ›Operations
OPERATIONS / SUMMARY

Daily inspection and issue history

Coverage, issue lifecycle, bounded logs and encrypted history.

What happens each day

GitHub Actions starts an inspection at 09:00 UTC. It checks available metrics, expected services and recurring error patterns, then publishes a report in the portal. GitHub may start scheduled work late; the report records the inspection window and delay. Owners can request another run after Google sign-in.

What issue statuses mean

A first failure is New. A repeated failure is Ongoing. A completed check without that failure makes it Remediated. A returning failure is Reopened. When the source cannot be checked, the issue stays Unverified instead of being declared fixed.

Read the coverage

Every report lists checked services, application relationships and missing instrumentation. A report with no findings is not proof of health if checks were incomplete. No email or messaging notifications are added.

ON THIS PAGE

THREE WAYS TO UNDERSTAND

Same system.
Your level of detail.

Switch reading modes above to find the explanation that fits.

Explore Expert →

Keep exploring

Public observability workspace

Public native dashboards, server navigation and owner changes.

↗
Backups & recovery

Protect existing data and know which recovery path to use.

↗