What it does
Mezmo Telemetry Pipeline is a hosted data-processing layer for logs, metrics, and traces. A pipeline connects one or more sources to destinations through processors that can filter, encrypt, route, and transform events. Pipeline Taps let operators inspect samples as data moves through the path, while volume metrics show ingress and egress. This makes the product useful for teams controlling telemetry flow and cost before indexing, rather than only searching data after it has been stored.
Shape the path, not just the dashboard
A first pipeline needs a source, a destination, and any processors that should act between them. In the Web App, create a pipeline, select the source configuration, choose where the data should go, and add processors for tasks such as filtering, routing, encryption, or transformation. The documentation describes destinations including Amazon S3, Elasticsearch, and Mezmo Log Analysis, along with sources such as the Mezmo Agent and AWS Kinesis Firehose.
Deploying the pipeline starts the flow. The active pipeline view reports the amount of data moving through it; add a Pipeline Tap to inspect a sample between nodes while tuning the processor chain. This gives an operator a way to check what is flowing without waiting for the destination's index. The pipeline's ingress and egress metrics are also useful when investigating a sudden increase in traffic.
The product is a processing and routing layer, so teams still need a destination for durable search, dashboards, or alert investigation. Deployment requires a Pipeline Manage permission. Mezmo documents a 30-day free trial with access to sources, destinations, and processors, capped at 20 pipelines; after the trial, a paid plan is required. Its pricing information says cost depends on data volume and retention, and pipeline documentation measures egress in bytes. Exact rates and plan-specific limits should be confirmed before routing production volume.
Strengths
- A single pipeline can filter or transform telemetry and send it to a chosen downstream destination.
- Pipeline Taps sample data in transit, and deployed pipeline views expose flow volume between configured components.
- Documentation covers log, metric, and trace flows, including integrations with OpenTelemetry.
Watch out for
- The team must configure and maintain source, processor, and destination connections; it is an additional component in the telemetry path.
- The trial is limited to 30 days and 20 pipelines, and continuing requires a paid plan.
Best for
- Platform teams reducing or reshaping high-volume logs before sending them to storage or analytics tools.
- Operations teams routing telemetry to several backends while checking pipeline throughput and samples.
Sources
- Mezmo Telemetry Pipeline: Cut Volume, Lift Quality (Oct 26, 2026)
- About Mezmo Telemetry Pipelines (Oct 26, 2026)
- Build and Deploy a Mezmo Telemetry Pipeline (Oct 26, 2026)
- About Mezmo Trial Accounts (Oct 26, 2026)
- Mezmo Telemetry Pipeline Pricing for Every Team Size (Oct 26, 2026)
- Getting Started with Mezmo Telemetry Pipelines (Oct 26, 2026)