Production Observability logo

Production Observability

Community
rrezartprebreza
production-observability

Use when adding service-wide Spring Boot 3 Actuator, Micrometer metrics, distributed tracing, OpenTelemetry export, structured logging, health probes, dashboards, or alerts. Combine with ai-observability only for Spring AI-specific token, prompt, and model telemetry.

Overview

Publisherrrezartprebreza
Repositoryspring-boot-skills
Skill nameproduction-observability
Stars
322
Forks
52
Bundled files
3
LicenseMIT
Links
  • Markdown instructions

    A SKILL.md file the model loads on demand, so it only costs tokens when a request actually matches.

  • Works with any LLM

    AI skills are plain Markdown, not provider-specific code, so this works with GPT, Claude, Gemini, Grok, or a local model.

  • 3 bundled files

    Scripts, templates, and references the model can read while it works. Files are read-only and never executed.

  • Open source

    Published by rrezartprebreza on GitHub. Read the source before you install it.

Installation

Install the Production Observability AI skill in TypingMind to use it with any LLM, or drop it into another agent that reads SKILL.md.

1

Install in TypingMind

TypingMind installs a skill straight from its GitHub folder — it reads SKILL.md, bundles the resource files, and stores the result locally.

  1. Open the app and go to Plugins → Skills.
  2. Choose "Install from GitHub".
  3. Paste the skill folder URL below and confirm.
    https://github.com/rrezartprebreza/spring-boot-skills/tree/main/skills/spring-boot-3/production-observability
  4. Enable the skill in any chat where you want it available.
Plugins → Skills → Add skill → From GitHub URL, then paste the folder URL and press Continue.
2

Install in another agent

Any agent that reads the Agent Skills format can use this skill — copy the folder into that agent's skills directory.

Claude Code — .claude/skills
git clone --depth 1 https://github.com/rrezartprebreza/spring-boot-skills.git /tmp/spring-boot-skills
mkdir -p .claude/skills
cp -r /tmp/spring-boot-skills/skills/spring-boot-3/production-observability .claude/skills/production-observability
Restart Claude Code after copying so it picks up the new skill.

Use it in TypingMind

Enable Production Observability in any TypingMind chat and the model takes it from there. Its name and description sit in the system prompt, and the moment a request matches, the model loads the full instructions itself — you never invoke it by hand, and it costs no tokens until it is actually used.

The model loads Production Observability on its own as soon as a request matches it.

Works with any AI model

AI skills are plain Markdown instructions rather than provider-specific code, so Production Observability is not tied to the model it was written for. Install it once in TypingMind and use it with GPT-5, Claude, Gemini, Grok, DeepSeek, Mistral, Llama, or a local model you run yourself — all on your own API keys.

  • Loaded only when it is needed

    The system prompt carries just the name and description. The instructions are fetched on the first matching request, so an idle skill costs nothing.

  • Switch models mid-chat

    Because the skill is instructions rather than code, changing model does not break it — the next model reads the same SKILL.md.

Skill instructions

This is the SKILL.md content the model loads. Read it before installing — a skill is instructions your model will follow.

Production Observability

Instrument user-visible operations and operational boundaries, not every method.

Baseline

  • Add Actuator and one metrics registry selected by the deployment platform.
  • Use Micrometer Observation for application metrics and traces.
  • Use Micrometer Tracing with the chosen bridge; do not mix tracing APIs throughout business code.
  • Export through OTLP when the platform standardizes on OpenTelemetry collectors.
  • Expose only required actuator endpoints and secure every non-public endpoint.

Observation conventions

  • Name observations by stable operation, such as orders.create.
  • Keep metric tags low-cardinality: method, outcome, region, or bounded status.
  • Put request IDs, user IDs, order IDs, and exception messages only in traces or logs.
  • Propagate context across @Async, executor, and Reactor boundaries.
  • Record latency, throughput, failures, and saturation for every external dependency.

Health and readiness

  • Keep liveness independent from remote systems so a dependency outage does not restart every pod.
  • Put required dependencies in readiness groups.
  • Write custom health indicators only for dependencies that affect traffic acceptance.
  • Set explicit timeouts on health checks.

Logging and alerts

  • Emit structured logs with trace and span correlation.
  • Redact credentials, tokens, personal data, prompts, and payloads by default.
  • Alert on symptoms tied to service objectives, not raw metric noise.
  • Include runbook links and enough dimensions to identify the affected service and dependency.

Examples

  • See examples/good-observation.java and examples/bad-observation.java.

Gotchas

  • Agent tags metrics with user or entity IDs - this creates unbounded cardinality.
  • Agent exposes every actuator endpoint publicly - expose the minimum and secure it.
  • Agent makes liveness depend on the database - dependency outages then cause restart loops.
  • Agent logs request bodies and tokens for debugging - redact sensitive data before emission.
  • Agent creates spans but loses context in async work - configure context propagation explicitly.

Bundled files

The model reads these on demand while the skill is loaded. They are exposed as readable files and are never executed.

Frequently asked questions

What does the Production Observability AI skill do?

Use when adding service-wide Spring Boot 3 Actuator, Micrometer metrics, distributed tracing, OpenTelemetry export, structured logging, health probes, dashboards, or alerts. Combine with ai-observability only for Spring AI-specific token, prompt, and model telemetry.

Why use Production Observability on TypingMind?

Because you install it once and use it with any model. Production Observability is plain Markdown rather than provider-specific code, so the same skill runs on GPT-5, Claude, Gemini, Grok, or a local model — and you can switch model mid-chat without it breaking. TypingMind runs on your own API keys, so you pay providers directly instead of a per-seat subscription, and your skills and chats stay in your own storage.

How do I install Production Observability in TypingMind?

Open Plugins → Skills → Install from GitHub in TypingMind and paste https://github.com/rrezartprebreza/spring-boot-skills/tree/main/skills/spring-boot-3/production-observability. TypingMind reads its SKILL.md and bundles its files and installs it as a skill you can enable per chat.

Which AI models can use Production Observability?

Any model you connect in TypingMind. AI skills are plain Markdown instructions rather than provider-specific code, so GPT, Claude, Gemini, Grok, and local models can all load this skill when a request matches it.

How many AI models can I use with Production Observability?

As many as you like. As long as a model supports skills, you can use Production Observability with it — GPT, Claude, Gemini, Grok, DeepSeek, Mistral, Llama and more — all on TypingMind with your own API keys.

Is the Production Observability AI skill free?

Yes. It is published on GitHub by rrezartprebreza under the MIT license. You only pay your own AI provider for the tokens you use.

What are AI skills?

An AI skill is a reusable instruction bundle that teaches an AI model how to do one specific task. It follows the open Agent Skills format: a SKILL.md file with a name and description, plus any scripts, templates or reference files the model may need. The model reads the instructions only when your request matches the skill, so an installed skill costs nothing until it is used.

How are AI skills different from plugins or MCP servers?

A plugin or MCP server gives a model new tools to call — code that runs somewhere and returns a result. An AI skill gives the model knowledge and process instead: how to approach a task, which steps to follow, what good output looks like. Skills are plain Markdown, so they need no server, no API key and no runtime, and they work with any model.

View all

Set up your own AI workspace now

Get notified about new features and future giveaways by subscribing to our newsletter 👇