> For clean Markdown of any page, append .md to the page URL. > For a complete documentation index, see https://mezmo.ferndocs.com/8---optimize-responsibly/llms.txt. > For AI client integration (Claude Code, Cursor, etc.), connect to the MCP server at https://mezmo.ferndocs.com/_mcp/server. # 8 - Test the Responsive Pipelines > If you run into any issues or have feedback on either the workshop or Pipeline, please reach out to us at [support@mezmo.com](mailto:support@mezmo.com). ## Why It Matters 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 introduced [Responsive Pipelines](https://docs.mezmo.com/telemetry-pipelines/configure-responsive-pipelines) specifically to address the dynamic nature of telemetry data. By allowing for extreme configurability, telemetry flows can be tuned for changing circumstances from incidents to deployments. ## 1 - Modify Responsive Test script Using the State ID's for your Log, Metric and Trace pipelines modify [`switch_state.sh`](https://github.com/mezmo/opentelemetry-demo/blob/main/switch_state.sh) with the proper credentials. ## 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: ```bash sh switch_state.sh incident ``` ## 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 Mezmo Web App. ### Normal Mode ![Normal Mode](https://uploads.developerhub.io/prod/2KW7/1jl0ugjtknek6rrrl233ah2gtl32teowj9sdk28yq8k7trglsr6wezh0feh5y1hr.png) ### Incident Mode ![Incident Mode](https://uploads.developerhub.io/prod/2KW7/71tfpfrsehwe1zr3rtpg9xl9zcsk6z0movm91ujouom9zyhp8x0i4ji11ewxf656.png) Due to the flexibility of [Mezmo's API](https://docs.mezmo.com/pipeline-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](mailto:support@mezmo.com).