observability-integrator

Name: observability-integrator
Availability: InStock
Author: mymx2

Design observability frameworks for Kotlin and Spring services with telemetry aligned to SLO targets.

4|Updated Jun 10, 2026

Search Tags:#monitoring #observability #telemetry #kotlin #opentelemetry #spring

Ready to run

npx skills add https://github.com/mymx2/foreman --skill observability-integrator-mymx2

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: observability-integrator
Source: https://github.com/mymx2/foreman/tree/main/.qoder/skills.collected/skills/observability-integrator
Command: npx skills add https://github.com/mymx2/foreman --skill observability-integrator-mymx2

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill addresses the challenge of creating meaningful, operational telemetry that helps engineers diagnose production issues rather than just collecting vanity metrics.

Core Features & Use Cases

Strategic Instrumentation: Focuses on defining operational questions before adding metrics, logs, or traces.
Operational Guardrails: Provides strict rules for cardinality management, PII redaction, and trace propagation in async/coroutine environments.
Use Case: Use this skill when you need to instrument a new Kotlin Spring service to ensure that your metrics, logs, and traces provide clear signals for incident response and SLO monitoring.

Quick Start

Use the observability-integrator skill to design a comprehensive telemetry plan for the current Kotlin Spring service.

Frequently Asked Questions about observability-integrator

High-intent search queries and answers about installing and using this skill.

FAQPage Schema

How do I design observability for Kotlin Spring services to avoid vanity metrics?▼

Designing observability for Kotlin Spring services requires defining operational questions and SLO targets before instrumenting logs, metrics, and traces. This approach ensures telemetry provides clear signals for incident response rather than vanity metrics.

What is the best way to manage telemetry cardinality in async Kotlin coroutine architectures?▼

Managing telemetry cardinality in async Kotlin coroutine architectures involves applying strict operational guardrails during instrumentation. This ensures trace propagation and PII redaction are handled correctly while maintaining production-grade performance and cost efficiency.

How do I instrument distributed traces across complex async and coroutine-based Spring services?▼

Instrumenting distributed traces across async and coroutine-based Spring services requires aligning telemetry with operational questions. This ensures technical requirements for trace propagation and health monitoring are met without compromising performance.

Does OpenTelemetry work with Kotlin Spring services for SLO monitoring?▼

OpenTelemetry works with Kotlin Spring services by aligning telemetry instrumentation with operational questions and SLO targets. This ensures logs, metrics, and traces provide actionable signals for health monitoring and incident response.

When do I need to align telemetry with operational questions for production-grade performance?▼

You need to align telemetry with operational questions whenever instrumenting a new Kotlin Spring service to ensure production-grade performance. This prevents high cardinality costs and ensures metrics, logs, and traces support SLO monitoring and incident response.

Why does trace propagation break in Kotlin coroutine environments and how do I fix it?▼

Trace propagation breaks in Kotlin coroutine environments due to async context switching, but applying strict operational guardrails during instrumentation fixes this. This ensures distributed traces remain intact while maintaining cost efficiency.