Site Reliability Engineers

Optimize data flowing to high-cost destinations and route to storage more intelligently with Mezmo Observability Pipeline.

Keep Services Humming

Telemetry data is your lifeblood, and managing it better is key. However, SRE teams cite managing huge data volumes and increasing costs as one of their biggest issues. Pipelining data in the right format to the right teams can reduce toil, improve collaboration and, most importantly, reduce resolution times.

Accelerate Resolution Times

Improve observability by boosting the "signal to noise ratio" of your telemetry data and directing it to the appropriate team. Aligning data formats across platforms enhances collaboration and root cause identification, while data enrichment deepens problem comprehension. With a collaborative team armed with superior data, issue resolution becomes more effective.

Benefit

01

Get Deeper Insights

You ensure great digital experiences “24 by 7”. But the data you need to meet your SLOs often hide in terabytes of telemetry data. Mezmo can parse, enrich, and transform that data in motion to help you monitor SLO adherence and make the decisions you need to keep your customers happy and subscribed.

Benefit

02

Eliminate Toil

You have more important things to do than calculating compute or storage requirements or performing open-source code maintenance. Mezmo gets you the observability answers you need without the toil. Automatically scale the infrastructure and data retention as your requirements grow. Stay in control of your consumption, with no hidden surprises.

Benefit

03

WHAT IS Mezmo TELEMETRY PIPELINE

Control Data

Control data volume and costs by identifying unstructured telemetry data, removing low-value and repetitive data, and using sampling to reduce chatter. Employ intelligent routing rules to send certain data types to low-cost storage.

  • Filter: Use the Filter Processor to drop events that may not be meaningful or to reduce the total amount of data forwarded to a subsequent processor or destination.
  • Reduce: Take multiple log input events and combine them into a single event based on specified criteria. Use Reduce to combine many events into one over a specified window of time.
  • Sample: Send only the events required to understand the data.
  • Dedupe: Reduce “chatter” in logs. The overlap of data across fields is the key to having the Dedup Processor work effectively. This processor will emit the first matching record of the set of records that are being compared.
  • Route: Intelligently route data to any observability, analytics, or visualization platform.

Transform Data

Increase your data value and optimize data flows by transforming and enriching data. Modify data as needed for compatibility with various end destinations. Enrich and augment data for better context. Scrub sensitive data, or encrypt it to maintain compliance standards.

  • Event to Metric: Create a new metric within the pipeline from existing events and log messages.
  • Parse: Various parsing options available to create multiple operations such as convert string to integers or parse timestamps.
  • Aggregate metrics: Metric data can have more data points than needed to understand the behavior of a system. Remove excess metrics to reduce storage without sacrificing value.
  • Encrypt: Use the Encrypt Processor when sending sensitive log data to storage, for example, when retaining log data containing account names and passwords.