メニュー
OpenTelemetry, distributed tracing, structured logging, metrics (Prometheus, Grafana, Datadog). Use when implementing monitoring, tracing, or debugging production issues.
Codex または Claude でインストール この Prompt をコピーして Codex、Claude、または他のアシスタントに貼り付けると、Skill ページを確認してインストールできます。
SOC 職業分類に基づく
Docker & Hadolint validation (2026). Use when working with Docker, containers, or validating Dockerfiles.
Security guidelines and OWASP Top 10. Use when reviewing security, implementing authentication or authorization, hardening code, or discussing vulnerabilities.
Third-party Claude Code token/context/code-review tools. Use when choosing or recommending an external tool to reduce token usage, manage context, or review large codebases (caveman, code-review-graph, token-savior, context-mode...).
Third-party Claude Code token/context/code-review tools. Use when choosing or recommending an external tool to reduce token usage, manage context, or review large codebases.
Testing Flutter 3.44 / BLoC v9 / Riverpod 3 - Stratégie Complète. Use when writing tests, reviewing test coverage, or setting up testing.
Testing React Native 0.85+. Use when writing tests, reviewing test coverage, or setting up testing.
| name | observability |
| description | OpenTelemetry, distributed tracing, structured logging, metrics (Prometheus, Grafana, Datadog). Use when implementing monitoring, tracing, or debugging production issues. |
| triggers | {"files":["**/otel*","**/prometheus*","**/grafana*","**/jaeger*","**/tempo*","**/loki*"],"keywords":["opentelemetry","otel","tracing","distributed tracing","prometheus","grafana","datadog","structured logging","metrics","observability","monitoring","SLI","SLO","golden signals"]} |
| auto_suggest | true |
Instrumentation moderne avec OpenTelemetry pour métriques, traces et logs structurés.
| Pilier | Technologies | Métriques clés |
|---|---|---|
| Metrics | Prometheus, Grafana, Datadog | RED (Rate, Errors, Duration), USE (Utilization, Saturation, Errors) |
| Traces | OpenTelemetry, Jaeger, Tempo | P95 latency, span duration, error rate |
| Logs | Loki, ElasticSearch, Datadog | Structured JSON, correlation IDs |
// Node.js — Auto-instrumentation
const { NodeSDK } = require('@opentelemetry/sdk-node');
const { getNodeAutoInstrumentations } = require('@opentelemetry/auto-instrumentations-node');
const sdk = new NodeSDK({
traceExporter: new OTLPTraceExporter(),
instrumentations: [getNodeAutoInstrumentations()],
});
sdk.start();
| Signal | Description | Seuil typique |
|---|---|---|
| Latency | P50, P95, P99 response time | P95 < 200ms |
| Traffic | Requests per second | Baseline + alerting |
| Errors | Error rate (5xx, exceptions) | < 0.1% |
| Saturation | CPU, Memory, Disk | < 80% sustained |
{
"timestamp": "2026-04-17T10:30:00Z",
"level": "error",
"message": "Payment processing failed",
"trace_id": "4bf92f3577b34da6a3ce929d0e0e4736",
"span_id": "00f067aa0ba902b7",
"service.name": "payment-api",
"error.type": "PaymentGatewayTimeout"
}
| Concept | Exemple |
|---|---|
| SLI (Indicator) | 99.5% requests < 200ms |
| SLO (Objective) | 99.9% uptime mensuel |
| SLA (Agreement) | 99.95% uptime + pénalités |
Pour instrumentation détaillée par stack : invoquer @observability-engineer