Mezmo provides a comprehensive platform for log management and telemetry data processing, enabling organizations to collect, analyze, and manage their log data efficiently.
Mezmo provides a comprehensive platform for log management and telemetry data processing, enabling organizations to collect, analyze, and manage their log data efficiently. On Nagent, Mezmo is exposed as a fully-configurable server monitoring integration that any agent can call — 36 actions, and API key authentication. No code is required to wire Mezmo into your workflow — connect it once via the External Integrations panel and reuse it across every agent you build.
Agent builders use Mezmo to automate the kinds of tasks server monitoring teams previously handled manually. Concrete examples — each one is a single agent step in Nagent — include:
Every action and trigger is paired with a structured input/output schema (visible in the sections below), so when you wire Mezmo into Helix — our agentic agent builder — the editor knows exactly what each step expects and produces. Configure once, deploy anywhere across your Nagent agents.
Every operation an agent can call against Mezmo, with input parameters and output schema. Drop these into any step of an agent built in Helix.
MEZMO_CREATE_CATEGORYTool to create a new category for views, boards, or screens in Mezmo. Use when organizing Mezmo resources into categories.
Input parameters
The name of the category to create.
The type of category to create. Valid values: 'views', 'boards', or 'screens'.
Output
Data from the action execution
Error if any occurred during the execution of the action
Whether or not the action execution was successful or not
MEZMO_CREATE_INGESTION_EXCLUSIONTool to create an exclusion rule for log ingestion to control costs. Use this when you need to prevent specific logs from being ingested or stored based on query patterns. Exclusion rules help reduce ingestion costs by filtering out debug logs, test environment logs, or other non-essential log data.
Input parameters
Query string to match logs for exclusion. Use log field syntax (e.g., 'level:debug', 'app:test-service', 'level:info AND environment:staging'). Matched logs will be excluded from ingestion to control costs.
Descriptive title/name for the exclusion rule. Should clearly identify the purpose of the rule.
Whether the exclusion rule is active. If true, the rule will immediately apply to incoming logs. Defaults to false if not specified.
Whether to only index but not store the matched logs. If true, logs are indexed for search but not stored, saving storage costs. Defaults to true if not specified.
Output
Data from the action execution
Error if any occurred during the execution of the action
Whether or not the action execution was successful or not
MEZMO_CREATE_KEYTool to create a new API key (ingestion or service key) in Mezmo. The API auto-generates a unique name for the key. Use when you need to provision a new key for log ingestion or API access.
Input parameters
Type of API key to create. Currently supports 'ingestion' for ingestion keys.
Output
Data from the action execution
Error if any occurred during the execution of the action
Whether or not the action execution was successful or not
MEZMO_CREATE_MEMBERTool to invite a new member to the Mezmo organization with a specified role. Use this to send invitations to team members and optionally assign them to specific groups.
Input parameters
Role to assign to the member (e.g., 'member', 'admin', 'viewer')
Email address of the member to invite to the organization
Array of group IDs to assign the member to. If not provided, member will not be assigned to any groups
Output
Data from the action execution
Error if any occurred during the execution of the action
Whether or not the action execution was successful or not
MEZMO_CREATE_PRESET_ALERTTool to create a new preset alert in Mezmo with specified name and notification channels. Use this to configure alerts that can be triggered based on log conditions. Supports email, PagerDuty, and webhook notification channels.
Input parameters
Name of the preset alert to create
Array of notification channel configurations for the alert. At least one channel must be specified.
Output
Data from the action execution
Error if any occurred during the execution of the action
Whether or not the action execution was successful or not
MEZMO_CREATE_VIEWTool to create a new Mezmo view with filtering and alert configuration. Use when you need to set up custom log views with specific filters (query, hosts, apps, levels, tags) and optional alert channels (email, PagerDuty, webhook). At least one filter parameter must be provided in addition to the view name.
Input parameters
Filter by application names. At least one filter parameter (query, hosts, apps, levels, or tags) must be provided.
Name of the view to create
Filter by tags. At least one filter parameter (query, hosts, apps, levels, or tags) must be provided.
Filter by specific hostnames. At least one filter parameter (query, hosts, apps, levels, or tags) must be provided.
Search query to filter logs in the view (e.g., 'error OR warning'). At least one filter parameter (query, hosts, apps, levels, or tags) must be provided.
Filter by log severity levels (e.g., 'ERROR', 'WARN', 'INFO', 'DEBUG'). At least one filter parameter (query, hosts, apps, levels, or tags) must be provided.
Filter by log categories
Email notification channel configuration.
Webhook notification channel configuration.
PagerDuty notification channel configuration.
Output
Data from the action execution
Error if any occurred during the execution of the action
Whether or not the action execution was successful or not
MEZMO_DELETE_CATEGORYTool to delete a category by its type and ID. Use when you need to remove a view, board, or screen category from Mezmo configuration.
Input parameters
Unique identifier of the category to delete
Type of category to delete (views, boards, or screens)
Output
Data from the action execution
Error if any occurred during the execution of the action
Whether or not the action execution was successful or not
MEZMO_DELETE_INGESTION_EXCLUSIONTool to remove an ingestion exclusion rule by its ID. Use when you need to delete a specific exclusion rule from Mezmo's ingestion configuration.
Input parameters
The unique identifier of the ingestion exclusion rule to delete
Output
Data from the action execution
Error if any occurred during the execution of the action
Whether or not the action execution was successful or not
MEZMO_DELETE_KEYTool to delete an API key by its unique identifier. Use when you need to remove an ingestion key from Mezmo to revoke access.
Input parameters
The unique identifier of the API key to delete
Output
Data from the action execution
Error if any occurred during the execution of the action
Whether or not the action execution was successful or not
MEZMO_DELETE_MEMBERTool to remove a member from the organization by their email address. Use when you need to revoke a user's access to the organization.
Input parameters
Email address of the member to remove from the organization
Output
Data from the action execution
Error if any occurred during the execution of the action
Whether or not the action execution was successful or not
MEZMO_DELETE_PIPELINE_ALERTTool to delete an alert for a specific component within a pipeline. Use after confirming pipeline ID, component kind, component ID, and alert ID.
Input parameters
Unique identifier of the alert to delete
Unique identifier of the pipeline containing the component
Unique identifier of the component containing the alert
Type of component within the pipeline (e.g., source, transform, sink)
Output
Data from the action execution
Error if any occurred during the execution of the action
Whether or not the action execution was successful or not
MEZMO_DELETE_PRESET_ALERTTool to delete a preset alert by its ID. Use after confirming the preset alert ID exists.
Input parameters
Unique identifier of the preset alert to delete
Output
Data from the action execution
Error if any occurred during the execution of the action
Whether or not the action execution was successful or not
MEZMO_DELETE_VIEWTool to delete a view by its ID. Use when you need to remove a specific view from Mezmo.
Input parameters
ID of the view to delete
Output
Data from the action execution
Error if any occurred during the execution of the action
Whether or not the action execution was successful or not
MEZMO_GET_ALERTTool to retrieve details of a specific preset alert by its ID. Use when you need to view the configuration of an existing alert.
Input parameters
ID of the preset alert to retrieve
Output
Data from the action execution
Error if any occurred during the execution of the action
Whether or not the action execution was successful or not
MEZMO_GET_CATEGORYTool to retrieve a category configuration by its type and ID. Use when you need to fetch details about a specific Mezmo category (view, board, or screen).
Input parameters
Unique identifier of the category to retrieve. Can be obtained from POST /v1/config/categories/{categoryType} or by listing categories
Type of category to retrieve (views, boards, or screens)
Output
Data from the action execution
Error if any occurred during the execution of the action
Whether or not the action execution was successful or not
MEZMO_GET_INDEX_RATE_ALERTTool to retrieve current index rate alert settings for the Mezmo account. Use this to check if index rate alerting is enabled and view configured thresholds and notification channels.
Output
Data from the action execution
Error if any occurred during the execution of the action
Whether or not the action execution was successful or not
MEZMO_GET_INGESTION_EXCLUSIONTool to retrieve an ingestion exclusion rule by its ID. Use when you need to fetch details of a specific exclusion rule.
Input parameters
The ID of the ingestion exclusion rule to retrieve
Output
Data from the action execution
Error if any occurred during the execution of the action
Whether or not the action execution was successful or not
MEZMO_GET_INGESTION_STATUSTool to get the current ingestion status for the Mezmo account. Use when you need to check whether log ingestion is currently active or paused.
Output
Data from the action execution
Error if any occurred during the execution of the action
Whether or not the action execution was successful or not
MEZMO_GET_KEYTool to retrieve an API key configuration by its ID. Use when you need to fetch details about a specific Mezmo API key.
Input parameters
The unique identifier of the API key to retrieve (MongoDB ObjectId format)
Output
Data from the action execution
Error if any occurred during the execution of the action
Whether or not the action execution was successful or not
MEZMO_GET_MEMBERTool to retrieve member information by their ID. Use when you need to fetch details about a specific member in your Mezmo account.
Input parameters
Unique identifier of the member. Can be an email address or member ID.
Output
Data from the action execution
Error if any occurred during the execution of the action
Whether or not the action execution was successful or not
MEZMO_GET_STREAM_CONFIGTool to retrieve the current event streaming configuration for the Mezmo account. Use when you need to check if streaming is enabled and get streaming settings. Returns error details if streaming is unavailable on the account/plan.
Output
Data from the action execution
Error if any occurred during the execution of the action
Whether or not the action execution was successful or not
MEZMO_GET_VIEWTool to retrieve details of a specific view by its ID. Use when you need to fetch view configuration including name, query, filters, and other attributes.
Input parameters
Unique identifier of the view to retrieve
Output
Data from the action execution
Error if any occurred during the execution of the action
Whether or not the action execution was successful or not
MEZMO_INGEST_LOGSIngest log lines into Mezmo Log Analysis. Use this tool to send structured log data from hosts, applications, or services to Mezmo for centralized logging, analysis, and alerting. Logs are sent to the Mezmo ingestion endpoint and will appear in the Mezmo dashboard.
Input parameters
IP address of the host (optional, for additional host identification).
MAC address of the host (optional, for additional host identification).
Array of log lines to ingest. Each log line must have at least a 'line' field with the log message.
Comma-separated tags for categorizing logs (e.g., 'production,critical').
Hostname of the server or device sending the logs. Used for grouping and filtering logs in Mezmo.
Output
Data from the action execution
Error if any occurred during the execution of the action
Whether or not the action execution was successful or not
MEZMO_LIST_ALERTSTool to list all preset alerts configured for the Mezmo account. Use when you need to retrieve notification rules that trigger based on log patterns. Returns preset alert configurations including their channels (email, PagerDuty, webhook).
Output
Data from the action execution
Error if any occurred during the execution of the action
Whether or not the action execution was successful or not
MEZMO_LIST_KEYSTool to list all API keys and ingestion keys configured for the account. Use when you need to retrieve all keys for viewing or management purposes.
Output
Data from the action execution
Error if any occurred during the execution of the action
Whether or not the action execution was successful or not
MEZMO_LIST_MEMBERSTool to list all team members in the Mezmo account configuration. Use when you need to retrieve information about all members in the organization.
Output
Data from the action execution
Error if any occurred during the execution of the action
Whether or not the action execution was successful or not
MEZMO_LIST_PIPELINESTool to list all telemetry pipelines configured for the account. Use when you need to view or retrieve information about existing pipelines that manage the flow and transformation of telemetry data.
Output
Data from the action execution
Error if any occurred during the execution of the action
Whether or not the action execution was successful or not
MEZMO_LIST_VIEWSTool to list all views configured for the account. Views are saved search queries and filters for quick access to specific log data.
Output
Data from the action execution
Error if any occurred during the execution of the action
Whether or not the action execution was successful or not
MEZMO_RESUME_INGESTIONTool to resume log ingestion for the account after it has been stopped. Use when you need to re-enable log collection after a pause.
Output
Data from the action execution
Error if any occurred during the execution of the action
Whether or not the action execution was successful or not
MEZMO_UPDATE_CATEGORYTool to update a category name by its type and ID. Use when you need to rename an existing category in Mezmo.
Input parameters
New name for the category
Unique identifier of the category to update. Obtained from POST /v1/config/categories/{categoryType} or GET endpoints
Type of category to update. Valid values: 'views', 'boards', 'screens'
Output
Data from the action execution
Error if any occurred during the execution of the action
Whether or not the action execution was successful or not
MEZMO_UPDATE_INDEX_RATE_ALERTTool to configure index rate alerting settings including thresholds and notification channels. Use this when you need to set up or modify alerts for unusual log ingestion rates based on absolute line counts or statistical deviations.
Input parameters
Whether index rate alerting is enabled
Notification channels configuration specifying where alerts should be sent
Notification frequency for sending index rate alerts
Maximum number of lines per hour threshold for triggering alerts. Set to null to disable this threshold.
Maximum Z-score (standard deviations above 30-day average) for triggering alerts. Set to null to disable this threshold.
Alert trigger mode: 'separate' triggers alert when either threshold is exceeded, 'both' triggers only when both thresholds are exceeded simultaneously
Output
Data from the action execution
Error if any occurred during the execution of the action
Whether or not the action execution was successful or not
MEZMO_UPDATE_INGESTION_EXCLUSIONTool to update an existing exclusion rule by its ID. Use when you need to modify the query, active status, indexonly behavior, or title of an existing exclusion rule. At least one field (query, active, indexonly, or title) must be provided for update.
Input parameters
ID of the exclusion rule to update
Query string to match logs for exclusion (e.g., 'level:warn', 'app:production')
Title/name of the exclusion rule for identification
Whether the exclusion rule is active. Set to false to disable the rule without deleting it.
Whether to only exclude from indexing but keep in ingestion. When true, logs are ingested but not indexed.
Output
Data from the action execution
Error if any occurred during the execution of the action
Whether or not the action execution was successful or not
MEZMO_UPDATE_KEYTool to update an API key name by its ID. Use when you need to rename an existing Mezmo API key.
Input parameters
The new name for the API key
The unique identifier of the API key to update
Output
Data from the action execution
Error if any occurred during the execution of the action
Whether or not the action execution was successful or not
MEZMO_UPDATE_MEMBERTool to update a member's role and group assignments by their email address. Use when you need to change a member's permissions or group memberships.
Input parameters
The role to assign to the member. Common roles include 'owner', 'admin', and 'member'.
Array of group identifiers the member should belong to. Empty array removes the member from all groups.
Email address of the member to update. This serves as the unique identifier for the member.
Output
Data from the action execution
Error if any occurred during the execution of the action
Whether or not the action execution was successful or not
MEZMO_UPDATE_PRESET_ALERTTool to update an existing preset alert by ID. Allows modifying the alert's name and notification channels. Use when you need to change alert configuration after creation. Requires full resource representation with both name and channels.
Input parameters
Updated name of the preset alert
Array of notification channel objects. Each channel must have integration type, triggerlimit, and integration-specific fields (e.g., emails for email integration). At least one channel is required.
ID of the preset alert to update
Output
Data from the action execution
Error if any occurred during the execution of the action
Whether or not the action execution was successful or not
MEZMO_UPDATE_VIEWTool to update an existing Mezmo view by its ID. Use when you need to modify a view's name or search query.
Input parameters
The name/title of the view
The search query string that defines what logs should be displayed in this view
ID of the view to update
Output
Data from the action execution
Error if any occurred during the execution of the action
Whether or not the action execution was successful or not
No publicly available marketplace agent is found using this tool yet. There are 32 agents privately built on Nagent that already use Mezmo.
Build on Nagent
Connect Mezmo to any Nagent agent in minutes — no API key management, no boilerplate. Just configure and deploy.
The five questions agent builders ask before adopting a new integration.
Open the External Integrations panel inside Nagent (app.nagent.ai/externalIntegration), find Mezmo, and click "Connect Now." You'll authenticate with an API key — Nagent handles credential storage and refresh automatically. Once connected, Mezmo is available to any agent in your workspace.
No. Nagent provides no-code integration for every tool. Once Mezmo is connected, you configure its 36 actions directly in the agent builder UI — no API calls, no boilerplate, no schema management.
Helix — Nagent's agentic agent builder — lets you drop Mezmo steps into any workflow visually. Pick an action (e.g., one of those listed above), fill in the inputs (Helix knows the required vs. optional schema for each parameter), and connect it to upstream/downstream steps. Triggers run as the entry point of an agent, so when a Mezmo event fires, the agent kicks off automatically.
Every Mezmo action and trigger ships with a fully-typed schema — input parameters with name, type, required flag, and description, plus the output payload shape. The schemas are documented in the sections above. Helix uses these schemas to validate your configuration at build time and to type-check the data flowing between steps.
Yes. While Mezmo ships with 36 pre-built server monitoring actions, you can layer custom logic around them inside Helix — pre/post-processing steps, conditional branches, retries, or stitching Mezmo together with other connected tools. For deeper customization, talk to our team about Nagent's Agentic AI Lab — forward-deployed engineers who build Mezmo-based workflows tailored to your business.