webflow-observability
Set up observability for Webflow integrations — Prometheus metrics for API calls, OpenTelemetry tracing, structured logging with pino, Grafana dashboards, and alerting for rate limits, errors, and latency. Trigger with phrases like "webflow monitoring", "webflow metrics", "webflow observability", "monitor webflow", "webflow alerts", "webflow tracing".
What this skill does
# Webflow Observability
## Overview
Full observability stack for Webflow Data API v2 integrations: Prometheus metrics
for API call counting and latency, OpenTelemetry distributed tracing, structured
JSON logging, and alerting rules for error rate and rate limit exhaustion.
## Prerequisites
- `prom-client` for Prometheus metrics
- `@opentelemetry/api` for tracing (optional)
- `pino` for structured logging
- Prometheus + Grafana (or compatible backend)
## Instructions
### Step 1: Prometheus Metrics
```typescript
// src/observability/metrics.ts
import { Registry, Counter, Histogram, Gauge } from "prom-client";
export const registry = new Registry();
// API request counter (by operation and status)
export const apiRequests = new Counter({
name: "webflow_api_requests_total",
help: "Total Webflow API requests",
labelNames: ["operation", "status_code", "method"] as const,
registers: [registry],
});
// Request duration histogram
export const apiDuration = new Histogram({
name: "webflow_api_request_duration_seconds",
help: "Webflow API request duration in seconds",
labelNames: ["operation"] as const,
buckets: [0.05, 0.1, 0.25, 0.5, 1, 2, 5, 10],
registers: [registry],
});
// Error counter by type
export const apiErrors = new Counter({
name: "webflow_api_errors_total",
help: "Webflow API errors by status code",
labelNames: ["operation", "status_code", "error_type"] as const,
registers: [registry],
});
// Rate limit remaining gauge
export const rateLimitRemaining = new Gauge({
name: "webflow_rate_limit_remaining",
help: "Remaining API calls before rate limit",
registers: [registry],
});
// CMS items gauge (track total items across collections)
export const cmsItemCount = new Gauge({
name: "webflow_cms_items_total",
help: "Total CMS items by collection",
labelNames: ["collection", "site"] as const,
registers: [registry],
});
// Webhook event counter
export const webhookEvents = new Counter({
name: "webflow_webhook_events_total",
help: "Received webhook events by trigger type",
labelNames: ["trigger_type", "status"] as const,
registers: [registry],
});
```
### Step 2: Instrumented Client Wrapper
```typescript
// src/observability/instrumented-client.ts
import { WebflowClient } from "webflow-api";
import { apiRequests, apiDuration, apiErrors, rateLimitRemaining } from "./metrics.js";
export async function instrumentedCall<T>(
operation: string,
method: string,
fn: () => Promise<T>
): Promise<T> {
const timer = apiDuration.startTimer({ operation });
try {
const result = await fn();
apiRequests.inc({ operation, status_code: "200", method });
timer();
return result;
} catch (error: any) {
const statusCode = String(error.statusCode || error.status || "unknown");
apiRequests.inc({ operation, status_code: statusCode, method });
apiErrors.inc({
operation,
status_code: statusCode,
error_type: statusCode === "429" ? "rate_limit" : statusCode >= "500" ? "server" : "client",
});
timer();
throw error;
}
}
// Usage
const { sites } = await instrumentedCall("sites.list", "GET", () =>
webflow.sites.list()
);
const { items } = await instrumentedCall("items.listLive", "GET", () =>
webflow.collections.items.listItemsLive(collectionId)
);
const item = await instrumentedCall("items.create", "POST", () =>
webflow.collections.items.createItem(collectionId, {
fieldData: { name: "Test", slug: "test" },
})
);
```
### Step 3: Metrics Endpoint
```typescript
// api/metrics.ts
import express from "express";
import { registry } from "../observability/metrics.js";
const app = express();
app.get("/metrics", async (req, res) => {
res.set("Content-Type", registry.contentType);
res.send(await registry.metrics());
});
```
### Step 4: OpenTelemetry Distributed Tracing
```typescript
// src/observability/tracing.ts
import { trace, SpanStatusCode, context } from "@opentelemetry/api";
const tracer = trace.getTracer("webflow-integration", "1.0.0");
export async function tracedCall<T>(
operationName: string,
attributes: Record<string, string>,
fn: () => Promise<T>
): Promise<T> {
return tracer.startActiveSpan(`webflow.${operationName}`, async (span) => {
span.setAttributes({
"webflow.operation": operationName,
...attributes,
});
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);
span.setAttributes({
"webflow.error.status_code": String(error.statusCode || "unknown"),
});
throw error;
} finally {
span.end();
}
});
}
// Usage
const { collections } = await tracedCall(
"collections.list",
{ "webflow.site_id": siteId },
() => webflow.collections.list(siteId)
);
```
### Step 5: Structured Logging
```typescript
// src/observability/logger.ts
import pino from "pino";
export const logger = pino({
name: "webflow-integration",
level: process.env.LOG_LEVEL || "info",
serializers: {
err: pino.stdSerializers.err,
},
// Redact sensitive fields
redact: {
paths: ["accessToken", "apiToken", "*.authorization", "req.headers.authorization"],
censor: "[REDACTED]",
},
});
// Log API calls with consistent structure
export function logApiCall(
operation: string,
durationMs: number,
status: "success" | "error",
metadata?: Record<string, any>
) {
const logFn = status === "error" ? logger.error.bind(logger) : logger.info.bind(logger);
logFn({
service: "webflow",
operation,
durationMs,
status,
...metadata,
}, `webflow.${operation} ${status} (${durationMs}ms)`);
}
// Log webhook events
export function logWebhook(triggerType: string, status: "processed" | "failed" | "skipped") {
logger.info({
service: "webflow",
event: "webhook",
triggerType,
status,
}, `webhook.${triggerType} ${status}`);
}
```
### Step 6: AlertManager Rules
```yaml
# prometheus/webflow-alerts.yml
groups:
- name: webflow
rules:
- alert: WebflowHighErrorRate
expr: |
(
rate(webflow_api_errors_total[5m]) /
rate(webflow_api_requests_total[5m])
) > 0.05
for: 5m
labels:
severity: warning
annotations:
summary: "Webflow API error rate > 5%"
description: "{{ $value | humanizePercentage }} errors in last 5m"
- alert: WebflowRateLimited
expr: |
rate(webflow_api_errors_total{status_code="429"}[5m]) > 0
for: 2m
labels:
severity: warning
annotations:
summary: "Webflow API rate limited"
- alert: WebflowHighLatency
expr: |
histogram_quantile(0.95,
rate(webflow_api_request_duration_seconds_bucket[5m])
) > 3
for: 5m
labels:
severity: warning
annotations:
summary: "Webflow P95 latency > 3s"
- alert: WebflowDown
expr: |
sum(rate(webflow_api_requests_total{status_code=~"5.."}[5m])) /
sum(rate(webflow_api_requests_total[5m])) > 0.5
for: 2m
labels:
severity: critical
annotations:
summary: "Webflow API > 50% server errors"
- alert: WebflowRateLimitLow
expr: webflow_rate_limit_remaining < 10
for: 1m
labels:
severity: warning
annotations:
summary: "Webflow rate limit nearly exhausted"
```
### Step 7: Grafana Dashboard Queries
```json
{
"panels": [
{
"title": "Request Rate by Operation",
"targets": [{ "expr": "sum by (operation) (rate(webflow_api_requests_total[5m]))" }]
},
{
"title": "Error Rate",
"targets": [{ "expr": "sum(rate(webflow_api_errors_total[5m])) / sum(rate(webflow_api_requests_total[Related in Backend & APIs
jfrog
IncludedInteract with the JFrog Platform via the JFrog CLI and REST/GraphQL APIs. Use this skill when the user wants to manage Artifactory repositories, upload or download artifacts, manage builds, configure permissions, manage users and groups, work with access tokens, configure JFrog CLI servers, search artifacts, manage properties, set up replication, manage JFrog Projects, run security audits or scans, look up CVE details, query exposures scan results from JFrog Advanced Security, manage release bundles and lifecycle operations, aggregate or export platform data, or perform any JFrog Platform administration task. Also use when the user mentions jf, jfrog, artifactory, xray, distribution, evidence, apptrust, onemodel, graphql, workers, mission control, curation, advanced security, exposures, or any JFrog product name.
cupynumeric-migration-readiness
IncludedPre-migration readiness assessor for porting NumPy to cuPyNumeric. Use BEFORE substantial porting work begins when the user asks whether code will scale on GPU, whether they should migrate to cuPyNumeric, which NumPy patterns transfer cleanly, what must be refactored before porting, or mentions pre-port assessment, scaling analysis, or refactor planning. Inspect the user's source code, look up NumPy usage, cross-reference the cuPyNumeric API support manifest, and distinguish distributed-scaling-friendly patterns from blockers such as unsupported APIs, scalar synchronization, host round-trips, Python/object-heavy control flow, shape/data-dependent branching, and in-place mutation hazards. Produce a verdict of READY, LIGHT REFACTOR, SIGNIFICANT REFACTOR, or NOT RECOMMENDED, with concrete refactor pointers.
alibabacloud-data-agent-skill
IncludedInvoke Alibaba Cloud Apsara Data Agent for Analytics via CLI to perform natural language-driven data analysis on enterprise databases. Data Agent for Analytics is an intelligent data analysis agent developed by Alibaba Cloud Database team for enterprise users. It automatically completes requirement analysis, data understanding, analysis insights, and report generation based on natural language descriptions. This tool supports: discovering data resources (instances/databases/tables) managed in DMS, initiating query or deep analysis sessions, real-time progress tracking, and retrieving analysis conclusions and generated reports. Use this Skill when users need to query databases, analyze data trends, generate data reports, ask questions in natural language, or mention "Data Agent", "data analysis", "database query", "SQL analysis", "data insights".
token-optimizer
IncludedReduce OpenClaw token usage and API costs through smart model routing, heartbeat optimization, budget tracking, and native 2026.2.15 features (session pruning, bootstrap size limits, cache TTL alignment). Use when token costs are high, API rate limits are being hit, or hosting multiple agents at scale. The 4 executable scripts (context_optimizer, model_router, heartbeat_optimizer, token_tracker) are local-only — no network requests, no subprocess calls, no system modifications. Reference files (PROVIDERS.md, config-patches.json) document optional multi-provider strategies that require external API keys and network access if you choose to use them. See SECURITY.md for full breakdown.
resend-cli
IncludedUse this skill when the task is specifically about operating Resend from an AI agent, terminal session, or CI job via the official resend CLI: installing/authenticating the CLI, sending/listing/updating/cancelling emails, batch sends, domains and DNS, webhooks and local listeners, inbound receiving, contacts, topics, segments, broadcasts, templates, API keys, profiles, or debugging Resend CLI/API failures. Trigger on mentions of Resend CLI, `resend`, `resend doctor`, `resend emails send`, `resend domains`, `resend webhooks listen`, `resend emails receiving`, or agent-friendly terminal automation.
alibabacloud-odps-maxframe-coding
IncludedUse this skill for MaxFrame SDK development and documentation navigation on Alibaba Cloud MaxCompute (ODPS). Helps answer MaxFrame API, concept, official example, and supported pandas API questions; create data processing programs; read/write MaxCompute tables; debug jobs (remote or local); and build custom DPE runtime images. Trigger when users mention MaxFrame, MaxCompute with MaxFrame, ODPS table processing, DPE runtime, MaxFrame docs/examples, DataFrame/Tensor operations, or GPU runtime setup. Works for both English and Chinese queries about Alibaba Cloud data processing with MaxFrame.