Page Comparison

...

Please see the WORKING WITH ... pages for further information of how the http timer can be used to monitor and diagnose your system.

Configuration

Configuration using UI configuration interface

Using the UI configuration interface no configuration is required at all as method sensor types are activated automatically if a profile defines such sensor assignment. 

Configuration using configuration file(s)

The http sensor needs to be defined in order to use it. This definition is already available within the sample inspectIT configuration file. In addition to just defining the sensor type, you can configure which data the http sensor should capture.

...

The Http sensor can capture information about the http session that is currently associated with the respective request. In the current realization the http sensor always captures the session attributes at the start of the invocation. In order to activate this capturing you need to specify the "sessioncapture" configuration setting to true. This  This capturing is disabled by default. Session capturing will never open a new http session, but just read data from an existing one.

Configuration using UI configuration interface

The HTTP session capturing setting is available under Sensor options part in the Environment configuration.

Configuration using configuration file(s)

 In order to activate this capturing you need to specify the "sessioncapture" configuration setting to true. 

method-sensor-type http info.novatec.inspectit.agent.sensor.method.http.HttpSensor MAX sessioncapture=true

...

Usually you do not need to change the assignment of the http sensor as inspectIT provides an out-of-the-box assignment for the http sensor. You can have a look at this instrumentation at the file http.cfg in the Out-of-the-box instrumentation or in the HTTP Common profile if you are using UI configuration. If you want to make additional assignments, please be aware of the following rules:

...

Regular expression URI modification

^{from version 1.5}

Configuration using configuration file(s)

The HTTP sensor definition brings the possibility to define the regular expression that can be used to transform the URI during the analysis in the User interface. The following example extracts the second part of the URI:

...

With following settings, when activated in the User interface, following URI transformation occur:

From above we can conclude that all the dvd actions have been grouped to one single group.

Defining Templates

Configuration using configuration file(s)

It is also possible to define the template that will be displayed in combination with the transformed URI. For example, the following settings:

...

will substitute the $1$ marker with the first extracted group from the regular expression transformation. The same set of URI from the previous example, would now look like this:

It is also possible to extract more groups with the regular expression and combine them into more meaningful transformation output. Since the first part of the example URIs we have is dvdstore, it is clear that that represents the name of our application. Thus, with following settings:

...

We would extract both first and second part of the URI and with defined template, the example results would look like this:

...