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".
Instalar com Codex ou Claude Copie este prompt, cole no Codex, Claude ou outro assistente e deixe que ele revise a página da skill e instale para você.
Um comando direto ignora o prompt de revisão. Verifique a origem antes de executá-lo.
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".
Designed for Claude Code, also compatible with Codex and OpenClaw
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.
set -euo pipefail
# Subscribe to events that matter for pipeline monitoring
curl -s -X POST "https://api.lokalise.com/api2/projects/${LOKALISE_PROJECT_ID}/webhooks" \
-H "X-Api-Token: ${LOKALISE_API_TOKEN}" \
-H "Content-Type: application/json" \
-d '{
"url": "https://hooks.company.com/lokalise",
"events": [
"project.imported",
"project.exported",
"project.key.added",
"project.key.modified",
"project.translation.updated",
"project.translation.proofread",
"project.task.closed",
"project.contributor.added"
]
}' | jq '{webhook_id: .webhook.webhook_id, events: .webhook.events}'
Step 6: Prometheus Alerting Rules
groups:-name:lokaliserules:-alert:LokaliseApiRateLimitedexpr:rate(lokalise_api_requests_total{status="error",code="429"}[5m])>0for:2mannotations:summary:"Lokalise API rate limit hit — requests being throttled"runbook:"Check for runaway loops. Lokalise limit is 6 req/sec per token."-alert:LokaliseApiErrorsexpr:rate(lokalise_api_requests_total{status="error",code=~"5.."}[10m])>0.1for:5mannotations:summary:"Lokalise API returning 5xx errors"runbook:"Check https://status.lokalise.com. Enable fallback translations."-alert:TranslationProgressStalledexpr:lokalise_translation_progress_pct<80andchanges(lokalise_translation_progress_pct[24h])==0for:24hannotations:summary:"Translation progress stalled at {{ $value }}% for 24+ hours"-alert:WebhookDeliveryFailingexpr:rate(lokalise_webhook_received_total{status="error"}[1h])>3annotations:summary:"Lokalise webhook deliveries failing ({{ $value }} errors/hour)"-alert:LokaliseApiLatencyHighexpr:histogram_quantile(0.95,rate(lokalise_api_duration_ms_bucket[5m]))>5000for:10mannotations:summary:"Lokalise API P95 latency above 5 seconds"
For setting up real-time automation based on webhook events, see lokalise-webhooks-events. For incident response procedures when alerts fire, see lokalise-incident-runbook.