Skip to main content
skill CX Codex

181-java-observability-logging — Claude Code skill for Java logs

181-java-observability-logging is a Claude Code skill for improving Java logging and observability. It activates on requests to add, review, or refactor logging.

Apache-2.0 325 installs ★ 465 updated 2026-10-21

Install into Claude Code · Skills CLI (Vercel) All methods and platforms ↓
npx skills add jabrena/plinth --skill 181-java-observability-logging -a claude-code
Open on GitHub

What 181-java-observability-logging does

The skill assesses a Java project's logging setup and guides changes to framework choice, log levels, parameterized messages, and correlation context. Its scope also covers masking sensitive values, environment-specific configuration, log aggregation, monitoring, and alerts.

Before changing code, the agent runs ./mvnw compile or mvn compile and stops if compilation fails. It then reads references/181-java-observability-logging.md, which contains good and bad code examples, applies relevant changes, and runs ./mvnw clean verify or mvn clean verify. The project needs Maven or the Maven Wrapper.

What it helps with

  • choose between SLF4J with Logback and Log4j2
  • assign suitable ERROR, WARN, INFO, DEBUG, and TRACE levels
  • add correlation context and parameterized messages
  • mask sensitive values in log output
  • configure logging across environments and connect monitoring

Example prompts for the agent

  • Improve logging in this Java project and verify the build.
  • Review the log levels and remove sensitive values from log output.
  • Add correlation context and set up log monitoring.

How to install 181-java-observability-logging

1Skills CLI (Vercel)

npx skills add jabrena/plinth --skill 181-java-observability-logging -a claude-code

2Manually: put the files in place

~/.claude/skills/181-java-observability-logging/SKILL.md

Copy the whole skill folder; for one project use .claude/skills/181-java-observability-logging/

Step by step, with commands for each platform: How to install skills in Claude Code: five ways

Questions about 181-java-observability-logging

How do I install 181-java-observability-logging in Claude Code?

Run npx skills add jabrena/plinth --skill 181-java-observability-logging -a claude-code. The skill file is at ~/.claude/skills/181-java-observability-logging/SKILL.md.

What does 181-java-observability-logging do?

It guides changes to Java logging frameworks, levels, sensitive-data handling, environment-specific configuration, and monitoring.

What does 181-java-observability-logging need to run?

The project must support Maven through ./mvnw or mvn. The skill compiles before making changes and runs full verification afterward.

Source text

SKILL.md · Apache-2.0
---
name: 181-java-observability-logging
description: Use when you need to implement or improve Java logging and observability — including selecting SLF4J with Logback/Log4j2, applying proper log levels (ERROR, WARN, INFO, DEBUG, TRACE), parameterized logging, correlation context, secure logging without sensitive data exposure, environment-specific configuration, log aggregation, monitoring, and alerting. This should trigger for requests such as Improve logging; Apply logging; Refactor logging; Add logging support; Review SLF4J structured logging in Java code. Part of Plinth Toolkit
license: Apache-2.0
metadata:
  author: Juan Antonio Breña Moral
  version: 0.19.0
---
# Java Logging Best Practices

Implement effective Java logging following standardized frameworks, meaningful log levels, core practices (parameterized logging, exception handling, no sensitive data), explicit correlation context, flexible configuration, security-conscious logging, monitoring, and alerting.

**What is covered in this Skill?**

- Standardized framework selection: SLF4J facade with Logback or Log4j2
- Meaningful and consistent log levels: ERROR, WARN, INFO, DEBUG, TRACE
- Core practices: parameterized logging, proper exception handling, avoiding sensitive data
- Configuration: environment-specific (logback.xml, log4j2.xml), output formats, log rotation
- Security: mask sensitive data, control log access, secure transmission, GDPR/HIPAA compliance
- Log monitoring and alerting: centralized aggregation (ELK, Splunk, Loki), automated alerts

**Scope:** The reference is organized by examples (good/bad code patterns) for each core area. Apply recommendations based on applicable examples.

## Constraints

Before applying any logging recommendations, ensure the project compiles. Compilation failure is a blocking condition. After applying improvements, run full verification.

- **MANDATORY**: Run `./mvnw compile` or `mvn compile` before applying any change
- **SAFETY**: If compilation fails, stop immediately — do not proceed until resolved
- **VERIFY**: Run `./mvnw clean verify` or `mvn clean verify` after applying improvements
- **BEFORE APPLYING**: Read the reference for detailed good/bad examples, constraints, and safeguards for each logging pattern

## When to use this skill

- Improve logging
- Apply logging
- Refactor logging
- Add logging support
- Review SLF4J structured logging in Java code

## Workflow

1. **Compile project before logging changes**

Run `./mvnw compile` or `mvn compile` and stop immediately if compilation fails.

2. **Read logging reference and assess current observability**

Read `references/181-java-observability-logging.md` and evaluate framework usage, log levels, sensitive-data handling, and config gaps.

3. **Apply logging and observability improvements**

Implement selected framework/configuration/practice changes, including secure logging and monitoring integration where applicable.

4. **Verify with full build**

Run `./mvnw clean verify` or `mvn clean verify` after applying improvements.

## Reference

For detailed guidance, examples, and constraints, see [references/181-java-observability-logging.md](references/181-java-observability-logging.md).

© Juan Antonio Breña Moral · Apache-2.0 · jabrena/plinth

Similar skills

All skills for Backend and APIs →

From the same set123

The whole set →
423-frameworks-quarkus-testing-acceptance-tests Build Quarkus acceptance tests from Gherkin scenario facts reviewed and sanitized by a maintainer. Useful when a test needs to exercise the HTTP layer alongside its supporting infrastructure. CX Codex +1 330installs 304-frameworks-spring-boot-security 304-frameworks-spring-boot-security configures Spring Boot security, endpoint authorization, and SecurityFilterChain. It helps implement JWT resource servers, method security, and safe headers. CX Codex +1 328installs 145-java-refactoring-high-performance 145-java-refactoring-high-performance — a skill for refactoring Java code for performance: reduce memory allocations, optimize CPU hot paths, and improve syntax. Works with Claude Code, Cursor, GitHub Copilot, and other AI editors. CX Codex +1 327installs 303-frameworks-spring-boot-validation 303-frameworks-spring-boot-validation — a skill that tells your coding agent how to design and review Spring Boot validation: Bean Validation on DTOs, @Valid at API boundaries, constraint groups and consistent 400 responses. CX Codex +1 327installs 521-frameworks-micronaut-testing-unit-tests 521-frameworks-micronaut-testing-unit-tests enforces unit testing standards for Micronaut apps: prefers fast Mockito tests without context boots and reserves @MicronautTest for HTTP or @MockBean setups. CX Codex +1 324installs 501-frameworks-micronaut-core 501-frameworks-micronaut-core — a skill that reviews and fixes Micronaut Java code: beans, configuration, @Requires, scheduling and blocking I/O. CX Codex +1 323installs 522-frameworks-micronaut-testing-integration-tests 522-frameworks-micronaut-testing-integration-tests guides writing Micronaut integration tests using Testcontainers and Maven test configurations. CX Codex +1 323installs 044-planning-jira 044-planning-jira guides Jira CLI setup and enforces maintainer-authored, sanitized issue workflows without ingesting raw ticket data. CX Codex +1 322installs

Project sponsors

Companies that keep this analytics open