From scm-return-34163-apmail-geronimo-scm-archive=geronimo.apache.org@geronimo.apache.org Wed Dec 03 05:48:30 2008 Return-Path: Delivered-To: apmail-geronimo-scm-archive@www.apache.org Received: (qmail 30862 invoked from network); 3 Dec 2008 05:48:30 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.2) by minotaur.apache.org with SMTP; 3 Dec 2008 05:48:30 -0000 Received: (qmail 91606 invoked by uid 500); 3 Dec 2008 05:48:42 -0000 Delivered-To: apmail-geronimo-scm-archive@geronimo.apache.org Received: (qmail 91597 invoked by uid 500); 3 Dec 2008 05:48:42 -0000 Mailing-List: contact scm-help@geronimo.apache.org; run by ezmlm Precedence: bulk list-help: list-unsubscribe: List-Post: Reply-To: dev@geronimo.apache.org List-Id: Delivered-To: mailing list scm@geronimo.apache.org Received: (qmail 91586 invoked by uid 99); 3 Dec 2008 05:48:41 -0000 Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 02 Dec 2008 21:48:41 -0800 X-ASF-Spam-Status: No, hits=-1994.1 required=10.0 tests=ALL_TRUSTED,HTML_MESSAGE,MIME_HTML_ONLY,OBFUSCATING_COMMENT X-Spam-Check-By: apache.org Received: from [140.211.11.140] (HELO brutus.apache.org) (140.211.11.140) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 03 Dec 2008 05:47:12 +0000 Received: from brutus (localhost [127.0.0.1]) by brutus.apache.org (Postfix) with ESMTP id 08E94234C298 for ; Tue, 2 Dec 2008 21:48:00 -0800 (PST) Message-ID: <975529642.1228283280021.JavaMail.www-data@brutus> Date: Tue, 2 Dec 2008 21:48:00 -0800 (PST) From: confluence@apache.org To: scm@geronimo.apache.org Subject: [CONF] Apache Geronimo v2.2: Monitoring performance of remote servers (page edited) MIME-Version: 1.0 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: 7bit X-Virus-Checked: Checked by ClamAV on apache.org

Monitoring performance of remote servers has been edited by Runhua Chi (Dec 02, 2008).

(View changes)

Content:

For monitoring the Web server performance the Monitoring portlet is available by selecting Monitoring on the Console Navigation menu on the left hand side. This feature will allow you to view a number of server statistics on the system JVM, web servers, and information via the AJP protocol. The graph information is provided by the data exposed by the connector MBean.

This article shows one such way of monitoring server information. For this example, we attempt to determine if there is a correlation between the server JVM heap space and the web containers number of bytes downloaded. In other words, this monitoring session will show if the server is releasing heap memory after client downloads.

First, select the Monitoring link on the Console Navigation menu. If this is your first monitoring session, you should see an empty set of Servers, Views, and Graphs as shown in this figure.

Adding a Server

Select a server to monitor by providing a host name or IP address. Select the protocol for communication and any security credentials. Save this server definition by pressing Save.

Adding a Graph

Select information to display by adding a graph. Select the server you are monitoring, and then choose an MBean that publishes server information by choosing an MBean from the MBean drop down control. Once you have selected an MBean, you can see what information is available by selecting data from the Data series drop down control. When you have described the data, save this graph by pressing Save.

Select more information to display by adding a second graph. As the two data series scroll in time, we will be able to detect any correlation between the data. Once again, choose a server and an MBean to monitor. Select data from the Data series drop down control. Since data sent increases over time, also select delta for the Data series, so we see the rise and fall of the data over time. Save this graph by pressing Save.

Adding a View

Now group one or more graphs into a view. Here we add a view for "JVM vs Bytes Sent" by selecting two of the graphs we created in earlier steps. Save the view by pressing Save.

This figure shows the console monitoring portlet after we have added the server, graphs, and views.

The Monitoring Graph View

Click on a view to start monitoring server information over time. This view shows the JVM heap and web server bytes sent over a one hour period. As you see in the example, the JVM heap memory goes up and down over time with little correlation to the number of bytes users request from the web server.