Agent skill · data analytics · jeremylongshore
documenso-observability
Implement monitoring, logging, and tracing for Documenso integrations.
Why this skill is useful
Adds executable scripts for monitoring and logging Documenso integrations that are not available in public documentation.
What it needs
Requires cloudwatch, datadog, grafana, prometheus, winston installed locally. About 4k tokens when loaded. Last updated 2026-08-07. 2,604 stars on the source repository.
What this skill does
Documenso Observability Output Redacted, bounded metrics/traces for document lifecycle, signing state, errors, latency, and rate headroom. An owned alert/runbook path that protects signer identity, document content, and credentials. Examples Emit aggregate counts by environment, document state, and status class while excluding document bodies, signer email, signing URLs, IP addresses, tokens, and audit payloads. Trigger a development signing-state alert with a synthetic document, verify the on-call route, then retain only the redacted receipt. Overview Implement monitoring, structured logging, and health checks for Documenso integrations. Since Documenso does not expose rate limit headers or usage metrics via API, observability is built around your API call patterns, latency, error rates, and webhook delivery. Prerequisites Working Documenso integration Monitoring stack (Prometheus/Grafana, Datadog, or CloudWatch) Logging infrastructure Instructions Step 1: Instrumented Client Wrapper Step 2: Structured Logging Step 3: Health Check Endpoint Step 4: Prometheus Metrics Endpoint Step 5: Webhook Delivery Monitoring Step 6: Alerting Rules Key Metrics to Monitor Metric Healthy Warning Critical -------- --------- --------- ---------- API error rate < 1% 1-5% > 5% Average latency < 1s 1-5s > 5s Health check Passing Degraded Failing Webhook delivery > 99% 95-99% < 95% Error Handling Observability Issue Cause Solution -------------------- ------- ---------- Metrics not appearing Scrape config wrong Verify Prometheus targets Logs missing Log level too high Set LOGLEVEL=debug temporarily False alerts Thresholds too sensitive Adjust to match your traffic patterns Health check flapping Transient network issues Add for: 2m to alert rules Resources Prometheus Best Practices OpenTelemetry Documentation Winston Logger Next Steps For incident response, see documenso-incident-runbook.
How to use it
Reference it in AdaL, Claude Code, Cursor or any coding agent — nothing to install:
@skills jeremylongshore/documenso-observability