Skip to main content

Documentation Index

Fetch the complete documentation index at: https://altostrat.io/docs/llms.txt

Use this file to discover all available pages before exploring further.

Audit Logs help you answer operational questions about activity in your SDX workspace: who made a change, when it happened, what area of the platform it touched, and whether the request succeeded.

​
Prerequisites

  • You have permission to view audit logs for the workspace.
  • You know the approximate time range, user, resource, or event type you want to investigate.

​
When to Use Audit Logs

Use audit logs when you need to:
  • Investigate an unexpected policy, site, or user change
  • Review access before or after an incident
  • Confirm whether a request succeeded or failed
  • Support change management or compliance review
  • Correlate portal activity with monitoring and fault events

​
Search and Filter

Start with the narrowest information you already know.
  1. Open Settings and select Audit Logs.
  2. Set the time range around the event.
  3. Filter by user, status, method, or event details when available.
  4. Review failed requests and error responses first if you are investigating breakage.
  5. Compare the timestamp with related Fault Logging, workflow runs, or notification events.

​
Investigation Pattern

For a suspected configuration regression:
  1. Identify when the behavior changed.
  2. Search audit logs around that time.
  3. Look for policy, site, team, role, script, or workflow changes.
  4. Confirm whether the actor and action were expected.
  5. Use the relevant feature page to inspect the current configuration.

​
Good Practices

Use named users for operational work instead of shared accounts. Give users roles that match their responsibilities. When a user changes teams or leaves, update their access promptly so future audit review remains clear.
Audit logs are most useful when paired with least-privilege roles. See User and Team Management for access control guidance.