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".
What this skill does
# 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>(
operation: string,
fn: () => Promise<T>
): Promise<T> {
const start = performance.now();
try {
const result = await fn();
const durationMs = performance.now() - start;
emitHistogram("lokalise_api_duration_ms", durationMs, {
operation,
status: "ok",
});
emitCounter("lokalise_api_requests_total", 1, {
operation,
status: "ok",
});
return result;
} catch (err: unknown) {
const code = (err as { code?: number })?.code?.toString() ?? "unknown";
const durationMs = performance.now() - start;
emitHistogram("lokalise_api_duration_ms", durationMs, {
operation,
status: "error",
code,
});
emitCounter("lokalise_api_requests_total", 1, {
operation,
status: "error",
code,
});
throw err;
}
}
// Usage — wrap every SDK call
const keys = await trackedApiCall("keys.list", () =>
lok.keys().list({ project_id: projectId, limit: 500 })
);
const bundle = await trackedApiCall("files.download", () =>
lok.files().download(projectId, {
format: "json",
filter_langs: ["en"],
original_filenames: false,
})
);
```
### Step 2: Monitor Translation Completion
Poll project statistics and emit per-locale progress as gauge metrics.
```typescript
declare function emitGauge(name: string, value: number, labels: Record<string, string>): void;
async function collectTranslationMetrics(projectId: string): Promise<void> {
const project = await trackedApiCall("projects.get", () =>
lok.projects().get(projectId)
);
// Overall progress
emitGauge("lokalise_translation_progress_pct", project.statistics?.progress_total ?? 0, {
project: projectId,
locale: "all",
});
emitGauge("lokalise_keys_total", project.statistics?.keys_total ?? 0, {
project: projectId,
});
// Per-language progress
const languages = await trackedApiCall("languages.list", () =>
lok.languages().list({ project_id: projectId, limit: 100 })
);
for (const lang of languages.items) {
emitGauge("lokalise_translation_progress_pct", lang.statistics?.progress ?? 0, {
project: projectId,
locale: lang.lang_iso,
});
emitGauge("lokalise_words_to_do", lang.statistics?.words_to_do ?? 0, {
project: projectId,
locale: lang.lang_iso,
});
}
}
// Run on a schedule (every 5 minutes)
// setInterval(() => collectTranslationMetrics(projectId), 5 * 60_000);
```
### Step 3: Track Rate Limit Consumption
```bash
set -euo pipefail
# Quick rate limit check — call from a monitoring cron job
HEADERS=$(curl -sI "https://api.lokalise.com/api2/projects?limit=1" \
-H "X-Api-Token: ${LOKALISE_API_TOKEN}" 2>/dev/null)
LIMIT=$(echo "$HEADERS" | grep -i "x-ratelimit-limit" | awk '{print $2}' | tr -d '\r')
REMAINING=$(echo "$HEADERS" | grep -i "x-ratelimit-remaining" | awk '{print $2}' | tr -d '\r')
RESET=$(echo "$HEADERS" | grep -i "x-ratelimit-reset" | awk '{print $2}' | tr -d '\r')
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}
```
### Step 4: Monitor Webhook Delivery
Track webhook processing success and latency in your webhook handler.
```typescript
import express from "express";
const webhookMetrics = {
received: 0,
processed: 0,
failed: 0,
totalLatencyMs: 0,
};
app.post("/webhooks/lokalise", async (req: express.Request, res: express.Response) => {
webhookMetrics.received++;
const start = performance.now();
// Respond immediately — Lokalise times out after 8 seconds
res.status(200).json({ received: true });
try {
await processWebhookEvent(req.body);
webhookMetrics.processed++;
} catch (error) {
webhookMetrics.failed++;
console.error("Webhook processing failed:", error);
}
const latencyMs = performance.now() - start;
webhookMetrics.totalLatencyMs += latencyMs;
emitCounter("lokalise_webhook_received_total", 1, {
event: req.body.event,
status: webhookMetrics.failed > 0 ? "error" : "ok",
});
emitHistogram("lokalise_webhook_processing_ms", latencyMs, {
event: req.body.event,
status: "ok",
});
});
// Health endpoint exposing webhook metrics
app.get("/metrics/webhooks", (_req, res) => {
res.json({
received: webhookMetrics.received,
processed: webhookMetrics.processed,
failed: webhookMetrics.failed,
avgLatencyMs: webhookMetrics.received > 0
? Math.round(webhookMetrics.totalLatencyMs / webhookMetrics.received)
: 0,
});
});
```
### Step 5: Register Webhooks for Key Events
```bash
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
```yaml
groups:
- name: lokalise
rules:
- alert: LokaliseApiRateLimited
expr: rate(lokalise_api_requests_total{status="error", code="429"}[5m]) > 0
for: 2m
annotations:
summary: "Lokalise API rate limit hit — requests being throttled"
runbook: "Check for runaway loops. Lokalise limit is 6 req/sec per token."
- alert: LokaliseApiErrors
expr: rate(lokalise_api_requests_total{status="error", code=~"5.."}[10m]) > 0.1
for: 5m
annotations:
summary: "Lokalise API returning 5xx errors"
runbook: "Check https://status.lokalise.com. Enable fallback translations."
- alert: TranslationProgressStalled
expr: lokalise_translation_progress_pct < 80 and changes(lokalise_translation_progress_pct[24h]) == 0
for: 24h
annotations:
summary: "Translation progress stalled at {{ $value }}% for 24+ hours"
- alert: WebhookDeliveryFailing
expr: rate(lokalise_webhook_received_total{status="error"}[1h]) > 3
annotations:
summary: "Lokalise webhook deliveries failing ({{ $value }} errors/hour)"
- alert: LokaliseApiLatencyHigh
expr: histogram_quantile(0.95, rate(lokalise_api_duration_ms_bucket[5m])) > 5000
for: 10m
annotations:
summary: "Lokalise API P95 latency above 5 seconds"
```
### Step 7: Translation Pipeline Dashboard Spec
Key panels for GrRelated in General
modeling-omnistudio-epc-catalog
IncludedSalesforce Industries CME EPC product-modeling skill for Product2-based catalog creation. Use when creating EPC products, configuring product attributes, building offer bundles with Product Child Items, or reviewing EPC DataPack JSON metadata for product catalog changes. TRIGGER when: user creates or updates Product2 EPC records, AttributeAssignment payloads, AttributeMetadata/AttributeDefaultValues, Offer bundles, or ProductChildItem relationships. DO NOT TRIGGER when: designing OmniScripts/FlexCards/Integration Procedures (use building-omnistudio-omniscript, building-omnistudio-flexcard, or building-omnistudio-integration-procedure), implementing Apex business logic (use generating-apex), or troubleshooting deployment pipelines (use deploying-metadata).
relationship-science-coach
IncludedUse this skill for direct, practical adult relationship coaching: couples conflict, repair, trust, marriage, dating, flirting, attachment patterns, emotional connection, sex, desire differences, eroticism, kink negotiation, affection, love languages, breakups, and long-term passion. Draw on Gottman, EFT and Hold Me Tight, attachment science, modern sex research, Perel, Nagoski, Kerner, Schnarch, Love and Stosny, and flexible love-language tools. Be concrete and low-hedge. Redirect only for imminent danger, abuse, coercive control, minors, non-consent, self-harm, stalking, or medical/legal/psychiatric decisions.
building-sf-integrations
IncludedSalesforce integration architecture and runtime plumbing with 120-point scoring. Use this skill to set up Named Credentials, External Credentials, External Services, REST/SOAP callout patterns, Platform Events, and Change Data Capture. TRIGGER when: user sets up Named Credentials, External Services, REST/SOAP callouts, Platform Events, CDC, or touches .namedCredential-meta.xml files. DO NOT TRIGGER when: Connected App/OAuth config (use configuring-connected-apps), Apex-only logic (use generating-apex), or data import/export (use handling-sf-data).
venue-templates
IncludedAccess comprehensive LaTeX templates, formatting requirements, and submission guidelines for major scientific publication venues (Nature, Science, PLOS, IEEE, ACM), academic conferences (NeurIPS, ICML, CVPR, CHI), research posters, and grant proposals (NSF, NIH, DOE, DARPA). This skill should be used when preparing manuscripts for journal submission, conference papers, research posters, or grant proposals and need venue-specific formatting requirements and templates.
let-fate-decide
IncludedDraws the 12 Houses of the Zodiac Tarot spread to inject entropy into planning when prompts are vague, ambiguous, or casually delegated. Interprets the spread to guide next steps. Use when the user says 'let fate decide', 'YOLO', 'whatever', 'idk', or other nonchalant phrases, makes Yu-Gi-Oh references, or when you are about to arbitrarily pick between multiple reasonable approaches. Prefer over ask-questions-if-underspecified when the user's tone is casual or playful rather than precision-seeking.
net-ops
IncludedCross-platform network troubleshooting (Windows, macOS, Linux) via local or remote shell. Use for: DNS broken, can't resolve hostnames, nslookup/dig works but apps fail, NRPT, WFP, scutil, /etc/resolver, systemd-resolved, /etc/resolv.conf, NetworkManager, VPN DNS leak residue (ProtonVPN/Mullvad/WireGuard/AnyConnect), AV/firewall blocking DNS or DoH, Tailscale DNS interaction, intermittent connectivity, remote diagnostics over SSH.