← Explore all skills

CLOUD OPERATIONS / JetBrains

Observability Integrator

Designs instrumentation that answers operational questions instead of filling dashboards: metrics tied to user journeys with a cardinality budget, structured logs with stable correlation identifiers and PII redaction by policy, trace propagation across async and coroutine boundaries, deliberate sampling, and liveness/readiness/startup health semantics.

“Design actionable observability for Kotlin plus Spring services across logs, metrics, tracing, and health endpoints. Use when instrumenting a service, improving incident diagnosis, defining SLO-driven metrics and alerts, adding trace propagation, controlling metric-cardinality cost, or ensuring async and coroutine flows remain observable in production.”

01 / THE REASONING

Why this made the selection.

  • Starts from the operational questions the instrumentation must answer — is the service healthy, which journey is slow, which dependency is failing, where is saturation growing — and explicitly rejects vanity dashboards.
  • Treats cardinality as a budget and names the labels that break it (raw user ids, full URLs, free-form exception messages), and notes that such labels make a metric unusable and expensive at the same time.
  • Covers the propagation traps that silently destroy correlation: executors, coroutine contexts and listeners failing to carry trace context even when HTTP tracing looks fine.

02 / THE REVIEW RECORD

What we actually inspected.

Source review has boundaries.
A clear record is more useful than a “safe” badge.

Material inspected

  • observability-integrator/SKILL.md (JetBrains mirror)
  • observability-integrator/agents directory listing
  • upstream yalishevant/kotlin-backend-agent-skills .agents/skills/observability-integrator/SKILL.md
  • upstream LICENSE
  • JetBrains/skills README mirror policy
  • https://github.com/Kotlin/kotlin-backend-agent-skills (answers HTTP 301 to yalishevant/kotlin-backend-agent-skills)
  • mirror SKILL.md diffed against the upstream SKILL.md at fd0ed521d22efd28221d532c9abab97af0b9bf0e

Our findings

  • The design sequence orders work by operational value — instrument the path that paged someone last time before the path that is merely interesting.
  • Distinguishes liveness, readiness and startup health semantics and warns that readiness depending on every optional downstream creates self-inflicted outages.
  • Cost and stability are first-class: burn-rate over static thresholds, histogram buckets chosen from user-facing latency objectives, and metric names treated as operator-facing APIs that must not be renamed casually.
  • A diff against the upstream SKILL.md at fd0ed521d22efd28221d532c9abab97af0b9bf0e shows the mirror adds four frontmatter lines (metadata, short-description, author: Kotlin, source) and nothing else; the upstream file has no author field. agents/openai.yaml is identical in both.
  • Upstream health: https://github.com/Kotlin/kotlin-backend-agent-skills, which the mirror’s metadata.source and README name, now answers HTTP 301 to yalishevant/kotlin-backend-agent-skills, a personal account (https://api.github.com/repos/Kotlin/kotlin-backend-agent-skills returns full_name yalishevant/kotlin-backend-agent-skills, owner type User). fd0ed521d22efd28221d532c9abab97af0b9bf0e is still that repository’s head, and its LICENSE (MIT, copyright 2026 Anton Yalyshev) is unchanged (checked 2026-10-13).

Not established by this review

  • No service was instrumented and no telemetry was emitted; the design rules were read, not executed.
  • The agents/openai.yaml companion file was noted but not exercised.

The review applies to the material and revision named here. A newer upstream release can change its behavior.

03 / PUT IT TO WORK

Add a skill to your workflow.

Upstream setup instructions ↗

DOCUMENTED COMMAND

npx skills add JetBrains/skills/observability-integrator --skill observability-integrator

Run in your terminal to choose your AI tools, project or global scope, and installation method. This short command follows the current upstream version; the review covers the revision shown above.

Optional: install the reviewed revision

Keeps the original source and installer version where recorded, while leaving your AI tools and installation scope for you to choose.

npx skills add https://github.com/JetBrains/skills/tree/e0f258b5cfed145015cb3e48da9a97947f7c4ed7/observability-integrator --skill observability-integrator
  1. Install the skill from the JetBrains mirror, or from the upstream Kotlin backend agent skills repository if you prefer the origin.
  2. Bring the service topology, SLO targets and the existing metrics or logging setup; the output contract expects them as inputs.

Before you start

  • Node.js/npm for the installer
  • An agent that supports the Agent Skills format
  • A service to instrument and a telemetry stack to receive it

04 / FOLLOW THE EVIDENCE

The source trail.

Our notes are separate from the original resource.
Check upstream before adopting a new version.

  1. https://github.com/JetBrains/skills/blob/e0f258b5cfed145015cb3e48da9a97947f7c4ed7/observability-integrator/SKILL.md

    Supports: summary, upstreamDescription, whySelected, bestFor, limitations, review, access

  2. https://github.com/yalishevant/kotlin-backend-agent-skills/blob/fd0ed521d22efd28221d532c9abab97af0b9bf0e/.agents/skills/observability-integrator/SKILL.md

    Supports: review, whySelected, limitations

  3. Upstream license (MIT) ↗Checked

    https://github.com/yalishevant/kotlin-backend-agent-skills/blob/fd0ed521d22efd28221d532c9abab97af0b9bf0e/LICENSE

    Supports: license

  4. https://github.com/Kotlin/kotlin-backend-agent-skills

    Supports: review, limitations

  5. https://github.com/JetBrains/skills/blob/e0f258b5cfed145015cb3e48da9a97947f7c4ed7/README.md

    Supports: review, install, limitations

  6. https://github.com/vercel-labs/skills/blob/7407f3893ad4dceab546ac002c3ef806e4000c73/README.md

    Supports: install

Evidence & Ask