Log Data Retention
Auth0 provides event logging capability and you can scan logs to identify event anomalies. Standard log retention period for Auth0 logs is determined by subscription level with the shortest period being 2 days and the longest period being only 30 days. Leveraging Auth0 support for integrating with external logging services allows you to retain logs outside of this timeframe, and will also provide for log aggregation across your organization.
To understand how you will use the Auth0 logs in your situation, review the log data retention period for your subscription level.
|Developer Pro||10 days|
You can implement an Auth0 log data export extension to send log data to an external log analytics service. For example, you can use log files for troubleshooting and detecting intermittent errors that may be hard to find with quality assurance testing. You may also want log data in case forensic data is ever needed for security purposes. Log data can also provide comprehensive analytics to help you see patterns in usage trends and anomaly detection triggers.
Auth0 extensions support following third-party services:
- Application Insights
- AWS Cloudwatch
- Azure Blob Storage
- Sumo Logic
You can also export logs to the following services using Auth0 Rules:
Rate limits exceeded and other errors
Auth0 provides a unique error code for errors reported when the rate limit is exceeded. You can set up automatic scanning of logs to check for rate limit errors so you can proactively address activity that hits rate limits before it causes too much trouble for your users. Auth0 also publishes error codes for other types of errors, and you can scan logs for authentication errors as well as errors from Auth0 Management API calls. (Management API error codes are shown below each call in the Management API Explorer).