Dashboard Logs

You can filter Application Logs by:

• Event type: The type of event (e.g., user.created, sign_in.completed). Supports trailing wildcards (e.g., sign_in.*).
• User ID: The ID of a user (e.g., user_123). Includes events the user triggered and events in which they were acted upon.
• Identifier: An email address, phone number, username, or Web3 wallet. The value must match the stored identifier exactly. If multiple users have it, events involving all of them are included.
• Actor: The user or API key that triggered the event.
• Subject: The ID of the resource being acted upon (e.g., a user ID or Organization ID).
• IP address: The IP address the event originated from.
• Trace ID: The distributed trace ID, for correlating events across systems.
• Device: The device ID.
• Session ID: The ID of a session (e.g., sess_123). Includes events triggered by requests made with that session, but excludes events triggered outside it, such as the sign-in that created it.
• Date range: The time window to search.

For a complete list of event types, see Supported events.

You can filter Email Logs by:

• Event type: The delivery outcome or interaction (e.g., bounced, delivered).
• Recipient: The recipient's email address.
• IP address: The IP address associated with the event.
• Message ID: A specific message, to follow every event for it.
• Date range: The time window to search.

For a complete list of event types, see Supported events.

You can filter Admin Logs by:

• Event type: The type of event (e.g., oauth_application.updated, domain.created). Supports trailing wildcards (e.g., oauth_application.*).
• Instance: The instance the action targeted.
• Application: The application the action targeted.
• Actor: The actor that triggered the event — a Dashboard user, an instance Secret Key⁠, or a Platform API access token.
• IP address: The IP address the action originated from.
• Date range: The time window to search.

For a complete list of event types, see Supported events.