Java Spring Boot 2 application monitoring with Netdata
This module monitors one or more Java Spring-boot 2 applications depending on configuration. Netdata can be used to monitor running Java Spring Boot 2 applications that expose their metrics with the use of the Spring Boot Actuator included in Spring Boot library.
Springboot2 module looks up http://localhost:8080/actuator/prometheus and http://127.0.0.1:8080/actuator/prometheus
to detect Spring Boot application by default.
Charts#
- Response Codes in
requests/s - Threads in
threads - Heap Memory Usage Overview in
bytes - Heap Memory Usage Eden Space in
bytes - Heap Memory Usage Survivor Space in
bytes - Heap Memory Usage Old Space in
bytes - Uptime in
seconds
Configuration#
Edit the go.d/springboot2.conf configuration file using edit-config from the
Netdata config directory, which is typically at /etc/netdata.
The Spring Boot Actuator exposes these metrics over HTTP and is very easy to use:
- add
org.springframework.boot:spring-boot-starter-actuatorandio.micrometer:micrometer-registry-prometheusto your application dependencies - set
management.endpoints.web.exposure.include=*in yourapplication.properties
Please refer to the Spring Boot Actuator: Production-ready features and 81. Actuator - Part IX. ‘How-to’ guides for more information.
Here is an example for 2 servers:
For all available options please see module configuration file.
Troubleshooting#
To troubleshoot issues with the springboot2 collector, run the go.d.plugin with the debug option enabled. The output
should give you clues as to why the collector isn't working.
First, navigate to your plugins directory, usually at /usr/libexec/netdata/plugins.d/. If that's not the case on your
system, open netdata.conf and look for the setting plugins directory. Once you're in the plugin's directory, switch
to the netdata user.
You can now run the go.d.plugin to debug the collector: