This will emit Prometheus metrics to port 9404.īe sure to replace the entry point .App with the correct Java application with the Prometheus exporter pattern: 'Catalina(processingTime|sessionCounter|rejectedSessions|expiredSessions)' pattern: 'Catalina(currentThreadCount|currentThreadsBusy|keepAliveCount|pollerThreadCount|connectionCount)' pattern: 'Catalina(requestCount|maxTime|processingTime|errorCount)' Name: catalina_globalrequestprocessor_$3_total pattern: 'java.lang(TotalStartedThreadCount|ThreadCount)' pattern: 'java.lang(FreePhysicalMemorySize|TotalPhysicalMemorySize|FreeSwapSpaceSize|TotalSwapSpaceSize|SystemCpuLoad|ProcessCpuLoad|OpenFileDescriptorCount|AvailableProcessors)' Here is a sample configuration for Java and Tomcat. The config.yaml file is the JMX exporter configuration file.įor more information, see Configuration in the JMX exporter documentation. Replace these parts of the commands with the jar for your application. The example commands in the following sections use The next step is to start the Java/JMX workload.įirst, download the latest JMX exporter jar file from the following location: Hjava, and Tomcat (Catalina), from a JMX exporter on EC2 instances. The CloudWatch agent can collect predefined Prometheus metrics from Java Virtual Machine (JVM), For more information, see prometheus/jmx_exporter. JMX Exporter is an official Prometheus exporter that can scrape and expose A sample configuration file contains the following global Update the configurations that are already in this file, and add additional The CloudWatch agent supports the standard Prometheus scrape configurations as documented The other is for theĬloudWatch agent configuration. One is for the standard Prometheus configurations as documented in The CloudWatch agent with Prometheus monitoring needs two configurations to scrape the The first step is to install the CloudWatch agent on the EC2 instance.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |