Logs
Overview
The Logs page provides visibility into system activity, security events, and technical issues.
Monitor user activity, track login attempts, identify security events, and detect SDK or API errors.
Log Types
Record user and system actions related to access and authentication. Used for security monitoring, user activity tracking, and compliance.
Provide technical insight into errors and issues occurring during SDK or API usage. Help identify integration issues and troubleshoot errors.
Audit Logs
What Are Audit Logs?
Audit Logs record user and system actions related to access and authentication.
These logs are mainly used for:
- Security monitoring
- User activity tracking
- Compliance and auditing
Audit Log Events
The following events are recorded:
- Login success
- Login failure
Audit Log Information
Each audit log entry may include:
- User identifier
- Action performed
- Date and time
- IP address (if applicable)
- Result (success or failure)
Threat Logs
What Are Threat Logs?
Threat Logs provide technical insight into errors and issues occurring during SDK or API usage.
These logs are intended to help:
- Identify integration issues
- Troubleshoot SDK and API errors
- Track error trends across versions
What Is Recorded in Threat Logs
Threat Logs may include:
- Error type
- Error message
- SDK or API version
- Date and time of occurrence
- Source (SDK or API)
When Threat Logs Are Created
Threat logs are generated when:
- An SDK error occurs on a device
- An API request fails unexpectedly
- An integration encounters a runtime or validation error
Access & Permissions
Key Notes
Important Information
- 🔒 Logs are read-only and cannot be modified
- 📚 Historical logs are retained for auditing purposes
- 🛡️ Threat logs do not expose sensitive customer data
- ⏰ Log timestamps reflect system time
Updated 20 days ago