In both cases the sFlow agent is included when starting the Java virtual machine and requires minimal configuration and no change to the application code. The articles, Java virtual machine and Tomcat, describes the steps needed to instrument existing Java applications and Apache Tomcat servlet engines respectively. Once configured, Ganglia will automatically discover and track new servers as they are added to the network. The article, Ganglia 3.2 released, describes the basic steps needed to configure Ganglia as an sFlow collector. Note: The Tomcat sFlow agent also allows Ganglia to report HTTP performance metrics. Instead, metrics are pushed directly from each Java virtual machine to the central Ganglia collector. The sFlow Java agent for stand-along Java services, or Tomcat sFlow for web-based servlets, simplify deployments by eliminating the need to poll for metrics using a Java JMX client. The combination of Ganglia and sFlow provides a highly scalable solution for monitoring the performance of clustered Java application servers. The Ganglia charts show the standard sFlow Java virtual machine metrics.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |