Mezmo
for LuumenAI
Read log volume and alert config in Mezmo, then change it as an approved step
Connect Mezmo and Luumen can read your ingestion status, views, preset alerts, exclusion rules, API keys, and team membership without leaving the terminal. Ask why ingest spiked last night, then act on the answer. Changes like adding an exclusion rule or inviting a member are previewed and approved before they run. Authentication is by API key.
The Mezmo toolbox
36 tools: 14 read, 22 write. Reads answer instantly. Writes require approval by default. Everything is logged.
- ReadGet Preset AlertRetrieve details of a specific preset alert by its ID.
- ReadGet CategoryRetrieve a category configuration by its type and ID.
- ReadGet Index Rate Alert ConfigurationRetrieve current index rate alert settings for the Mezmo account.
- ReadGet Ingestion Exclusion RuleRetrieve an ingestion exclusion rule by its ID.
- ReadGet Ingestion StatusGet the current ingestion status for the Mezmo account.
- ReadGet API KeyRetrieve an API key configuration by its ID.
- ReadGet MemberRetrieve member information by their ID.
- ReadGet Stream ConfigurationRetrieve the current event streaming configuration for the Mezmo account.
- ReadGet View DetailsRetrieve details of a specific view by its ID.
- ReadList Preset AlertsList all preset alerts configured for the Mezmo account.
- ReadList API KeysList all API keys and ingestion keys configured for the account.
- ReadList MembersList all team members in the Mezmo account configuration.
- ReadList Telemetry PipelinesList all telemetry pipelines configured for the account.
- ReadList ViewsList all views configured for the account.
- WriteCreate CategoryCreate a new category for views, boards, or screens in Mezmo. Approval by default
- WriteCreate Ingestion Exclusion RuleCreate an exclusion rule for log ingestion to control costs. Approval by default
- WriteCreate API KeyCreate a new API key (ingestion or service key) in Mezmo. Approval by default
- WriteCreate Member InvitationInvite a new member to the Mezmo organization with a specified role. Approval by default
- WriteCreate Preset AlertCreate a new preset alert in Mezmo with specified name and notification channels. Approval by default
- WriteCreate ViewCreate a new Mezmo view with filtering and alert configuration. Approval by default
- WriteDelete CategoryDelete a category by its type and ID. Approval by default
- WriteDelete Ingestion ExclusionRemove an ingestion exclusion rule by its ID. Approval by default
- WriteDelete API KeyDelete an API key by its unique identifier. Approval by default
- WriteDelete Organization MemberRemove a member from the organization by their email address. Approval by default
- WriteDelete Pipeline AlertDelete an alert for a specific component within a pipeline. Approval by default
- WriteDelete Preset AlertDelete a preset alert by its ID. Approval by default
- WriteDelete ViewDelete a view by its ID. Approval by default
- WriteIngest Logs to MezmoIngest log lines into Mezmo Log Analysis. Approval by default
- WriteResume Log IngestionResume log ingestion for the account after it has been stopped. Approval by default
- WriteUpdate CategoryUpdate a category name by its type and ID. Approval by default
- WriteUpdate Index Rate Alert ConfigurationConfigure index rate alerting settings including thresholds and notification channels. Approval by default
- WriteUpdate Ingestion Exclusion RuleUpdate an existing exclusion rule by its ID. Approval by default
- WriteUpdate API KeyUpdate an API key name by its ID. Approval by default
- WriteUpdate Member Role and GroupsUpdate a member's role and group assignments by their email address. Approval by default
- WriteUpdate Preset AlertUpdate an existing preset alert by ID. Approval by default
- WriteUpdate Mezmo ViewUpdate an existing Mezmo view by its ID. Approval by default
One prompt, start to finish
What a governed Mezmo run looks like inside Luumen.
Questions
Authorize once with API token. Luumen lists the scopes each action needs before you approve the connection, and credentials never appear in the chat.
Read actions answer immediately. Anything that writes — create category, create ingestion exclusion rule, create api key, create member invitation, and more — is shown as a plan and requires approval by default, including the 7 actions classified as destructive. Administrators configure that per tool, so you decide exactly which actions can ever run unattended.
You decide. Actions are granted per agent, skill, and team, and per environment — production is not staging. Read access can be broad while writes stay narrow.
Every call to Mezmo — read or write, approved or declined — is recorded with the actor, the input, and the result, and can be linked to the ticket or change record.
Often connected alongside
All integrations
DynatraceProblems, root-cause detail, and metrics beside the session.
DatadogMonitors, dashboards, and logs pulled into the investigation.
GrafanaRead Grafana health, rings, and dashboard data, then push log records with approval
PrometheusAlerts, metrics, and traces from Prometheus in the session that fixes them.Put Mezmo to work with Luumen
Connect in minutes. Every action scoped, approved, and audited from day one.