Inngest Integration
Monitor function run metrics, event ingestion rates, and step execution latency across your Inngest durable functions. Detect failure rate spikes and step latency SLO breaches before they impact your users.
How It Works
Connect via Inngest Webhook
Register the TigerOps webhook URL in your Inngest dashboard under Manage > Webhooks. TigerOps receives function run lifecycle events — queued, started, completed, failed, and cancelled — in real time.
Configure the Inngest API Integration
Add your Inngest signing key and environment to TigerOps. The integration polls the Inngest Metrics API to collect function run throughput, queue depths, and step latency percentiles across all your apps and environments.
Set Function Run SLOs
Define per-function p95 execution time SLOs and failure rate thresholds. TigerOps alerts when a function's p95 run duration breaches your SLO or when the failure rate exceeds your configured error budget.
Correlate with Your Backend Services
TigerOps correlates Inngest function failures with traces from the external services they call — databases, HTTP APIs, and queues — so you know whether a function failure is an Inngest issue or a downstream dependency failure.
What You Get Out of the Box
Function Run Throughput
Per-function completed, failed, and cancelled run counts with historical trend analysis. Track throughput across all Inngest environments (production, staging) in a single unified view.
Step Execution Latency
p50/p95/p99 latency per function step. Identify which step in a multi-step Inngest function is introducing the most latency — whether it's a slow database query, external API call, or sleep/waitForEvent.
Event Ingestion Rate Monitoring
Track events sent to Inngest per second, event type breakdown, and ingestion errors. Alert when event ingestion volume drops unexpectedly — indicating upstream producers have stopped sending events.
Queue Depth & Concurrency
Monitor per-function queue depth and in-progress concurrency against your Inngest plan limits. Alert before functions are throttled due to concurrency limits being reached during traffic spikes.
Failed Run & Retry Tracking
Track function run failures, retry attempt counts, and runs exhausting all retries. Correlate failure spikes with code deployments using TigerOps deploy event tracking.
AI Root Cause Analysis
When Inngest function failure rates spike, TigerOps AI analyzes the failed step, correlated service dependency errors, deploy events, and infrastructure changes to surface the most likely root cause.
Inngest Webhook & API Setup
Register the TigerOps webhook and API credentials in your Inngest dashboard and environment configuration.
# Step 1: Register TigerOps webhook in Inngest dashboard
# Navigate to: Inngest Dashboard > Manage > Webhooks > New Webhook
# URL: https://ingest.atatus.net/webhooks/inngest
# Signing Key: (copy from TigerOps dashboard)
# Events: function/run.created, function/run.completed,
# function/run.failed, function/run.cancelled
# Step 2: Set environment variables in your deployment
TIGEROPS_API_KEY=your_api_key_here
INNGEST_SIGNING_KEY=your_inngest_signing_key
INNGEST_ENV=production # or staging, etc.
# Step 3: Configure in TigerOps dashboard
# Settings > Integrations > Inngest
# - Inngest API Key: (from Inngest Dashboard > Settings > API Keys)
# - Environment: production
# - Alert on failure rate exceeding: 1%
# - Alert on p95 step latency exceeding: 5000ms
# Per-function SLO configuration (tigerops.yaml)
integrations:
inngest:
apiKey: ${INNGEST_API_KEY}
signingKey: ${INNGEST_SIGNING_KEY}
environments:
- production
- staging
functionSLOs:
"app/send-welcome-email":
p95LatencyMs: 10000
failureRatePct: 2
"app/process-payment":
p95LatencyMs: 5000
failureRatePct: 0.5
concurrencyAlertThreshold: 80 # % of plan limitCommon Questions
How does TigerOps collect Inngest function metrics?
TigerOps uses two complementary methods: webhook delivery for real-time run lifecycle events (start, complete, fail) and the Inngest Metrics API for aggregated throughput and latency metrics. The combination gives both real-time alerting and accurate historical percentiles.
Can TigerOps monitor Inngest functions across multiple apps and environments?
Yes. TigerOps ingests metrics from all Inngest apps registered in your account. Functions are labeled with their app name and environment (production, staging, branch environments) so you can filter dashboards and alerts by scope.
How does TigerOps handle Inngest sleep and waitForEvent steps in latency tracking?
TigerOps separates active execution time from sleep/wait time in step latency metrics. You can view both total function wall-clock time and active CPU/IO time, so a function with a 24-hour waitForEvent step doesn't skew your execution latency SLOs.
Can TigerOps alert me when a specific Inngest function has a high failure rate?
Yes. Configure per-function failure rate thresholds in TigerOps. Alerts include the function name, app, environment, error message from the last failed run, and a direct link to the failed run in the Inngest dashboard for immediate investigation.
Does TigerOps support Inngest's branch environments for preview deployments?
Yes. Branch environment function metrics are collected with an environment label. You can set separate (typically less strict) SLOs for branch environments while keeping tight production SLOs, and TigerOps won't page you for branch environment noise.
Stop Discovering Inngest Function Failures After Users Report Them
Function run SLOs, step latency tracking, and failure rate alerts. Set up via webhook in 5 minutes.