Service API Audit Trail
Every authenticated request and failed auth attempt is recorded per-app. Review traffic from Applications → Manage → Activity.
In this article you'll learn about What is recorded, then explore Where to find it, and finally review Best practices.
What is recorded
Every authenticated request, plus failed authentication attempts, is recorded in the per-app audit log. The log captures method, path, status, latency, client IP and timestamp for the last 24 hours of traffic.
Where to find it
Tenant admins can review the audit log from Dashboard → Security & Apps → Applications → Manage → Activity. The Activity tab surfaces:
- Total requests, success count, error count, and average latency.
- Error code breakdown.
- The 20 most recent requests with full method, path, status, latency, IP and timestamp.
Best practices
Use the audit log to spot misconfigurations before they reach production traffic: a spike in SERVICE_AUTH_SECRET_MISMATCH usually means a stale secret in your fleet, and a spike in SERVICE_IP_NOT_ALLOWED means your egress IP changed without an allowlist update.
For longer retention, mirror the data into your own observability stack via the upcoming webhooks integration.