dynamic-loglevel-rfc-27

Adjust runtime log levels for Java Spring Boot services via Developer Portal or Bitso CLI.

40|33|Updated Aug 20, 2015
One-click install
npx skills add https://github.com/bitsoex/bitso-java --skill dynamic-loglevel-rfc-27
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: dynamic-loglevel-rfc-27
Source: https://github.com/bitsoex/bitso-java/tree/main/.claude/skills/dynamic-loglevel-rfc-27
Command: npx skills add https://github.com/bitsoex/bitso-java --skill dynamic-loglevel-rfc-27

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill provides a standardized way to dynamically adjust the logging levels of Java services in real-time, simplifying debugging and operational monitoring without requiring service restarts.

Core Features & Use Cases

  • Runtime Log Level Adjustment: Change log levels (e.g., from INFO to DEBUG) for specific classes or packages on live services.
  • Standardized RFC-27 Compliance: Ensures consistent logging behavior across different services.
  • Developer Portal & CLI Integration: Manage log levels through user-friendly interfaces or automated scripts.
  • Use Case: When a critical issue arises in production, you can temporarily increase the log verbosity for the affected component to gather detailed diagnostic information, then revert it once the issue is resolved.

Quick Start

Use the dynamic-loglevel-rfc-27 skill to set the log level for the 'com.bitso.payments.processor' logger to DEBUG for 30 minutes.

Frequently Asked Questions about dynamic-loglevel-rfc-27

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

FAQPage Schema
How do I change Java Spring Boot logging levels at runtime without restarting the service?

Runtime log level control for Java Spring Boot services lets you dynamically adjust logging verbosity for specific classes or packages on live services without requiring restarts. This simplifies debugging production issues and operational monitoring in real-time.

What is RFC-27 compliance for dynamic log level configuration in Java services?

RFC-27 compliance ensures standardized, consistent logging behavior across different Java services. It provides a uniform approach to dynamically manage and adjust log level configurations via YAML frontmatter and operational commands.

Can I use the Developer Portal or Bitso CLI to adjust log levels for production debugging?

Yes, you can manage runtime log levels through the Developer Portal interface or automate adjustments via Bitso CLI. Both integrate with estate-catalog registered services to control logging verbosity for production debugging.

How do I temporarily set a specific package logger to DEBUG for diagnostic purposes?

You can temporarily increase log verbosity for an affected component, such as setting a package like 'com.bitso.payments.processor' to DEBUG for 30 minutes, to gather detailed diagnostic information, then revert it once the issue is resolved.

Does dynamic log level adjustment require my Java service to be registered in the estate-catalog?

Yes, enabling RFC-27 compliant runtime log level control requires your Java Spring Boot services to be registered in the estate-catalog to facilitate management via the Developer Portal or Bitso CLI.