Logs: Improved request troubleshooting

We’re excited to announce the launch of Logs!

Logs is a new feature that provides a single pane-of-glass view for searching and understanding traffic sent across the Redox platform. It combines the previous Message, Transmission, Error, and Search pages of the Dashboard into a single page that offers additional insights such as status, type, and data lifecycle indicators to improve transparency and troubleshooting efficiency.

You can learn more about Logs here: https://developer.redoxengine.com/core-concepts/logs/

Rollout & Data Availability

Logs will be rolled out gradually to our customers, starting today. Once available for your organization, the Logs page will be accessible from the left navigation pane of the Redox Dashboard.

To start, available Logs data extends back to June 1st, 2021. This data set will continue to grow each day and reach the full 60 day historical range by July 31st, 2021 and retain this range thereafter.

Finally, the previous Message, Transmission, Error, and Search pages will remain accessible for a short time via a link on the top right of the Logs page. If you are not able to achieve a critical workflow with the new Logs interface and require these legacy views, we’d like to know! Please submit feedback using the form linked from the Logs page of the Dashboard.

Changelog

✅ Added:

New Logs page in the Dashboard
Platform API endpoints for exporting Logs metadata, detailed at https://redox-platform-api.readme.io/v1/reference/logs
Updated platform documentation at https://developer.redoxengine.com
All outgoing data requests from Redox have a new Meta.Logs[] property that contains Log objects with ID and AttemptID values

🔴 Removed (over time):

Message, Transmission, Error, and Search pages and list views
v0 /messages, /transmissions, and /errors Platform API endpoints
Meta.Message.ID and Meta.Transmission.ID values in Redox API requests are deprecated in favor of Meta.Logs[].ID