The scope of the OpenTelemetry project encompasses how telemetry data is collected, processed, and transmitted. The OpenTelemetry project is not involved with how the data is stored, displayed, or used beyond the collection and transmission phases. The OpenTelemetry Collector is an application written in Go.

For this post, we’ll use a small Flask app that allows users to input a city name and they receive the current weather information for that city. We’ll make an API call to openweathermap.org to get the weather information for the city.

Within the technology stack used by developers today you would be hard-pressed not to find products and features that save time. Time-saving tools are crucial for developers because we look for ways to deliver production-ready code faster to keep up with the demands of our users and customers. We want to be able to identify, reproduce, and fix issues – fast.

Snapshot of the content that AppDynamics’ OpenTelemetry experts, Erwan Paccard and Severin Neumann find valuable.

At Mezmo, we see a massive opportunity to reduce Mean Time to Detection (MTTD) and Mean Time to Resolution (MTTR) by making log data more valuable and actionable. Today, we’re thrilled to announce the release of the Mezmo Exporter for OpenTelemetry- the first step in our continued work with the project to further simplify the ingestion of log data and make that data more actionable with enrichment of key OpenTelemetry attributes.