> For clean Markdown of any page, append .md to the page URL.
> For a complete documentation index, see https://mezmo.ferndocs.com/the-log-analysis-source-data-pipeline/llms.txt.
> For AI client integration (Claude Code, Cursor, etc.), connect to the MCP server at https://mezmo.ferndocs.com/_mcp/server.

# Primary Ingestion Pipeline

> Discover the new features available to customers through this Pipeline, as well as an overview of the Processors in this Pipeline & their configuration at Mezmo.

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

1. Log in to the Mezmo Web App.
2. 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](https://uploads.developerhub.io/prod/2KW7/d8jizv5xta6tdgr3d1z7zuwztw49l7ii3pmrxksl8lbtprpcvdqsodmimwq0ibx6.png)

| Component                         | Description                                                                                                                                                                                                                                                                            | Configuration                                                                                                       |
| --------------------------------- | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | ------------------------------------------------------------------------------------------------------------------- |
| 1. Mezmo Log Analysis Data Source |                                                                                                                                                                                                                                                                                        |                                                                                                                     |
| 2. Route Processor                | The [Route Processor](https://docs.mezmo.com/2.8/telemetry-pipelines/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. | ![](https://uploads.developerhub.io/prod/2KW7/tyh04lxdsigtonmi55hovtroclow1yq9ffcj2q9bny06o3eoq01ikhh252ygaznt.png) |
| 3. Remove Fields Processor        | The [Remove Fields Processor](https://docs.mezmo.com/2.8/telemetry-pipelines/drop-fields-processor) drops the .app field when a file is also present.                                                                                                                                  | ![](https://uploads.developerhub.io/prod/2KW7/fstjxllfw58f071eqvkcysxefr3khm30gqseewho45foufyt0qs3xx2x8chlm5rw.png) |
| 4. Route Processor                | The [Route Processor](https://docs.mezmo.com/2.8/telemetry-pipelines/route-processor) routes empty fields to a [Blackhole](https://docs.mezmo.com/2.8/telemetry-pipelines/blackhole-destination) Destination, where they are dropped.                                                  | ![](https://uploads.developerhub.io/prod/2KW7/fmd2o3bdhah36vvt3dz431n635n9swu14c0jwvzkwgk8ibxwcxjoqhajobsqvjqe.png) |
| 5. Log Analysis Destination       | The processed telemetry data is sent to Mezmo Log Analysis.                                                                                                                                                                                                                            | ![](https://uploads.developerhub.io/prod/2KW7/mfqjapuzyz0otmq3l8uhg96a2uc2yuk8gqksiveq8a12donygjwj5l5cjqre5f5s.png) |
| 6. Blackhole Destination          | The [Blackhole](https://docs.mezmo.com/2.8/telemetry-pipelines/blackhole-destination) 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.

* [Getting Started with Mezmo Telemetry Pipelines](https://docs.mezmo.com/2.8/telemetry-pipelines/getting-started-with-mezmo-telemetry-pipeline)
* [About Mezmo Flow](https://docs.mezmo.com/2.8/telemetry-pipelines/about-mezmo-flow)
* [Supported Processors](https://docs.mezmo.com/2.8/telemetry-pipelines/supported-processors)
* [In-Stream Alerts](https://docs.mezmo.com/2.8/telemetry-pipelines/in-stream-alerts)
* [Configure Responsive Pipelines](https://docs.mezmo.com/2.8/telemetry-pipelines/configure-responsive-pipelines)

> Discover the new features available to customers through this Pipeline, as well as an overview of the Processors in this Pipeline & their configuration at Mezmo.