spring-boot-observability
Spring Boot 4 observability with Actuator, Micrometer, and OpenTelemetry. Use when configuring health indicators, health checks, custom metrics, distributed tracing, production endpoint exposure, Kubernetes probes, Cloud Run probes, logging, or monitoring. Covers Actuator endpoint security, Micrometer Timer/Counter/Gauge patterns, OpenTelemetry span customization, liveness/readiness probe setup, and metric tag best practices.
What this skill does
# Spring Boot Observability Production observability with Actuator endpoints, Micrometer metrics, and OpenTelemetry tracing. ## Core Components | Component | Purpose | |-----------|---------| | **Actuator** | Health checks, info, metrics exposure, operational endpoints | | **Micrometer** | Metrics abstraction (Timer, Counter, Gauge, DistributionSummary) | | **OpenTelemetry** | Distributed tracing (default in Spring Boot 4) | ## Core Workflow 1. **Add starters** → `actuator`, `micrometer-registry-*`, `opentelemetry` 2. **Configure endpoint exposure** → Secure sensitive endpoints 3. **Define health groups** → Separate liveness from readiness 4. **Add custom metrics** → Business-specific measurements 5. **Configure tracing** → Sampling, propagation, export ## Quick Patterns See [EXAMPLES.md](EXAMPLES.md) for complete working examples including: - **Production Actuator Configuration** with health groups and Kubernetes probes - **Custom Health Indicator** with latency monitoring (Java + Kotlin) - **Custom Micrometer Metrics** with Counter, Timer, and Gauge patterns - **OpenTelemetry Span Customization** with Observation API - **OpenTelemetry Configuration** for OTLP export - **Actuator Endpoint Access Control** (Boot 4) ## Spring Boot 4 Specifics - **OpenTelemetry** is the default tracer (replaces Brave) - **Health Indicator** imports from `org.springframework.boot.health.contributor.*` - **Endpoint Access Control** with `access: none/unrestricted/read-only` ## Detailed References - **Examples**: See [EXAMPLES.md](EXAMPLES.md) for complete working code examples - **Troubleshooting**: See [TROUBLESHOOTING.md](TROUBLESHOOTING.md) for common issues and Boot 4 migration - **Actuator Endpoints**: See [references/ACTUATOR.md](references/ACTUATOR.md) for endpoint configuration, security, custom endpoints - **Micrometer Metrics**: See [references/METRICS.md](references/METRICS.md) for Timer, Counter, Gauge, DistributionSummary patterns - **Distributed Tracing**: See [references/TRACING.md](references/TRACING.md) for OpenTelemetry, span customization, context propagation ## Anti-Pattern Checklist | Anti-Pattern | Fix | |--------------|-----| | DB checks in liveness probe | Move to readiness group only | | 100% trace sampling in production | Use 10% or less | | Exposing all endpoints publicly | Separate management port + auth | | High-cardinality metric tags | Use low-cardinality tags only | | Missing graceful shutdown | Add `server.shutdown=graceful` | | No health probe groups | Separate liveness and readiness | ## Related Skills | Need | Skill | |------|-------| | Dependency validation | `spring-boot-verify` | | Actuator security | `spring-boot-security` | | Actuator testing | `spring-boot-testing` | | Module metrics | `spring-boot-modulith` | ## Critical Reminders 1. **Separate liveness from readiness** — Liveness: "is process alive?", Readiness: "can handle traffic?" 2. **Low cardinality tags only** — User IDs, request IDs = bad; status codes, regions = good 3. **Secure Actuator endpoints** — Use separate port or authentication 4. **Sample traces in production** — 100% sampling overwhelms collectors 5. **Graceful shutdown** — Allow in-flight requests to complete
Related in Cloud & DevOps
appbuilder-action-scaffolder
IncludedCreate, implement, deploy, and debug Adobe Runtime actions with consistent layout, validation, and error handling. Use this skill whenever the user needs to add actions to an App Builder project, understand action structure (params, response format, web/raw actions), configure actions in the manifest, use App Builder SDKs (State, Files, Events, database), deploy and invoke actions via CLI, debug action issues, or implement patterns such as webhook receivers, custom event providers, journaling consumers, large payload redirects, action sequence pipelines, and Asset Compute workers. Also trigger when users mention serverless functions in Adobe context, action logging, IMS authentication for actions, or cron-style scheduled actions.
orchestrating-datacloud
IncludedSalesforce Data Cloud product orchestrator for connect→prepare→harmonize→segment→act workflows. Use this skill when the user needs a multi-step Data Cloud pipeline, cross-phase troubleshooting, or data space and data kit management. TRIGGER when: user needs a multi-step Data Cloud pipeline, asks to set up or troubleshoot Data Cloud across phases, manages data spaces or data kits, or wants a cross-phase sf data360 workflow. DO NOT TRIGGER when: work is isolated to a single phase (use the matching phase-specific skill), the task is STDM/session tracing/parquet telemetry (use observing-agentforce), standard CRM SOQL (use querying-soql), or Apex implementation (use generating-apex).
github-project-automation
IncludedAutomate GitHub repository setup with CI/CD workflows, issue templates, Dependabot, and CodeQL security scanning. Includes 12 production-tested workflows and prevents 18 errors: YAML syntax, action pinning, and configuration. Use when: setting up GitHub Actions CI/CD, creating issue/PR templates, enabling Dependabot or CodeQL scanning, deploying to Cloudflare Workers, implementing matrix testing, or troubleshooting YAML indentation, action version pinning, secrets syntax, runner versions, or CodeQL configuration. Keywords: github actions, github workflow, ci/cd, issue templates, pull request templates, dependabot, codeql, security scanning, yaml syntax, github automation, repository setup, workflow templates, github actions matrix, secrets management, branch protection, codeowners, github projects, continuous integration, continuous deployment, workflow syntax error, action version pinning, runner version, github context, yaml indentation error
sf-datacloud
IncludedSalesforce Data Cloud product orchestrator for connect→prepare→harmonize→segment→act workflows. TRIGGER when: user needs a multi-step Data Cloud pipeline, asks to set up or troubleshoot Data Cloud across phases, manages data spaces or data kits, or wants a cross-phase `sf data360` workflow. DO NOT TRIGGER when: work is isolated to a single phase (use the matching sf-datacloud-* skill), the task is STDM/session tracing/parquet telemetry (use sf-ai-agentforce-observability), standard CRM SOQL (use sf-soql), or Apex implementation (use sf-apex).
fabric-cli
IncludedUse this skill for Fabric.so CLI workflows with the `fabric` terminal command: diagnose/install/login, search or browse a Fabric library, save notes/links/files, create folders, ask the Fabric AI assistant, manage tasks/workspaces, generate shell completion, check subscription usage, produce JSON output, and use Fabric as persistent agent memory. Do not use for Microsoft Fabric/Azure/Power BI `fab`, Daniel Miessler's Fabric framework, Python Fabric SSH, Fabric.js, or textile/fashion fabric.
lark
IncludedLark/Feishu CLI skills: lark-cli operations for docs, markdown, sheets, base, calendar, im, mail, task, okr, drive, wiki, slides, whiteboard, apps, approval, attendance, contact, vc, minutes, event. Use when the user needs to operate Lark/Feishu resources via lark-cli, send messages, manage documents, spreadsheets, calendars, tasks, OKRs, deploy web pages, or any Feishu/Lark workspace operations.