| name | lindy-observability |
| description | Monitor Lindy AI agent health, task success rates, and credit consumption.
Use when setting up monitoring, building dashboards, configuring alerts,
or tracking agent performance over time.
Trigger with phrases like "lindy monitoring", "lindy observability",
"lindy metrics", "lindy logging", "lindy dashboard".
|
| allowed-tools | Read, Write, Edit, Bash(curl:*) |
| version | 1.15.0 |
| license | MIT |
| author | Jeremy Longshore <jeremy@intentsolutions.io> |
| tags | ["saas","lindy","monitoring","observability","dashboard"] |
| compatibility | Designed for Claude Code |
Lindy Observability
Overview
Monitor Lindy AI agent execution health, task completion rates, step-level failures,
trigger frequency, and credit consumption. Lindy provides built-in task history in
the dashboard. External observability requires webhook callbacks, the Task Completed
trigger, and application-side metrics collection.
Prerequisites
- Lindy workspace with active agents
- For external monitoring: webhook receiver + metrics stack (Prometheus/Grafana, Datadog)
- For alerts: Slack or email integration configured
Key Observability Signals
| Signal | Source | Why It Matters |
|---|
| Task completion rate | Tasks tab / callback | Measures agent reliability |
| Task duration | Task detail view | Tracks performance over time |
| Step failure rate | Task detail (red steps) | Identifies broken actions |
| Credit consumption | Billing dashboard | Budget tracking |
| Trigger frequency | Task count over time | Detects trigger storms |
| Agent error rate | Failed tasks / total tasks | Overall health indicator |
Instructions
Step 1: Dashboard Monitoring (Built-In)
Lindy's Tasks tab provides per-agent monitoring:
- Open agent > Tasks tab
- Filter by status: Completed, Failed, In Progress
- For failed tasks: click to see which step failed and why
- Track patterns: same step failing? same time of day? same trigger type?
Step 2: Task Completed Trigger (Agent-to-Agent Monitoring)
Use Lindy's built-in Task Completed trigger to build an observability agent:
Monitoring Agent:
Trigger: Task Completed (from Production Support Agent)
Condition: "Go down this path if the task failed"
→ Action: Slack Send Channel Message to #ops-alerts
Message: "Support Agent task failed: {{task.error}}"
Condition: "Go down this path if task duration > 30 seconds"
→ Action: Slack Send Channel Message to #ops-alerts
Message: "Support Agent slow: {{task.duration}}s"
Step 3: Webhook-Based Metrics Collection
Configure agents to call your metrics endpoint on task completion:
