<<Previous | Next>>
There are 2 ways in which you can customize the behavior of InfraRED.
- By modifying the properties in infrared.properties and infrared.web.properties. After the properties are changed, the steps to integrate InfraRED with the application need to be followed again, for change to take effect.
- The properties can be changed on the Web GUI. This change will not be persisted to the properties file for future use. This approach is only applicable to local collection strategy.
The following properties in infrared.properties can be modified. If omitted InfraRED assumes suitable defaults for each of the property. You need to modify these only if you need to alter the default behavior. infrared.properties.central and infrared.properties.local are available under the setup folder in the release zip. Modify the appropriate file based on the collection strategy chosen.
Property |
Description |
Default |
net.sf.infrared.monitoring |
This boolean property controls if InfraRED should monitoring the application. If this property is set to false, no data will be visible on the InfraRED site. |
false |
net.sf.infrared.callTraceProfiling |
This boolean property controls if InfraRED should record call traces. |
false |
net.sf.infrared.jdbcMonitoringEnabled |
This boolean property controls if InfraRED should record JDBC statistics. |
false |
net.sf.infrared.collectFetchDataEnabled |
This boolean property controls if InfraRED should record JDBC Fetch statistics. Enabling this flag would track the number of rows being fetched and the time consumed by the resultset.next calls (some of which might result in a network roundtrip to the database). |
false |
net.sf.infrared.pruneBelowTime |
APIs taking lesser time that this value (in ms) would not be recorded by InfraRED. |
10 |
The following properties in infrared.web.properties can be modified. This file is part of infrared.war.
Property |
Description |
Default |
net.sf.infrared.ui.colorThreshold |
The threshold (in ms) above which "hot spots" of the application are displayed in a different color. |
100 |
net.sf.infrared.ui.
numberOfSqlQueriesToBeDisplayed
|
This property is to control the number of SQL queries that get listed on the JDBC summary page. |
10 |
net.sf.infrared.ui.
numberOfSqlQueriesToBeDisplayedInCallTracePage
|
This property is to control the number of SQL queries that get listed along with the operation trees. |
3 |
net.sf.infrared.ui.nameFieldLengthLimit |
This property is to limit the length of SQL queries & API names. Strings will be truncated to this value in the display. |
25 |
net.sf.infrared.snapShotDir |
The directory where the snapshots are saved. |
./IRSnapShots (Relative to the deployment directory of infrared.war) |
net.sf.infrared.performanceDataTransfer
.useTimer |
The performance data is collected in memory and is periodically
persisted using a timer-based task. After persisting the data, the
statistics in the memory are reset.
This boolean property controls if a timer needs to be used to persist individual API times. If this property is set to false, statistics are not persisted. |
False |
net.sf.infrared.performanceDataTransfer
.timerFrequency |
The frequency of the timer (in milliseconds) which persists individual API times. |
600000 |
net.sf.infrared.persistence |
The implementation of the PersistenceProvider Interface to be used. net.sf.infrared.web.persistence.FilePersist is the default implementation. |
net.sf.infrared.web. persistence.FilePersist |
net.sf.infrared.persistLogsDir |
The directory to which data collected by InfraRED has to be persisted for file persistence. |
./infrared-logs (Relative to the deployment directory of infrared.war) |
<<Previous | Next>> |
