Notifications
Raise a PagerDuty incident when spend breaches a threshold that warrants waking someone.
Lineman raises a PagerDuty incident when your AI-coding spend breaches a budget, so a runaway bill pages someone instead of waiting in an inbox until Monday. You choose the PagerDuty service the incidents land on. Each one carries the alert rule's name and the alert's own figures, so whoever is paged can see what breached before opening Lineman. Severity is held per connection: warning by default, with critical, error and info available.
When spend crosses a budget threshold, Lineman raises an incident on the PagerDuty service you nominate. A bill that would otherwise sit unread in an inbox until Monday reaches PagerDuty instead. Incidents are raised as warning by default, because a budget threshold is a look-at-today matter rather than a production outage.
A budget that stays breached re-fires every hour, and each firing updates the same incident instead of opening another. Different alert rules get separate incidents, so acknowledging one does not quietly acknowledge the rest.
The incident summary is the alert rule's name, and the alert's figures ride along in PagerDuty's custom details. Dismissing the alert in Lineman resolves its incident, and that is the only thing that closes it. Spend alerts have no automatic all-clear, so an incident nobody dismisses stays open.
The documentation walks through connecting it, what Lineman reads and writes, and the settings worth knowing about.
Read the setup guideEvery integration in one place, searchable by name and filterable by what it does.
View all integrations