Operations
Monitor access point health, diagnose delivery and certificate failures, and find the right audit and recovery records.
Monitor SDK Access Point from the private listener, structured runtime events and PostgreSQL state. Check Digg’s service status when DNS or metadata failures affect more than one transfer. Digg’s SDK service status
Check service health
Section titled “Check service health”Use the configured private diagnostic certificate to call the health endpoints over mTLS.
| Check | What to look for |
|---|---|
GET /health/live |
HTTP 200 means the service answered the liveness request. |
GET /health/ready |
HTTP 200 means the readiness checks passed. HTTP 503 can indicate database or discovery failure. |
X-Database-Status |
UP or DOWN from the readiness database probe. |
X-SMP-Discovery-Status |
Latest discovery diagnostic. It starts at NOT_CHECKED and records successes or categorized failures as lookups occur. |
Readiness describes the local instance and the latest discovery outcome. Use a synthetic peer exchange to check delivery, a signed receipt and inbound retrieval.
Monitor the service
Section titled “Monitor the service”Track readiness, certificate expiry, repeated retries, terminal failures, unresolved inbox deliveries, log collection and PostgreSQL capacity. Use transport API responses for current application state, and protect audit extracts and signed evidence separately from operational logs. Logging and audit
Diagnose common failures
Section titled “Diagnose common failures”| Reason or symptom | What to check |
|---|---|
AUTH_DENIED |
Confirm the private client identity belongs to the configured tenant and that the API bearer credential matches. |
CLIENT_CERTIFICATE_REJECTED, TLS_TRUST_FAILURE |
Identify the affected listener, then check the certificate chain, validity, trust store and revocation. |
CERTIFICATE_REVOKED, CERTIFICATE_STATUS_NOT_CURRENT, CERTIFICATE_STATUS_UNAVAILABLE |
Check the issuer’s CRL, publication time and endpoint reachability. Replace a revoked certificate before retrying. |
DNS_FAILURE, HTTPS_FAILURE |
Check the configured SML zone, DNS resolution and the connection to SMP. |
METADATA_SIGNATURE_FAILURE, ROUTE_CERTIFICATE_FAILURE |
Check metadata signing trust and the receiver’s published AS4 certificate. |
AS4_HEADERS_MISMATCH, AS4_PROTOCOL_REJECTED, AS4_SECURITY_REJECTED |
Compare transport profiles and use the protected journal to identify the affected message and attempt. |
DATABASE_UNAVAILABLE, BOUNDARY_AUDIT_UNAVAILABLE |
Check PostgreSQL, database TLS, service credentials, free space and runtime role privileges. |
RUNTIME_DATABASE_POLICY_REFUSED during Docker start |
Check the runtime login’s actual PostgreSQL memberships, ownership and grants. The installer checks the effective privileges. |
For a single transfer, keep the original transport ID, correlate the attempt in the journal, then decide whether to wait for automatic retry, reconcile with the peer or escalate. Recovery diagnostics
In this section