Monitoring Java Applications: Tools and Best Practices

Monitoring Java Applications: From Basics to Production Solutions

Monitoring Java applications is a critically important practice for ensuring the stability, performance, and fault tolerance of modern server systems. Without quality monitoring, it is impossible to timely detect memory leaks, thread issues, performance degradation, or errors in business logic. In this article, we will review key tools and libraries for monitoring Java, from built-in JVM tools to modern solutions based on Micrometer, Prometheus, and Grafana.

Why is Monitoring Java Applications Necessary?

Java applications, especially those running 24/7, require constant observation for several reasons:

• Performance: tracking response time, throughput, CPU and memory load.
• Reliability: detecting errors, exceptions, connection failures to databases and external services.
• Scaling: understanding when to add resources or optimize code.
• Security: identifying anomalous activity and potential vulnerabilities.

Built-in Tools: JMX and JConsole

Java Management Extensions (JMX) is a standard mechanism for monitoring and managing the JVM. It allows you to obtain information about memory, threads, class loading, garbage collection, and the state of MBean components. Use JConsole or VisualVM to connect to a remote application.

Example of enabling JMX when starting an application:

java -Dcom.sun.management.jmxremote \     -Dcom.sun.management.jmxremote.port=9010 \     -Dcom.sun.management.jmxremote.local.only=false \     -Dcom.sun.management.jmxremote.authenticate=false \     -Dcom.sun.management.jmxremote.ssl=false \     -jar myapp.jar

Disadvantage: JMX provides raw data but cannot aggregate metrics or build graphs. Full monitoring requires integration with external systems.

Micrometer: A Facade for Metrics

Micrometer is a facade library that provides a unified API for collecting metrics in Java applications. It supports most popular monitoring systems: Prometheus, Datadog, New Relic, Graphite, InfluxDB, and others. Micrometer integrates with Spring Boot, Micronaut, Quarkus, and other frameworks.

Example of adding Micrometer to a Maven project:

<dependency>    <groupId>io.micrometer</groupId>    <artifactId>micrometer-registry-prometheus</artifactId>    <version>1.12.5</version></dependency>

Example of creating and registering a custom metric:

import io.micrometer.core.instrument.MeterRegistry;import io.micrometer.core.instrument.Counter;import org.springframework.stereotype.Component;

@Componentpublic class OrderMetrics {    private final Counter orderCreatedCounter;

    public OrderMetrics(MeterRegistry registry) {        this.orderCreatedCounter = Counter.builder("orders.created")                .description("Number of created orders")                .tag("region", "ru-central1")                .register(registry);    }

    public void recordOrderCreated() {        orderCreatedCounter.increment();    }}

Micrometer supports several metric types:

• Counter — a counter that only increases.
• Gauge — a current value (e.g., queue size).
• Timer — execution time of operations.
• DistributionSummary — distribution of values.

Prometheus: Collecting and Storing Metrics

Prometheus is an open-source system for collecting and storing metrics. It works