Skip to content
Back to skills

Documenso Observability

ASecurity

Implement monitoring, logging, and tracing for Documenso integrations. Use when setting up observability, implementing metrics collection, or debugging production issues. Trigger with phrases like "documenso monitoring", "documenso metrics", "documenso logging", "documenso tracing", "documenso observability".

  • 4 stars
  • 0 votes
  • 0 copies
  • 2 views
  • Added September 10, 2026
devopsdebuggingapidocumentation

Works with

  • api

Security analysis

A100/100

Pro scans all 2 files and shows the line behind each finding

Scanned September 10, 2026

npx -y skills add micsapp/micstec-skills --skill documenso-observability --agent claude-code

Installs into .claude/skills of the current project.

Are you the author of Documenso Observability?

Add the live security badge to your README. It updates with every re-scan.

Security grade badge for Documenso Observability
[![Security: A — Skills Directory](https://www.skillsdirectory.com/api/skills/micsapp-documenso-observability/badge)](https://www.skillsdirectory.com/skills/micsapp-documenso-observability)

More formats (shields.io, HTML) on the badges page. Keep it an A: scan every change in CI with Pro.

Download with Pro
SKILL.md
---
name: documenso-observability
description: |
  Implement monitoring, logging, and tracing for Documenso integrations.
  Use when setting up observability, implementing metrics collection,
  or debugging production issues.
  Trigger with phrases like "documenso monitoring", "documenso metrics",
  "documenso logging", "documenso tracing", "documenso observability".
allowed-tools: Read, Write, Edit
version: 1.0.0
license: MIT
author: Jeremy Longshore <jeremy@intentsolutions.io>
compatible-with: claude-code, codex, openclaw
---
# Documenso Observability

## Overview
Implement comprehensive observability for Documenso integrations including metrics, logging, and distributed tracing.

## Prerequisites
- Working Documenso integration
- Monitoring platform (Datadog, Prometheus, etc.)
- Logging infrastructure (ELK, CloudWatch, etc.)
- Tracing system (Jaeger, Zipkin, etc.)

## Instructions

### Step 1: Metrics Collection
// src/observability/metrics.ts
### Step 2: Structured Logging
// src/observability/logger.ts
### Step 3: Distributed Tracing
// src/observability/tracing.ts
### Step 4: Health Check Endpoint
// src/api/health.ts
### Step 5: Alerting Rules
groups:
### Step 6: Grafana Dashboard
{

For detailed implementation code and configurations, load the reference guide:
`Read(${CLAUDE_SKILL_DIR}/references/implementation-guide.md)`

## Output
- Metrics Collection
- Structured Logging
- Distributed Tracing
- Health Check Endpoint
- Alerting Rules
- Grafana Dashboard

## Error Handling
| Observability Issue | Cause | Solution |
|--------------------|-------|----------|
| Metrics not showing | Wrong scrape config | Check Prometheus config |
| Logs not appearing | Log level too high | Set LOG_LEVEL=debug |
| Traces missing | OTEL not initialized | Call initTracing() |
| High cardinality | Too many labels | Reduce label values |

## Resources
- [Prometheus Best Practices](https://prometheus.io/docs/practices/)
- [OpenTelemetry Documentation](https://opentelemetry.io/docs/)
- [Structured Logging](https://www.structlog.org/)

## Next Steps
For incident response, see `documenso-incident-runbook`.

## Examples

**Basic usage**: Apply documenso observability to a standard project setup with default configuration options.

**Advanced scenario**: Customize documenso observability for production environments with multiple constraints and team-specific requirements.

Files in this skill

  • SKILL.md2.3 KB
  • references/implementation-guide.md12 KB

Attribution

Is this your skill, or is something wrong with this listing? Request removal or report an issue. Author removals are honored within 72 hours.

Comments

Loading comments…

Newsletter

Get the weekly list of safe new skills, and the ones we pulled.