# Clerk Observability

> Implement monitoring, logging, and observability for Clerk authentication. Use when setting up monitoring, debugging auth issues in production, or implementing audit logging. Trigger with phrases like "clerk monitoring", "clerk logging", "clerk observability", "clerk metrics", "clerk audit log".

- Skill: `micsapp/clerk-observability` (Agent Skill, multi-file: 2 files)
- Install (CLI): `npx skillmds@latest add micsapp/clerk-observability`
- Raw SKILL.md: https://api.skillmd.com/api/skills/micsapp/clerk-observability/raw
- Safety review: pending
- Works with: Claude Code, Claude.ai, OpenAI Codex
- Category: Security
- License: MIT
- Author: micsapp (https://skillmd.com/u/micsapp)
- Updated: 2026-09-08
- Page: https://skillmd.com/skills/micsapp/clerk-observability

---

# Clerk Observability

## Overview
Implement comprehensive monitoring, logging, and observability for Clerk authentication.

## Prerequisites
- Clerk integration working
- Monitoring platform (DataDog, New Relic, Sentry, etc.)
- Logging infrastructure

## Instructions
1. Step 1: Authentication Event Logging
2. Step 2: Middleware Monitoring
3. Step 3: Session Analytics
4. Step 4: Webhook Event Tracking
5. Step 5: Error Tracking with Sentry
6. Step 6: Health Check Endpoint

For full implementation details and code examples, load:
`Read(${CLAUDE_SKILL_DIR}/references/implementation-guide.md)`

## Output
- Authentication event logging
- Performance monitoring
- Error tracking integration
- Health check endpoints

## Error Handling
| Issue | Monitoring Action |
|-------|-------------------|
| High auth latency | Alert on p95 > 200ms |
| Failed webhooks | Alert on failure rate > 1% |
| Session anomalies | Track unusual session patterns |
| API errors | Capture with Sentry context |

## Resources
- [Clerk Dashboard Analytics](https://dashboard.clerk.com)
- [Sentry Integration](https://docs.sentry.io)
- [DataDog APM](https://docs.datadoghq.com/tracing)

## Next Steps
Proceed to `clerk-incident-runbook` for incident response procedures.

## Examples

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

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