Skip to main content
Mezmo Telemetry Pipelines provides support for ingesting pipeline log data from a number of popular sources, as described in the topics in this section. If you have an interest in using a pipeline source not listed here, contact your Account Manager.
  1. Log into the Mezmo Web App.
  2. In the left-hand menu, click Pipelines. This will open the Edit Pipeline interface.
  3. In the left-hand navigation, click + New Pipeline.
  4. Enter a name for the Pipeline, then click Save.
  5. In the Sources column of the pipeline schematic, click Add.
  6. Select the Pipeline Source you want to use, and enter the configuration information. When the source picker opens, some sources may appear in a Recommended Sources section above the regular Sources tabs. See Recommended Sources below for details.
The topic Supported Telemetry Pipeline Sources provides a full list of available sources and their configuration instructions. The pipeline editor groups account-wide shared streams into a Recommended Sources section shown above the regular Sources tabs in the source picker. The section describes this behavior: “These sources live at the account level. Every pipeline that adds one reads from the same ingest stream.” The OpenTelemetry Source is listed first because Mezmo recommends OpenTelemetry as the primary way to send data into a pipeline. Other recommended sources, such as Mezmo Log Analysis Ingestion, follow it.
A pipeline can include at most one source of a given account-wide shared-stream type. Today the account-wide shared-stream types are the OpenTelemetry Source and Mezmo Log Analysis Ingestion, so a pipeline can include one of each but not more than one of either. You can still add the same shared-stream source to other pipelines.Mezmo enforces this limit for account-wide shared-stream sources however you add the source: the Mezmo Web App, the Pipeline API, Terraform, cloning a pipeline, and importing a pipeline manifest. It is not merely a disabled button in the source picker.In the source picker, if a shared-stream source is already in the pipeline, its card is disabled and shows this hint: “Only one of the these nodes is allowed per pipeline because it reads a shared account-wide stream.” If you try to add a second source of the same shared-stream type to a pipeline through the Pipeline API or a manifest import, Mezmo rejects the request instead of silently succeeding.

​
Video Overview

Azure Event Hub

Ingest data from an Azure Event Hub into Mezmo Pipelines via the Kafka interface, including prerequisites and configuration options.

Demo Logs

Ready-to-use demo log sources in formats like NGINX, Apache, syslog, JSON, and metrics for building and testing your Pipelines.

FluentD and FluentBit

Stream FluentD and FluentBit logs and metrics to Mezmo Pipelines using HTTP output plugins for SaaS or Forward plugins for Edge.

HTTP

Send data to a Mezmo Pipeline via a RESTful POST when a native source type isn't supported, then parse it in-stream to extract fields.

HTTP Client

A pull source that polls an HTTP endpoint on a schedule and ingests the responses into your pipeline, with configurable method, interval, headers, decoding, and authentication.

Kafka

A pull source that collects events from Kafka-compatible brokers, with configurable topics, consumer group, TLS, and SASL/SCRAM authentication.

AWS Kinesis Firehose

Stream near real-time data into your Mezmo Pipeline from AWS Kinesis Firehose by configuring the HTTP endpoint and API key on your delivery stream.

Mezmo Log Analysis Ingestion

Redirect data sent to the logs.mezmo.com Log Analysis endpoint into a Pipeline Source, supporting agent, ingest, syslog, and Heroku endpoints.

Mezmo Log Analysis

A deprecated source that forwards logs from your Log Analysis account into a Pipeline, including the metadata query fields it attaches to each event.

Mezmo Agent

Stream log data from the Mezmo Agent directly into a Pipeline, including configuration variables, migration from Log Analysis, and Helm installation.

Datadog Agent

Receive logs and metrics directly from the Datadog Agent over HTTPS into a Mezmo Pipeline, with setup, configuration, and Docker/host examples.

Datadog Agent V2

Receive logs, metrics, and traces from a Datadog Agent on separate output ports so each telemetry type can be routed independently.

OpenTelemetry Source

Pipeline Data Restoration

Source that lets you restore telemetry data from an archive location into a Pipeline, with no configuration options required.

Logstash

Send data from your Logstash instance to Mezmo Pipelines using the HTTP output plugin with string or JSON formatting.

Prometheus Remote Write

Send metrics to a Mezmo Pipeline using the Prometheus Remote Write source, with a unique endpoint URL and Bearer Token authentication.

AWS S3 via SQS

Use log data stored in Amazon S3 as a pipeline source via Amazon SQS to rehydrate, parse, and route archived data for analysis or compliance.

Splunk HEC

Use the Splunk HTTP Event Collector as a pipeline source to route, reduce, and process events before forwarding them on to Splunk or a SIEM.

Syslog over HTTP

Send Syslog events to Mezmo Pipelines through an HTTP endpoint over TLS, including an example rsyslog om-http configuration.

AWS SQS

Stream log data from an Amazon SQS queue as a pipeline source, including SQS setup, the required access policy, and IAM permissions.

Webhook (WebSub)

Accept RESTful webhook messages using the WebSub protocol, verifying payloads with an HMAC signature based on a configured signing key.