Logs
1. Overview
The Logs module in Sumo Ledger provides detailed system-level logging across three categories: Access Logs, Audit Logs, and Webhook Logs. These logs are essential for debugging, security auditing, and monitoring system activity.
Navigation: Logs
URL: https://las.ledger.raralabs.dev/log/list?log=access
2. Access Logs
The Access Logs tab records every gRPC service call made to the Sumo Ledger backend. This is the most detailed log, capturing all API interactions.
Table Columns
| Column | Description |
|---|---|
| Start Time | The timestamp when the request was received. |
| Elapsed Time (ms) | The time taken to process the request, in milliseconds. |
| Trace Id | A unique trace identifier for request tracing and correlation. |
| Grpc Service | The backend service that handled the request (e.g., ConfigService, TariffService, transaction_service.TransactionService). |
| Request Method | The specific method called on the service (e.g., ListAccessLog, ListPostings, FetchTariffVolumeByDate, ReportingGroupList). |
| IP Address | The IP address of the client that made the request. |
| requestHost | The host identifier of the requesting client. |
| RequestBody | A link to view the JSON request body. |
| ResponseBody | A link to view the JSON response body. |
Controls
- Search: Free-text search across log entries.
- View: Toggle table layout.
- Pagination (e.g.,
1-100 / 117807).
3. Audit Logs
The Audit Logs tab records all configuration changes made to the system, providing a complete audit trail of who changed what and when.
URL: https://las.ledger.raralabs.dev/log/list?log=audit
Table Columns
| Column | Description |
|---|---|
| Created At | The timestamp when the change was made. |
| Updated At | The timestamp of the last update. |
| Table Name | The configuration table that was modified (e.g., stages, configurations, feed_sources, feed_type_mappings, feed_types). |
| Action | The type of change: CREATE, UPDATE, or DELETE. |
| User Id | The ID of the user who made the change. |
| Before | A link to view the JSON state before the change. Displays "No Data" for CREATE actions. |
| After | A link to view the JSON state after the change. Displays "No Data" for DELETE actions. |
Controls
- Search: Free-text search across audit entries.
- View: Toggle table layout.
- Pagination (e.g.,
1-100 / 79664).
4. Webhook Logs
The Webhook Logs tab records all webhook deliveries triggered by process events.
URL: https://las.ledger.raralabs.dev/log/list?log=webhook
Table Columns
| Column | Description |
|---|---|
| Ref ID | The reference ID of the transaction or event that triggered the webhook. |
| Name | The name of the webhook configuration. |
| Status | The delivery status of the webhook. |
| Process Slug | The process that triggered the webhook. |
| Stage Slug | The specific stage within the process. |
| Resolved Payload | The resolved payload that was sent. |
| Failure Reason | The reason for failure, if the delivery failed. |
| Retry Count | The number of delivery retries attempted. |
| Sent At | The timestamp when the webhook was sent. |
| Created At | The timestamp when the webhook log entry was created. |
| webhook_id | The ID of the webhook configuration. |
Controls
- Filter: Dropdown filter for narrowing results.
- Search: Free-text search.
- View: Toggle table layout.
5. Best Practices
- Use Access Logs for performance debugging. The Elapsed Time column helps identify slow API calls.
- Use Audit Logs for compliance and change tracking. Before and After JSON views show exactly what changed in each configuration update.
- Monitor Webhook Logs for delivery failures. Failed webhooks may indicate endpoint issues or payload format problems.
- Use Trace IDs to correlate related log entries. A single user action may generate multiple service calls — the Trace ID links them together.
- Search by Request Method to find specific types of operations in the Access Logs.