lokalise-observability

Featured

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".

AI & Automation 2,266 stars 315 forks Updated today MIT

Install

View on GitHub

Quality Score: 99/100

Stars 20%
100
Recency 20%
100
Frontmatter 20%
70
Documentation 15%
100
Issue Health 10%
50
License 10%
100
Description 5%
100

Skill Content

# 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",...

Details

Author
jeremylongshore
Repository
jeremylongshore/claude-code-plugins-plus-skills
Created
7 months ago
Last Updated
today
Language
Python
License
MIT

Integrates with

Similar Skills

Semantically similar based on skill content — not just same category

AI & Automation Featured

lokalise-data-handling

Implement Lokalise translation data handling, PII management, and compliance patterns. Use when handling sensitive translation data, implementing data redaction, or ensuring compliance with privacy regulations for Lokalise integrations. Trigger with phrases like "lokalise data", "lokalise PII", "lokalise GDPR", "lokalise data retention", "lokalise privacy", "lokalise compliance".

2,266 Updated today
jeremylongshore
AI & Automation Featured

lokalise-hello-world

Create a minimal working Lokalise example. Use when starting a new Lokalise integration, testing your setup, or learning basic Lokalise API patterns. Trigger with phrases like "lokalise hello world", "lokalise example", "lokalise quick start", "simple lokalise code".

2,266 Updated today
jeremylongshore
AI & Automation Featured

lokalise-sdk-patterns

Apply production-ready Lokalise SDK patterns for TypeScript and Node.js. Use when implementing Lokalise integrations, refactoring SDK usage, or establishing team coding standards for Lokalise. Trigger with phrases like "lokalise SDK patterns", "lokalise best practices", "lokalise code patterns", "idiomatic lokalise".

2,266 Updated today
jeremylongshore
AI & Automation Featured

lokalise-security-basics

Apply Lokalise security best practices for API tokens and access control. Use when securing API tokens, implementing least privilege access, or auditing Lokalise security configuration. Trigger with phrases like "lokalise security", "lokalise secrets", "secure lokalise", "lokalise API token security".

2,266 Updated today
jeremylongshore
AI & Automation Featured

lokalise-rate-limits

Implement Lokalise rate limiting, backoff, and request queuing patterns. Use when handling rate limit errors, implementing retry logic, or optimizing API request throughput for Lokalise. Trigger with phrases like "lokalise rate limit", "lokalise throttling", "lokalise 429", "lokalise retry", "lokalise backoff".

2,266 Updated today
jeremylongshore