Export API v2: Streamline Large Log Data Exports

The Mezmo platform improves how teams use logs to help with debugging and troubleshooting. However, having fast access to actionable data isn’t the only value you can get from logs. There’s a lot of additional value in analyzing historical log data to understand long-term trends. For example, customers can use log data as a way to represent security logs for user actions and benefit from visualizing them in third-party software or within a telemetry pipeline. For this kind of analysis, our users require access to log data in a flexible manner, which is why we created our Export API—enabling users to define a time period of logs to be exported out and used in other applications.

However, while this feature was helpful for users that require access to log data in other platforms, we realized that the experience of piecing multiple export requests together was frustrating. Furthermore, using only timestamps to stitch together requests made it possible to lose logs if not careful.

To solve those issues and meet the needs of our users, we’re excited to introduce our newest version of the Mezmo Export API. This includes two major improvements:

• We introduced pagination IDs to help with queries that export a large number of logs, making it easier to stitch together large exports of log data.
• In addition, the output format is now in JSON, which allows for a more user-friendly experience and simplifies log rotation or integration within existing observability systems.

For observability engineers, this new Export API enhances visibility by connecting raw log data directly to other monitoring or analytics tools, ensuring more seamless end-to-end insights.

How to Get Started

Check out our newest Export API by trying it out live within our documentation. You will also find all the information you need regarding query parameters, as well as some best practices, tips, and tricks for integrating the Export API into your telemetry pipeline.