An introduction to a new company and this one is called Mezmo, what what does this group really want to talk about? Well how about Telemetry and observability? First thing that would be discussed about Mezmo is that they have been around for a while. They were originally LogDNA and are now Mezmo and have been utilized for observability and telemetry for IBM for a long time:

Now telemetry data has a value but that value does not grow in the same amount as the linearly data of the telemetry consumption. So there is a gap between the value and the data.

Introducing Telemetry pipeline with Mezmo:

Top use cases for telemetry pipeline:

However the main goal of MezMo is to help you understand your data and have a deeper understanding of where your data is going and what it is doing. This is difficult for most organizations because data is specific to the use-case and they only use specific data for specific things without cross relationships between different use cases. Here is where Mezmo changes the game and compliments multiple providers under one umbrella:

Ok, so we know a bit about Mezmo, its demo time!

Looking at the data profiler we see the data coming through different integrations with Mezmo.

After validating where the data is coming from, they are able to parse between multiple different sources of data and validate what data should be needed and available for the different reasons.

My Thoughts:

I’m not big on telemetry but this is the second time I have heard a talk today at cloud field day, on the second group. So I’d say knowing where the data should be going, and how it should be consumed, pared down etc. Will continue to be a discussion. It’s good to hear that a large amount of this will be ran by Terraform because it allows users the ability to automate and orchestrate the solution from the ground up. This helps users understand the blocks of each part of the solution and have a better way to validate how they would be connected within their architecture. One thing I did not bring up was they have the ability to swap over to an “Incident” mode and start looking at debug logs so they can validate what happened, and why it happened. This is a really nice feature as it allows customers to validate the issue and fix it rather quickly. The last thought which is a small thing but really nice is the UI looks very clean and easy to utilize to track down the logs and pare it down to what you want to utilize. Good first viewing of Mezmo.