lokalise-observability
Set up comprehensive observability for Lokalise integrations with metrics, traces, and alerts. Use when implementing monitoring for Lokalise operations, setting up dashboards, or configuring alerting for Lokalise integration health. Trigger with phrases like "lokalise monitoring", "lokalise metrics", "lokalise observability", "monitor lokalise", "lokalise alerts", "lokalise tracing". '
Profile →npx skills add jeremylongshore/claude-code-plugins-plus-skills --skill lokalise-observability --agent claude-code
Same command for any agent — swap --agent for codex, cursor, copilot.
Weekly change comes from our own snapshots, not the repository page — it measures attention, not adoption.
# Lokalise Observability ## Overview Monitor Lokalise translation pipeline health: API response times, rate limit consumption, translation completion rates, webhook delivery reliability, file upload/download status, and per-word cost tracking. Built around the `@lokalise/node-api` SDK with Prometheus-compatible metrics and alerting rules. ## Prerequisites - `@lokalise/node-api` SDK installed - Metrics backend (Prometheus, Datadog, CloudWatch, or OpenTelemetry collector) - Lokalise API token with read access - Optional: webhook endpoint for real-time event monitoring ## Instructions ### Step 1: Instrument API Calls with Metrics Wrap every SDK call to emit duration, success/failure counts, and rate limit status. ```typescript import { LokaliseApi } from "@lokalise/node-api"; interface MetricLabels { operation: string; status: "ok" | "error"; code?: string; } // Implement this to emit to your metrics backend declare function emitHistogram(name: string, value: number, labels: MetricLabels): void; declare function emitCounter(name: string, value: number, labels: MetricLabels): void; const lok = new LokaliseApi({ apiKey: process.env.LOKALISE_API_TOKEN! }); async function trackedApiCall<T
- Overview
- Prerequisites
- Instructions
- Step 1: Instrument API Calls with Metrics
- Step 2: Monitor Translation Completion
- Step 3: Track Rate Limit Consumption
- Step 4: Monitor Webhook Delivery
- Step 5: Register Webhooks for Key Events
- Step 6: Prometheus Alerting Rules
- Step 7: Translation Pipeline Dashboard Spec
- Output
- Error Handling
- Resources
- Next Steps
set -euo pipefail
Quick rate limit check — call from a monitoring cron job
echo "Rate limit: ${REMAINING}/${LIMIT} remaining (resets at ${RESET})"
Emit as metrics for Prometheus/Datadog
lokalise_rate_limit_remaining ${REMAINING}
lokalise_rate_limit_max ${LIMIT}
Subscribe to events that matter for pipeline monitoring
curl -s -X POST "https://api.lokalise.com/api2/projects/${LOKALISE_PROJECT_ID}/webhooks" \What does the lokalise-observability skill do?
Set up comprehensive observability for Lokalise integrations with metrics, traces, and alerts. Use when implementing monitoring for Lokalise operations, setting up dashboards, or configuring alerting for Lokalise integration health. Trigger with phrases like "lokalise monitoring", "lokalise metrics", "lokalise observability", "monitor lokalise", "lokalise alerts", "lokalise tracing". '
How do I install it?
Run `npx skills add jeremylongshore/claude-code-plugins-plus-skills --skill lokalise-observability --agent claude-code` — it drops the skill into your project so the agent can pick it up. Swap the --agent value for codex, cursor or copilot if you use one of those.
Where does this skill come from?
From jeremylongshore/claude-code-plugins-plus-skills, a repository with 2,630 stars. We read it straight from the repository tree rather than a submitted listing, so what you see here is what is actually published.
Is a popular skill a good skill?
Not necessarily. Stars measure attention, not adoption — a repository can trend for a week and be abandoned. That is why we show the weekly change from our own snapshots next to the total, instead of a single flattering number.