Loading…
Loading…
Every configuration change in SOAP-2-REST by Specaria is captured as an audit event. The audit trail answers the governance question — who changed what, when,…
Every configuration change in SOAP-2-REST by Specaria is captured as an audit event. The audit trail answers the governance question — who changed what, when, and what did it look like before and after — and it shares the same UI as the rest of observability, so operational and governance questions are answered in one place.
Each audit event records:
Sensitive values are never written to the audit trail in plaintext — backend credentials, for example, are recorded as a change to the credential metadata (set / last-updated), never the secret itself. See backend credential encryption.
Audit events are mandatory for every mutating control-plane action, including:
If a change can affect how traffic is converted or who can administer the platform, it is audited.
GET /admin/v1/audit-events returns audit history, paged server-side. Filters:
window — 15m / 1h / 24h / 7d / 30d / 60d, or a custom start/end range
inside the retained window.page / pageSize.The response carries items[] plus page, pageSize, totalItems, and totalPages. See the
Admin API.
Audit events are retained for 60 days by default, and the window is configurable to your policy — the same retention model as the rest of the platform's telemetry. See Data retention.