Skip to main content

Notice: this Wiki will be going read only early in 2024 and edits will no longer be possible. Please see: https://gitlab.eclipse.org/eclipsefdn/helpdesk/-/wikis/Wiki-shutdown-plan for the plan.

Jump to: navigation, search

Difference between revisions of "Jetty/Tutorial/Statistics"

(New page: {{Jetty Tutorial | introduction = Jetty allows collecting several types of statistics. This tutorial shows how to configure Jetty to enable collecting statistics, although it is not reco...)
 
Line 3: Line 3:
 
Jetty allows collecting several types of  statistics. This tutorial shows how to configure Jetty to enable collecting statistics, although it is not recommended and it is best to use a JMX agent to select statistics only when needed.
 
Jetty allows collecting several types of  statistics. This tutorial shows how to configure Jetty to enable collecting statistics, although it is not recommended and it is best to use a JMX agent to select statistics only when needed.
 
| details =  
 
| details =  
==Connector statistics==
+
===Connector statistics===
  
 
The following example shows how to turn on connector statistics in jetty.xml.
 
The following example shows how to turn on connector statistics in jetty.xml.
Line 19: Line 19:
 
</source>
 
</source>
  
==Request Statistics==
+
===Request Statistics===
  
 
To collect request statistics a StatisticsHandler must be configured as one of the handlers of the server. Typically this can be done as the top level handler, but you may choose to configure a statistics handler for just one context by creating a context configuration file.  The following jetty.xml fragment shows how to configure a top level statistics handler:
 
To collect request statistics a StatisticsHandler must be configured as one of the handlers of the server. Typically this can be done as the top level handler, but you may choose to configure a statistics handler for just one context by creating a context configuration file.  The following jetty.xml fragment shows how to configure a top level statistics handler:

Revision as of 09:12, 13 February 2010



Introduction

Jetty allows collecting several types of statistics. This tutorial shows how to configure Jetty to enable collecting statistics, although it is not recommended and it is best to use a JMX agent to select statistics only when needed.

Details

Connector statistics

The following example shows how to turn on connector statistics in jetty.xml.

<Item>
  <New class="org.mortbay.jetty.nio.SelectChannelConnector">
    <Set name="port">8080</Set>
    <Set name="maxIdleTime">30000</Set>
    <Set name="lowResourceMaxIdleTime">3000</Set>
    <Set name="Acceptors">1</Set>
    <Set name="StatsOn">true</Set>
  </New>
</Item>

Request Statistics

To collect request statistics a StatisticsHandler must be configured as one of the handlers of the server. Typically this can be done as the top level handler, but you may choose to configure a statistics handler for just one context by creating a context configuration file. The following jetty.xml fragment shows how to configure a top level statistics handler:

<!-- =========================================================== -->
<!-- Set handler Collection Structure                            -->
<!-- =========================================================== -->
<Set name="handler">
  <New class="org.mortbay.jetty.handler.StatisticsHandler">
    <Set name="handler">
      <New id="handlers" class="org.mortbay.jetty.handler.HandlerCollection">
        <Set name="handlers">
         <Array type="org.mortbay.jetty.Handler">
           <Item><New id="contexts" class="org.mortbay.jetty.handler.ContextHandlerCollection"/></Item>
           <Item><New id="defaultHandler" class="org.mortbay.jetty.handler.DefaultHandler"/></Item>
           <Item><New id="requestLog" class="org.mortbay.jetty.handler.RequestLogHandler"/></Item>
         </Array>
        </Set>
      </New>
    </Set>
  </New>
</Set>

Additional Resources

See Jetty JMX tutorial for instructions on how to configure Jetty JMX integration.

Back to the top