Skip to main content
Mezmo Pipeline provides support for multiple types of log data destinations, including Mezmo Log Analysis, cloud storage and monitoring platforms, and analytical tools. If you have an interest in using a pipeline destination not listed here, contact your Account Manager. All destinations are buffered, meaning that Mezmo Pipelines will not send a set of events until one of the following two conditions is satisfied:
  1. The number of events ready to be sent is 500.
  2. 300 seconds have elapsed since the first event of a set was received.
If you send data through the Pipeline and it is not showing up in your destination, please check that at least one of the conditions has been satisfied first.
  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. After you have set up a Pipeline Source, in the Destinations column, click Add.
  6. Select the Destination for your Pipeline log data, and enter the configuration information.
  7. To connect your Source and Destination, click the right edge of your Source, and when the and when the blue circle appears, drag the connector from the Source to the Destination until the Destination tile turns blue.
The topic Supported Telemetry Data Destinations provides a full list of available Destinations and their configuration instructions.

​
Video Overview

Azure Blob Storage

Send Mezmo Pipeline log data to an Azure Blob Storage container with configurable batching, encoding, compression, and prefixes.

Blackhole

A Destination that drops all data sent to it, useful for testing Pipeline data processing in a simulation without billable egress.

Checkly

Send Checkly-related spans to Checkly via the OpenTelemetry Destination, using a Route Processor to filter the correct traces.

AWS CloudWatch Metrics

Send Pipeline metrics to AWS CloudWatch for monitoring, with configuration for credentials, compression, namespace, and region.

AWS CloudWatch Logs

Send Pipeline logs to AWS CloudWatch for monitoring, with options for credentials, encoding, compression, log group, and stream.

Datadog Logs

Send Pipeline log data to Datadog, configuring the API key, compression, and Datadog site region.

Datadog Metrics

Send metrics data to Datadog as Custom Metrics, supported with Datadog Agent, HTTP, and Prometheus Remote Write sources.

Datadog Traces

Send Pipeline trace data to Datadog, configuring the API key, compression, and Datadog site region.

ElasticSearch

Send indexed log data to an ElasticSearch destination, with options for authentication strategy, compression, endpoints, and indices.

Google Cloud Storage

Send Mezmo Pipeline log data to a Google Cloud Storage bucket with configurable encoding, compression, batching, and credentials.

Google Cloud Monitoring

Send metric events to Google Cloud Monitoring, configuring project ID, resource type and labels, and JSON service account credentials.

Google Cloud Operations

Send log events to Google Cloud Operations, configuring log ID, project ID, resource type and labels, and JSON credentials.

Google Cloud PubSub

Send events to Google Cloud Pub/Sub, configuring encoding, project ID, topic, and JSON service account credentials.

Honeycomb Logs

Send log data to a Honeycomb dataset by configuring your Honeycomb API key and target dataset name.

HTTP Endpoint

Send Mezmo Pipeline log data to any HTTP endpoint, with options for encoding, compression, authentication, headers, proxies, and TLS.

Kafka

Send Mezmo Pipeline data to Kafka, with options for encoding, compression, TLS, and SASL/SCRAM authentication.

AWS Kinesis Data Firehose

Publish logs from your Mezmo Pipeline to AWS Kinesis Data Firehose streams using AWS credentials, encoding, and compression settings.

AWS Kinesis Streams

Publish logs from your Mezmo Pipeline to AWS Kinesis Streams using AWS credentials, encoding, compression, and a partition key field.

Loki

Send logs from your Mezmo Pipeline to any Loki destination, such as Grafana Logs, with configurable endpoint, auth strategy, codec, and labels.

Mezmo Archive Destination

Archive telemetry data to S3 or Azure Cloud Storage in a date-partitioned folder structure so it can later be restored into a Pipeline.

Mezmo Log Analysis

Send Pipeline data to a Mezmo Log Analysis account for search, views, and alerts, with configuration options for ingestion, query, and message fields.

New Relic

Send logs, metrics, and traces to a New Relic instance, configuring the account ID, API endpoint, US or EU region, and license key.

Notification Channel

Send a Pipeline-triggered notification to Slack, PagerDuty, a Webhook, or Mezmo Log Analysis based on event thresholds over a configurable time window.

OpenTelemetry Destination

Open Telemetry Destination configuration

Prometheus Remote Write

Send metrics to any destination that accepts the Prometheus Remote Write protocol, such as Grafana, with authentication and endpoint options.

AWS S3 Storage

Send pipeline data to an AWS S3 bucket for long-term storage, with options for encoding, compression, storage class, and required IAM permissions.

Splunk HTTP Event Collector

Send Mezmo Pipeline log data to Splunk via the HTTP Event Collector, configuring endpoint, token, encoding, compression, and indexed fields.

AWS SQS

Publish observability events from a pipeline to an Amazon SQS queue, configuring access keys, encoding, region, and queue URL.

Sumo Logic Logs

Send logs from a pipeline to your Sumo Logic instance, configuring the collector endpoint, compression, and category.