Primary Ingestion Pipeline
In November of 2024, Mezmo Log Analysis customers were given access to a Pipeline designed specifically to provide them with an optimized log data management experience. This topic provides an overview of the new features available to customers through this Pipeline, as well as an overview of the Processors in this Pipeline and their configuration.
Access the Pipeline
- Log in to the Mezmo Web App.
- Click the Pipeline icon at the top of the left navigation column.
Do not edit the Pipeline without consulting Mezmo Technical Services.
Pipeline Architecture
The Primary Ingestion Pipeline processes data in four steps, with each step designed to optimize your data for use with Mezmo Log Management.
Schematic of the LASD Pipeline showing 1) the Mezmo Log Analysis Source 2) the Route Processor for Kubernetes Enrichment 3) the Drop Fields Processor 4) the Route Processor for Bad LInes 5) the Mezmo Log Analysis Destination 6)the Blackhole Destination
| Component | Description | Configuration |
|---|---|---|
| ||
| The Route Processor uses conditional statements to identify Kubernetes enrichment metrics, app/file metadata, and other relevant data for further processing, while unmatched data is sent directly to Log Analysis. |  |
| The Remove Fields Processor drops the .app field when a file is also present. |  |
| The Route Processor routes empty fields to a Blackhole Destination, where they are dropped. |  |
| The processed telemetry data is sent to Mezmo Log Analysis. |  |
| The Blackhole Destination drops all data sent to it. |
Learn More About Mezmo Telemetry Pipelines
Check out these links to learn more about Mezmo Telemetry Pipelines, and how you can optimize your telemetry data to reduce costs, gain insights, and quickly respond to anomalies and incidents.