View actions performed by administrators using the Dashboard.
View operations performed via the Management API.
View authentications made by your users.
View troubleshooting and detecting intermittent errors that may be hard to find with quality assurance testing.
Capture forensic data for security purposes and to identify anomaly detection triggers.
Identify patterns in usage trends.
Check for authentication errors and Management API call errors.
Set up automatic log scanning to check for rate limit errors so that you can proactively address activity that hits rate limits before it impacts your users.
Correlate management API events to their initiating requests by matching
X-Correlation-IDheader values. (See Management API for details.)
Log usage examples
If a customer has raised a support ticket that they are unable to sign in to your service or application, you can verify in the logs that they have indeed tried, and are attempting in the manner they say they are. They may think it's a password issue, but you may discover they never completed setting up their multi-factor authentication (MFA).
Additionally, administrators can use logs to expose business metrics that can help:
Find prime times of usage for different regions.
Identify a target audience.
Detect patterns in user behavior that can be optimized.
Identify problematic actors by IP address.
Calculate frequency and type of Attack Protection triggers.
Logs can be helpful when debugging an issue, or setting up an integrations. You can use logs as a history of events to see where a flow may be broken, or where customers are getting confused.
You can also detect nefarious behavior or verify that Auth0 anomaly detection is being triggered during questionable behavior. We recommend searching the logs for specific events using our Dashboard or Management API directly. It can also be use to export logs to your preferred log processing systems, like Splunk or Sumo Logic, for deeper analysis over time.