Where to find logs
Logs are accessible from several places across the platform:| Location | What it shows |
|---|---|
| Tasks | Logs for each individual task, including error messages, transformer output, and processing details. Accessible from the Tasks overview or directly from a Route, Incoming, or Outgoing detail page. |
| HTTP Proxies | History of all past requests processed by a specific HTTP Proxy. Found under the Logs tab on the HTTP Proxy detail page. |
| Webhooks | History of all past requests received by a specific Webhook. Found under the Logs tab on the Webhook detail page. |
| Storages | History of entity-level events (creating, updating, and deleting entities) when logging is enabled. Found under the Logs tab on the Storage detail page. |
| Email Servers | Logs of email send attempts when logging is enabled on the Email Transformer. Configurable per event: sender, recipients, and message body. |
| Queue | Processing and throughput times per job. Found under More > System > Queue. Useful for diagnosing timing and performance issues. |
How to use logs
Logs are most useful for:- Debugging failed tasks –– a task with a Failed status will have a log entry explaining what went wrong, such as a
500error from the destination API or a misconfigured transformer. - Tracing data flow –– logs on tasks show the entity data at each stage of processing, making it possible to see exactly what data was sent and what came back.
- Monitoring Webhook and HTTP Proxy activity –– the Logs tab on these configurations shows every inbound request, useful for verifying that external systems are connecting correctly.
- Tracking Storage changes –– when entity-level logging is enabled on a Storage, you can see a full history of when entities were created, updated, or deleted and by which process.
Configuring logs
Logs in Alumio are not enabled globally –– each configuration type has its own logging settings that need to be enabled individually. Tasks and HTTP Proxies Task-level logs and HTTP Proxy request logs are available automatically. No additional configuration is required. Webhooks Webhook logging is enabled in the General tab of the Webhook configuration via the Enable logging checkbox. When enabled, the full incoming request data is logged each time the Webhook is called. Storages Logging on a Storage is configured in the Edit tab under the Enable logging for field. Three operations can be enabled independently:| Option | What it logs |
|---|---|
| Creating entities | Logs when a new entity is written to the Storage. |
| Updating entities | Logs when an existing entity is modified. |
| Deleting entities | Logs when an entity is removed from the Storage. |
| Option | What it logs |
|---|---|
| Email sender | Logs the sender address used for each email. |
| Email recipients | Logs the recipient addresses. |
| Email message | Logs the full email body. |
Log retention
- Queue records are retained for a maximum of 30 days or 1000 entries, whichever is reached first.
- Task and configuration logs –– for retention policies, check your environment settings or contact your Customer Success Manager.