- Purpose
- Make every integration action attributable and reconstructable.
- Prerequisites
- Centralised log store
- Architecture
- Correlate by request id across portal, integration layer and Integration Lab.
Configuration
| Retention | 12 months (customer policy) |
Implementation steps
- 01Log request id, actor, resource, outcome
- 02Never log tokens, secrets or full payload PII
- 03Alert on repeated authorisation failures
Examples
Log line
json
{ "ts": "2026-08-24T09:12:06Z", "request_id": "req_01H8ZQF3", "actor": "integration-client", "action": "assignment.create", "external_id": "WC-8291", "status": 201 }Testing procedure
- Reconstruct a full purchase-to-certificate journey from logs alone
Troubleshooting
Cannot correlate
Propagate a single request id end to end.