Mezmo Agent

Description

The Mezmo Agent Pipeline Source enables streaming of log data from the Mezmo Agent directly to your Pipeline.

Mezmo Agent Configuration

Environment Variable NameYaml Variable NameDescription
MZ_ENDPOINThttp.endpointPath of your Pipeline. For all Pipelines this should be set to /v1/<YOUR ROUTE ID>
MZ_HOSThttp.hostThe ingest endpoint for your Pipeline. Should be a value similar to pipeline.mezmo.com
MZ_INGESTION_KEYhttp.ingestion_keyThis is the access key to your Pipeline.
MZ_INGEST_BUFFER_SIZEhttp.body_sizeLimit the body size per request in bytes (please configure to 1000000 or less)

Migrating from Log Analysis

Please upgrade your Agent version to 3.9 or above before starting your migration to Pipeline ingestion. You may already have similar variables configured to point to your log analysis endpoint (prefixed with LOGDNA_). Just update these settings to the values in the table with values provided by your Pipeline setup. Please note the the MZ_prefix is only supported for Agent version 3.7+.

You can find more information about Agent settings in the Agent GitHub repo.

For complete information on setting up and configuring the OpenTelemetry Export for Mezmo log ingestion, check out the GitHub repo for the mezmoexporter.

Installing via Helm

If your cluster is managed with Helm, you can also install the Mezmo Agent for Pipeline using Helm. Utilizing the same information above, you can set these environment variables using the extraEnv attribute.

In the YAML file example shown here, replace <YOUR_PIPELINE_INGEST_KEY> with the key you obtained when setting up the Agent source in your Pipeline. When using the environment variables shown in the Configuration section, this is also the same value you would set for MZ_INGESTION_KEY.

Bash
Copy

Or using a values.yaml

YAML
Copy
Bash
Copy
Type to search, ESC to discard
Type to search, ESC to discard
Type to search, ESC to discard
  Last updated