clickup-observability
Monitor ClickUp API integrations with metrics, tracing, structured logging, and alerting using Prometheus, OpenTelemetry, and Grafana. Trigger: "clickup monitoring", "clickup metrics", "clickup observability", "monitor clickup", "clickup alerts", "clickup tracing", "clickup dashboard".
Best use case
clickup-observability is best used when you need a repeatable AI agent workflow instead of a one-off prompt.
Monitor ClickUp API integrations with metrics, tracing, structured logging, and alerting using Prometheus, OpenTelemetry, and Grafana. Trigger: "clickup monitoring", "clickup metrics", "clickup observability", "monitor clickup", "clickup alerts", "clickup tracing", "clickup dashboard".
Teams using clickup-observability should expect a more consistent output, faster repeated execution, less prompt rewriting.
When to use this skill
- You want a reusable workflow that can be run more than once with consistent structure.
When not to use this skill
- You only need a quick one-off answer and do not need a reusable workflow.
- You cannot install or maintain the underlying files, dependencies, or repository context.
Installation
Claude Code / Cursor / Codex
Manual Installation
- Download SKILL.md from GitHub
- Place it in
.claude/skills/clickup-observability/SKILL.mdinside your project - Restart your AI agent — it will auto-discover the skill
How clickup-observability Compares
| Feature / Agent | clickup-observability | Standard Approach |
|---|---|---|
| Platform Support | Not specified | Limited / Varies |
| Context Awareness | High | Baseline |
| Installation Complexity | Unknown | N/A |
Frequently Asked Questions
What does this skill do?
Monitor ClickUp API integrations with metrics, tracing, structured logging, and alerting using Prometheus, OpenTelemetry, and Grafana. Trigger: "clickup monitoring", "clickup metrics", "clickup observability", "monitor clickup", "clickup alerts", "clickup tracing", "clickup dashboard".
Where can I find the source code?
You can find the source code on GitHub using the link provided at the top of the page.
SKILL.md Source
# ClickUp Observability
## Overview
Monitor ClickUp API v2 integrations with metrics (request rate, latency, errors, rate limit usage), distributed tracing, and alerting.
## Key Metrics
| Metric | Type | Labels | Description |
|--------|------|--------|-------------|
| `clickup_requests_total` | Counter | method, endpoint, status | Total API requests |
| `clickup_request_duration_seconds` | Histogram | method, endpoint | Request latency |
| `clickup_errors_total` | Counter | status_code, error_type | Errors by type |
| `clickup_rate_limit_remaining` | Gauge | token_hash | Rate limit headroom |
| `clickup_rate_limit_resets_total` | Counter | | Times we hit 429 |
## Prometheus Instrumentation
```typescript
import { Registry, Counter, Histogram, Gauge } from 'prom-client';
const registry = new Registry();
const requestCounter = new Counter({
name: 'clickup_requests_total',
help: 'Total ClickUp API v2 requests',
labelNames: ['method', 'endpoint', 'status'] as const,
registers: [registry],
});
const requestDuration = new Histogram({
name: 'clickup_request_duration_seconds',
help: 'ClickUp API request duration in seconds',
labelNames: ['method', 'endpoint'] as const,
buckets: [0.05, 0.1, 0.25, 0.5, 1, 2, 5],
registers: [registry],
});
const rateLimitGauge = new Gauge({
name: 'clickup_rate_limit_remaining',
help: 'ClickUp rate limit remaining requests',
registers: [registry],
});
const errorCounter = new Counter({
name: 'clickup_errors_total',
help: 'ClickUp API errors by status code',
labelNames: ['status_code', 'error_type'] as const,
registers: [registry],
});
```
## Instrumented Client
```typescript
async function instrumentedClickUpRequest<T>(
path: string,
options: RequestInit = {}
): Promise<T> {
const method = options.method ?? 'GET';
// Normalize endpoint for cardinality control (replace UUIDs)
const endpoint = path.replace(/\/[a-zA-Z0-9]{6,}(?=\/|$|\?)/g, '/:id');
const timer = requestDuration.startTimer({ method, endpoint });
try {
const response = await fetch(`https://api.clickup.com/api/v2${path}`, {
...options,
headers: {
'Authorization': process.env.CLICKUP_API_TOKEN!,
'Content-Type': 'application/json',
...options.headers,
},
});
// Update rate limit gauge
const remaining = response.headers.get('X-RateLimit-Remaining');
if (remaining) rateLimitGauge.set(parseInt(remaining));
const status = response.ok ? 'success' : `${response.status}`;
requestCounter.inc({ method, endpoint, status });
if (!response.ok) {
const body = await response.json().catch(() => ({}));
errorCounter.inc({
status_code: String(response.status),
error_type: body.ECODE ?? 'unknown',
});
throw new Error(`ClickUp ${response.status}: ${body.err}`);
}
return response.json();
} catch (error) {
if (!(error instanceof Error && error.message.startsWith('ClickUp'))) {
errorCounter.inc({ status_code: 'network', error_type: 'fetch_error' });
}
throw error;
} finally {
timer();
}
}
```
## OpenTelemetry Tracing
```typescript
import { trace, SpanStatusCode } from '@opentelemetry/api';
const tracer = trace.getTracer('clickup-integration', '1.0.0');
async function tracedClickUpCall<T>(
operationName: string,
path: string,
fn: () => Promise<T>
): Promise<T> {
return tracer.startActiveSpan(`clickup.${operationName}`, async (span) => {
span.setAttribute('clickup.path', path);
span.setAttribute('clickup.method', 'GET');
try {
const result = await fn();
span.setStatus({ code: SpanStatusCode.OK });
return result;
} catch (error: any) {
span.setStatus({ code: SpanStatusCode.ERROR, message: error.message });
span.recordException(error);
throw error;
} finally {
span.end();
}
});
}
```
## Structured Logging
```typescript
import pino from 'pino';
const logger = pino({ name: 'clickup', level: process.env.LOG_LEVEL ?? 'info' });
function logClickUpCall(data: {
method: string;
path: string;
status: number;
durationMs: number;
rateLimitRemaining?: number;
error?: string;
}): void {
const level = data.status >= 500 ? 'error' : data.status >= 400 ? 'warn' : 'info';
logger[level]({
service: 'clickup',
...data,
}, `ClickUp ${data.method} ${data.path} -> ${data.status} (${data.durationMs}ms)`);
}
```
## Alert Rules
```yaml
# prometheus/clickup_alerts.yaml
groups:
- name: clickup
rules:
- alert: ClickUpHighErrorRate
expr: rate(clickup_errors_total[5m]) / rate(clickup_requests_total[5m]) > 0.05
for: 5m
labels: { severity: warning }
annotations:
summary: "ClickUp API error rate > 5%"
- alert: ClickUpHighLatency
expr: histogram_quantile(0.95, rate(clickup_request_duration_seconds_bucket[5m])) > 3
for: 5m
labels: { severity: warning }
annotations:
summary: "ClickUp P95 latency > 3s"
- alert: ClickUpRateLimitLow
expr: clickup_rate_limit_remaining < 10
for: 1m
labels: { severity: critical }
annotations:
summary: "ClickUp rate limit nearly exhausted"
- alert: ClickUpAuthFailures
expr: increase(clickup_errors_total{status_code="401"}[5m]) > 0
labels: { severity: critical }
annotations:
summary: "ClickUp authentication failures detected"
```
## Metrics Endpoint
```typescript
app.get('/metrics', async (req, res) => {
res.set('Content-Type', registry.contentType);
res.send(await registry.metrics());
});
```
## Error Handling
| Issue | Cause | Solution |
|-------|-------|----------|
| High cardinality | Dynamic IDs in labels | Normalize paths (replace IDs with `:id`) |
| Missing metrics | Uninstrumented code path | Wrap all API calls through instrumented client |
| Alert storm | Threshold too sensitive | Tune `for` duration and threshold |
| Trace gaps | Missing context propagation | Ensure span context is passed |
## Resources
- [Prometheus Best Practices](https://prometheus.io/docs/practices/naming/)
- [OpenTelemetry JS SDK](https://opentelemetry.io/docs/languages/js/)
- [ClickUp Rate Limits](https://developer.clickup.com/docs/rate-limits)
## Next Steps
For incident response, see `clickup-incident-runbook`.Related Skills
exa-observability
Set up monitoring, metrics, and alerting for Exa search integrations. Use when implementing monitoring for Exa operations, building dashboards, or configuring alerting for search quality and latency. Trigger with phrases like "exa monitoring", "exa metrics", "exa observability", "monitor exa", "exa alerts", "exa dashboard".
evernote-observability
Implement observability for Evernote integrations. Use when setting up monitoring, logging, tracing, or alerting for Evernote applications. Trigger with phrases like "evernote monitoring", "evernote logging", "evernote metrics", "evernote observability".
documenso-observability
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".
deepgram-observability
Set up comprehensive observability for Deepgram integrations. Use when implementing monitoring, setting up dashboards, or configuring alerting for Deepgram integration health. Trigger: "deepgram monitoring", "deepgram metrics", "deepgram observability", "monitor deepgram", "deepgram alerts", "deepgram dashboard".
databricks-observability
Set up comprehensive observability for Databricks with metrics, traces, and alerts. Use when implementing monitoring for Databricks jobs, setting up dashboards, or configuring alerting for pipeline health. Trigger with phrases like "databricks monitoring", "databricks metrics", "databricks observability", "monitor databricks", "databricks alerts", "databricks logging".
customerio-observability
Set up Customer.io monitoring and observability. Use when implementing metrics, structured logging, alerting, or Grafana dashboards for Customer.io integrations. Trigger: "customer.io monitoring", "customer.io metrics", "customer.io dashboard", "customer.io alerts", "customer.io observability".
coreweave-observability
Set up GPU monitoring and observability for CoreWeave workloads. Use when implementing GPU metrics dashboards, configuring alerts, or tracking inference latency and throughput. Trigger with phrases like "coreweave monitoring", "coreweave observability", "coreweave gpu metrics", "coreweave grafana".
cohere-observability
Set up comprehensive observability for Cohere API v2 with metrics, traces, and alerts. Use when implementing monitoring for Chat/Embed/Rerank operations, setting up dashboards, or configuring alerts for Cohere integrations. Trigger with phrases like "cohere monitoring", "cohere metrics", "cohere observability", "monitor cohere", "cohere alerts", "cohere tracing".
coderabbit-observability
Monitor CodeRabbit review effectiveness with metrics, dashboards, and alerts. Use when tracking review coverage, measuring comment acceptance rates, or building dashboards for CodeRabbit adoption across your organization. Trigger with phrases like "coderabbit monitoring", "coderabbit metrics", "coderabbit observability", "monitor coderabbit", "coderabbit alerts", "coderabbit dashboard".
clickup-webhooks-events
Create and manage ClickUp webhooks for real-time event notifications. Use when setting up webhook listeners for task/list/space events, implementing two-way sync, or handling ClickUp event payloads. Trigger: "clickup webhook", "clickup events", "clickup notifications", "clickup real-time", "clickup event listener", "clickup webhook create".
clickup-upgrade-migration
Migrate between ClickUp API versions (v2 to v3) and handle breaking changes. Use when upgrading API versions, adapting to endpoint changes, or migrating between ClickUp plan tiers. Trigger: "upgrade clickup API", "clickup v2 to v3", "clickup breaking changes", "clickup API migration", "clickup deprecation".
clickup-security-basics
Secure ClickUp API tokens, implement least-privilege access, and audit usage. Use when securing API keys, rotating tokens, configuring per-environment credentials, or auditing ClickUp API access patterns. Trigger: "clickup security", "clickup secrets", "secure clickup token", "clickup API key rotation", "clickup access audit".