Mezmo

Overview

Mezmo (formerly LogDNA) is a log management platform. With Sazabi's Mezmo backend, you can query your Mezmo logs directly from Chat without duplicating data.

What you can query

When Mezmo is configured as a backend, Chat can access:

Logs: Search and analyze logs stored in Mezmo
Apps: Filter logs by application name
Hosts: Filter logs by hostname
Levels: Filter by severity level (debug, info, warn, error, critical)

Prerequisites

Before you begin, make sure you have:

A Mezmo account with logs flowing into it
Access to generate service keys in your Mezmo organization

Setup

Generate a service key in Mezmo

Log in to your Mezmo dashboard
Go to Settings > Organization > API Keys
Click Generate Service Key
Give it a descriptive name like "Sazabi Integration"
Copy the key and store it securely

Use a Service Key, not an Ingestion Key. Service keys have read permissions for querying logs. Ingestion keys are for sending logs to Mezmo and will not work for this integration.

Data Sources

Select Mezmo from the list of external backends.

Enter your service key

Paste your Mezmo service key when prompted. Sazabi validates the key by making a test query to the Mezmo Export API.

If validation fails, verify:

You are using a service key (not an ingestion key)
The key has not been revoked in Mezmo
Your Mezmo account has active logs

Confirm and connect

Click Connect to save the configuration. Chat can now query your Mezmo logs directly.

Required permissions

Mezmo service keys provide read access to logs via the Export API. There are no granular permission scopes to configure. The service key grants access to all logs in your Mezmo organization.

If you need to restrict access:

Create a separate Mezmo organization for the logs you want Sazabi to access
Generate a service key for that specific organization

Query capabilities

Search syntax

Mezmo uses free-text search across log lines:

Pattern	Description
`error`	Find logs containing "error"
`connection timeout`	Find logs containing both words (AND)
`"connection timeout"`	Find logs with the exact phrase
`-debug`	Exclude logs containing "debug"

Filtering

Chat can filter Mezmo logs by:

Applications: Filter by the app field (e.g., "api-server", "worker")
Hosts: Filter by hostname (e.g., "web-01", "db-01")
Levels: Filter by severity (debug, info, notice, warn, error, critical, alert, emergency)
Time range: Query logs within a specific time window

Sorting

Newest first: Most recent logs appear first (default)
Oldest first: Oldest logs appear first

Limitations

Query size: Maximum 10,000 log entries per query. For larger result sets, narrow your time range or add filters.
Timeseries aggregation: Computed client-side from raw log entries. Queries that would require aggregating more than 10,000 entries will fail with an error asking you to narrow the time range.
Real-time: There may be a slight delay between logs appearing in Mezmo and being queryable through Sazabi.
Field queries: Mezmo's Export API uses free-text search. Complex field-based queries may not be supported.

Use cases

Configure Mezmo as a backend when:

You have an existing Mezmo deployment with production logs
You want to query Mezmo alongside other observability platforms in Sazabi
Compliance requirements prevent duplicating log data
You prefer to keep log storage and retention in Mezmo

Verify you are using a service key, not an ingestion key. Service keys are generated under Settings > Organization > API Keys and are used for reading logs. Ingestion keys are only for sending logs to Mezmo.

No logs returned

Check that logs exist in Mezmo for the queried time range
Verify your application names and hostnames match the filters
Try a broader search without filters to confirm connectivity
Ensure the service key has not been revoked

Query truncated error

Queries are limited to 10,000 entries. If you see a truncation error:

Narrow your time range
Add filters to reduce the result set
Use more specific search terms

Permission denied

Service keys provide organization-wide read access. If you see permission errors, the key may have been revoked. Generate a new service key in Mezmo and update your Sazabi configuration.

Slow queries

Large time ranges or broad searches can be slow. To improve performance:

Use shorter time ranges
Add filters for specific apps, hosts, or levels
Use specific search terms instead of broad queries

Security

Your Mezmo service key is encrypted at rest in Sazabi's database. The key is only decrypted when making queries to the Mezmo Export API. Sazabi does not store or cache your log data; all queries are executed directly against Mezmo's API.

To revoke access, either:

Disconnect Mezmo from Sazabi in Settings > Data Sources
Revoke the service key in Mezmo under Settings > Organization > API Keys