Skip to content

Understanding Trail Logs

Trail logs record system-wide audit data across your entire Vidos infrastructure. Unlike usage logs which are specific to individual service instances, trail logs capture broader administrative and operational events at the account level, providing organization-wide visibility into system operations.

Each trail log entry records:

  • Account-level activities: Actions taken across your account
  • Request details: The HTTP method, path, headers, query parameters, and authentication context
  • Response details: The status code, response headers, and response body content
  • Cross-service context: Which service processed the request
  • Audit context: Complete record of who did what and when

Trail logs capture system operations without being tied to a specific instance, enabling you to see patterns and activities across your entire deployment.

Trail logs are ingested in near real time but may take up to 5 minutes to appear after an operation completes. Treat brief gaps as ingestion delay rather than missing data.

Trail logs are scoped to your entire account:

  • Organization-wide visibility: See activities across all services and regions
  • Cross-service patterns: Understand interactions between services
  • Account-level audit trail: Maintain compliance and security records
  • System-wide troubleshooting: Correlate activities across instances

This account-scoped design enables compliance auditing, security investigation, and understanding system behavior at the organizational level.

Trail logs are designed for queries like:

  • “What administrative operations occurred in my account over the past week?”
  • “Show me all requests to any service instance in my account that returned errors”
  • “What was the authentication method distribution across all my services?”
  • “Which services processed the most requests in this time period?”
  • Instances: Individual service instances that contribute to trail logs
  • Usage Logs: Instance-specific operational logs