Updating to Responsive Pipelines

Telemetry data is both fundamental and costly for any business. While this data is invaluable for troubleshooting, monitoring and various other concerns, it is not always valuable at the same time.Mezmo Responsive Pipelines adapt in real time to the content and conditions of your telemetry data, ensuring it’s routed and processed intelligently. They enable dynamic filtering, sampling, enrichment, and destination routing without manual reconfiguration. This flexibility helps teams reduce noise, control costs, and deliver the right data to the right tools when it matters most.

Step 1: Modify Responsive Test script

Using the State ID's for your Log, Metric and Trace pipelines modify switch_state.sh with the proper credentials.

Step 2: Run Responsive Test Script

Now let's run the script with your desired state to initiate Mezmo Pipeline flow changes. For instance, to flip to Incident mode you would run:

sh switch_state.sh incident

Step 3: Evaluate Impact

Notice that when in Normal mode, data in your pipelines are sampled and rolled up ensuring the needed signals are captured while remaining cost conscious. However, when in Incident or Deployment modes, data is grabbed at full fidelity. You will also see this represented in the UX

Normal Mode

Normal Mode

Incident Mode

Incident Mode

Due to the flexibility of Mezmo's API, any pipeline can be integrated with just about any Incident Management or Deployment method, from PagerDuty to Github to Shell scripts. To learn more, reach out to Mezmo at support@mezmo.com.