Governance Service Operations

Operators should monitor Governance Service as part of the full Governance Platform. User-facing issues often come from dependency problems, configuration mismatches, or missing permissions.

Readiness Checks

Governance Service exposes a liveness probe, a readiness probe, and an authenticated probe that exercises the Auth Service token path. The readiness probe reports whether the service can reach the platform database; it does not check object storage, Integrity Service, or the PDF generation service.

Because readiness covers only the database, confirm the remaining dependencies separately: use the authenticated probe for Auth Service, and check object storage, Integrity Service, and the PDF generation service through their own health signals before declaring the deployment ready.

If readiness fails, check the deployment status and service logs before asking users to retry.

Before Upgrades

Before upgrading, back up platform data, preserve current deployment values, and review release notes for migrations or behavior changes. Avoid starting an upgrade while large evidence imports, report generation, or credential workflows are in progress.

Common Operational Symptoms

• Users cannot access projects: check Auth Service health and membership assignments.
• Attachments fail: check object storage configuration and permissions.
• Credentials fail: check Integrity Service health and connectivity.
• Reports fail: check PDF generation service health.
• Indicator evaluations do not appear: check the event integration, project context, and active indicator applications.

Escalation Information

When escalating, include the project, affected workflow, approximate time, user role, and whether the issue affects all users or a single project. Do not include sensitive attachment contents unless support explicitly requests them through an approved channel.