The latest information about Mezmo products and features
Pipeline Destination

New Pipeline Destination: Google Cloud Operations

Kai avatar
Shared by Kai • July 25, 2024

Mezmo is pleased to announce the release of a new Pipeline Destination for Google Cloud Operations. For more information check out the topic Google Cloud Operations at docs.mezmo.com.

Pipeline Destination

New Pipeline Destination: Google Cloud PubSub

Kai avatar
Shared by Kai • July 25, 2024

Mezmo is pleased to announce the release of a new Pipeline Destination for Google Cloud PubSub. For more information check out the topic Google Cloud PubSub at docs.mezmo.com.

Pipeline Destination

New Pipeline Destination: Google Cloud Monitoring

Kai avatar
Shared by Kai • July 25, 2024

Mezmo is pleased to announce the release of a new Pipeline Destination for Google Cloud Monitoring. For more information check out the topic Google Cloud Monitoring at docs.mezmo.com.

Pipeline Feature

New Pipeline Feature: In-stream Alerts

Kai avatar
Shared by Kai • June 28, 2024

Mezmo is pleased to announce the availability of In-stream alerts for telemetry data. With this feature you can set alerts based on specific conditions for telemetry data on any Source, Destination, or Processor in your Pipeline. For more information, check out the topic In-stream Alerts at docs.mezmo.com.

Pipeline Feature

New Pipeline Feature: Data Archiving and Restoration

Kai avatar
Shared by Kai • May 29, 2024

Mezmo is pleased to announce the release of two new Pipeline components to enable archiving and restoration of telemetry data:

For complete information on how to set up data archiving and restoration, check out the topic Archive and Restore Telemetry Data in our product documentation.

Pipeline Processor

New Pipeline Processor: Redact (Beta)

Kai avatar
Shared by Kai • May 01, 2024

Mezmo is pleased to announce the release of the Redact Processor (Beta)

This Processor enables you to detect defined patterns of personal identifying information, like email addresses and social security numbers, and mask them with a hash or a specified string.

For more information, check out our technical documentation.

New Pipeline Feature: Shared Sources (Beta)

Kai avatar
Shared by Kai • May 01, 2024

With the new Shared Sources (Beta) feature, you can configure a Source one time, and use it across multiple Pipelines. This simplifies management of your Pipeline sources, and adds savings to your data volume costs.

Shared Sources also includes Auto-Parsing, which will automatically parse your source data, and Data Profiling, which will provide a profile of the most common patterns in your source data. For more information about Shared Sources, Auto-Parsing, and Data Profiling, check out the Shared Sources topic in our docs!

Pipeline Processor

New Pipeline Processor: Throttle (Beta)

Kai avatar
Shared by Kai • May 01, 2024

Mezmo is pleased to announce the release of the Throttle Processor (Beta) for Telemetry Pipelines. The Throttle processor applies rate limiting to a stream of events to limit load on downstream destinations. For more information about how to use and configure the Processor, check out the docs topic.

Pipeline Module

New Pipeline Module: Security & Compliance

Kai avatar
Shared by Kai • May 01, 2024

Mezmo is pleased to announce the publication of a new demo Pipette for the Security & Compliance module. Check out the topic Pipeline Module: Security & Compliance in the Practitioner's Guide to Data Optimization for an interactive demo, detailed information for configuring the Redact and Encrypt Processors, and instructions on how to build your own Pipettte to try out the Processors with your own sample data.

Pipeline Module

New Pipeline Module: Convert Events to Metrics

Kai avatar
Shared by Kai • April 03, 2024

Mezmo is pleased to announce the publication of a new demo Pipette for converting Status log events to metrics. This example, which is one of the recommendations in our White Paper "Optimize Your Telemetry Data in Five Steps," shows how to set up and cofigure the Route, Event to Metric, and Aggregate (Metric) Processors to extract common status messages from your logs, and convert those to metrics. The result is a significant reduction in the volume of log data that you need to send to your observability tools.