Mezmo
Monitoring Service API keyShip logs and manage views, alerts and archiving in Mezmo from any Windmill script, flow or app.
Set up in 3 steps
Copy a service key
In Mezmo, open Settings then API Keys, and take a service key — the ingestion key is a different one, for sending log lines.
Add the resource in Windmill
Open Resources, add a resource of type mezmo, and paste the key.
Run your first script
Fork any script below and read before writing anything. There are dozens here, so search by the verb you need.
Scripts
Building blocks, if none of the projects above fit. Fork one, run it, or call it as a step inside your own flow.
Update one or more fields of a key resource
Update a member
Update View
Update Index Rate Alert
Update Group
Update Exclusion Rule
Update Child Organization Contract
Update Category
Update Archive Configuration
Update Alert
Send Log Lines
Retrieve account usage totals
Retrieve a specific key
Retrieve a specific entperise key
Retrieve a screen
Retrieve a member
Retrieve a list of all the keys
Resume Ingestion
Lists all members
List all screens
List all enterprise keys
List all accounts
List Views
List Usage by Tag
List Usage by Host
List Usage By App
List Preset Alerts
List Parsing Templates
List Groups
List Exclusion Rules
Resource type
mezmo — the shape of the credential every script on this page expects.
| Field | Type | Required | What it is |
|---|---|---|---|
| apiKey | string | Yes | API key retrieved from the dashboard. |
Questions
Service key or ingestion key?
Service. The ingestion key only sends log lines and cannot read or configure anything through this API.
Is my key stored on the hub?
Never. It lives only in your own Windmill workspace, encrypted at rest.