Alerts & channels
Two-step model: create a channel (where notifications go), then create an alert (when to fire).
Channels
Supported types: webhook, slack, discord, telegram.
Interactive (recommended)
Prompts include where to obtain credentials for each provider:
loguro channels create Non-interactive (CI / scripted)
loguro channels create --name=ops --type=webhook --url=https://...
loguro channels create --name=ops-slack --type=slack --token=xoxb-... --channel=#alerts
loguro channels create --name=ops-tg --type=telegram --bot-token=... --chat-id=... Manage
loguro channels list
loguro channels enable ops # / disable
loguro channels delete ops --yes Alerts
From an existing log (recommended)
After seeing an error in loguro logs, derive an alert from it. The wizard pre-fills name, level, and message substring from the source log:
loguro alerts create --from-log 01KQ0E1ZTAP7YWFBK1S2K6XM2W Non-interactive
loguro alerts create --name "prod errors" --channel=ops \
--levels=error,critical \
--messageContains=payment \
--cooldown=30 | Flag | Description |
|---|---|
--name <str> | Alert name |
--channel <name> | Channel to fire on |
--levels <list> | Comma-separated log levels |
--messageContains <str> | Substring match on message |
--cooldown <minutes> | Minimum minutes between consecutive notifications |
--from-log <id> | Pre-fill the wizard from an existing log |
Manage
loguro alerts list
loguro alerts show "prod errors"
loguro alerts update "prod errors" --levels=critical
loguro alerts disable "prod errors" # / enable
loguro alerts delete "prod errors" --yes