القائمة
APM setup for Node.js applications (Express, Fastify, Koa, NestJS)
التثبيت باستخدام Codex أو Claude انسخ هذا Prompt والصقه في Codex أو Claude أو مساعد آخر ليراجع صفحة Skill ويثبّتها لك.
استنادا إلى تصنيف SOC المهني
Debug and analyze LLM eval runs — view traces, compare runs, investigate failures, track costs. Use when debugging @kbn/evals failures, comparing eval runs, or analyzing LLM performance.
Start your security session with a personalized briefing — attacks, alerts, cases, rules, threat intel. Use as the first thing when starting security work.
Guide users from zero to a working Elastic cluster — Cloud or on-prem, connection config, first queries, and next steps.
Interactive guide for creating an APM service overview dashboard — discovers service data, presents metrics, and creates a tailored dashboard.
Interactive guide for creating SLOs from discovered APM and metric data — identifies candidates, lets user configure targets, and creates SLOs.
Create, configure, and manage Elasticsearch indices — mappings, settings, templates, data streams, and lifecycle policies.
| name | apm-nodejs |
| description | APM setup for Node.js applications (Express, Fastify, Koa, NestJS) |
Use when the user wants to add Elastic APM to a Node.js app.
get_connection_config or Cloud project setup.elastic-apm-node as a dependency.require('elastic-apm-node').start({ serverUrl, secretToken })./_otlp/):
@opentelemetry/exporter-metrics-otlp-proto (protobuf), NOT @opentelemetry/exporter-metrics-otlp-http (JSON). ES native OTLP only accepts application/x-protobuf and returns HTTP 406 for application/json.@opentelemetry/sdk-metrics major version (e.g. proto exporter 0.52.x for SDK 1.x; proto exporter 0.212.x for SDK 2.x).forceFlush() may resolve successfully even when the exporter fails silently (e.g. HTTP 406) — always verify data landed in ES after first export.