limit_mu

Client name associated with the client_id, when available. May be empty string.

Description of the event. This can also contain a description of the issue for failure logs.

The name of the environment where the event occurred

The hostname associated with the request. For forwarded requests, this should resolve to the original hostname. For failure logs, this may include invalid hostnames.

The IP address associated with the request. For an auth related log this should be the end user IP. For a machine-to-machine auth flow this should be the IP of the computer doing the authentication. For management logs like sapi and mgmt_api_read this should be the IP of the admin using the manage dashboard.

Log id

Tenant name

Blocked Account - Too many attempts or signups

Client related to the API call. Clients are also called applications. The underlying application may not be owned by your tenant and may not be accessible. For failure logs, this may be a valid ID, an invalid one, or any ID.

Name of the connection, when available. The connection here matches the connection_id field.

ID of the connection on which the auth flow is happening or connection of the user doing the action, when applicable. For failure logs this field may contain an invalid ID.

The date when the event occurred in ISO 8601 format

ID for the user as reported by the IdP.

Whether the request originated from a mobile device. Only present when user_agent is available.

The user_agent behind this log, when available

ID of the user behind the auth flow, or of the user executing the action, whichever applies. For machine to machine auth flows, this field may contain an empty string. For failure logs, the value may be a valid ID, an invalid ID, or empty string

Username of the user related to the ID is shown in user_id, when available. For failure logs, the value may be a valid username, an invalid username, or empty string.