| Configuration |
Description |
Default Value |
| application.name |
- Specify the desired Application's Name to show in Site24x7.
- If there are multiple instances of your application and you would like to group them, then specify the same application name in all installed APM Insight Agent Configuration files.
Example: myonlineshopping.com
|
|
| license.key |
- The API Key for the corresponding user
- This will be available in the APM Insight home page, after login.
- Copy and Paste the Key as value for this parameter.
- This key is user specific. Do not share with anyone else.
|
|
| behind.proxy |
- Specify weather the Agent installed Application Server is under a proxy network.
- If set True, Proxy credential information should be given in order to send the metric data from the agent to Site24x7.
- If behind.proxy is set to true, specify values for the following keys:
proxy.server.host: Host name of the proxy server
proxy.server.port: Proxy server's port
proxy.auth.username: User name of the proxy server
proxy.auth.password: password for the proxy server
|
Default value: false |
| agent.server.port |
- Specify the HTTP listening port of the Application Server.
- It will be useful to distinguish Instances when more than one Application Server runs in same host.
Example: 8080
|
|
| apdex.threshold |
- Application Performance Index (simply called Apdex) is measurement of an Application's Performance ranging from 0 to 1.
- Detailed information about Apdex can be found at www.apdex.org
- If any transaction response time scores values below the apdex.threshold value, the transaction is labeled as Satisfied.
- If any transaction response time scores above four times the apdex.threshold, the transaction is labeled as Frustrated.
- If it is exactly equal to apdex.threshold or in between satisfied and frustrated threshold value it is labeled as Tolerating.
|
Default value: 0.5 (Second) |
| sql.capture.enabled |
- Enabling this option will listen to all SQL Queries which gets executed.
- If this option is disabled, no Database Metrics will be collected.
|
Default value: true
|
| transaction.trace.enabled |
- Enabling this option will construct Trace for Slow Transactions.
- You can view the traces collected in Site24x7 APM Insight Edition Page by selecting Traces tab.
|
Default value: true |
| transaction.trace.threshold |
- Trace of any transaction whose response time scoring above the specified threshold value will be collected, provided if transaction.trace.enabled is set to true.
- The trace can be used to analyze, troubleshoot the transaction working.
|
Default value: 2 (Seconds) |
| transaction.trace.sql.parametrize |
- Enabling this option will parametrize all SQL Queries in Slow Transaction Traces. (if sql.capture.enabled set to true & transaction.trace.enabled set to true)
- Disabling this option will give you the real query (with parameters).
- It is recommended to enable this option if there are queries getting executed using confidential parameters like credit card number, passwords, etc.
|
Default value: true |
| transaction.trace.sql.stacktrace.threshold |
- Enabling this option will collect the stacktrace whenever any sql query executed above this threshold time value.
|
Default value: 3 (Second) |
| webtransaction.trace.input.params.record |
- Enabling this option captures parameters of all GET & POST web requests
- To skip capturing specific parameters use webtransaction.trace.input.params.ignore key
- Captured parameters can be viewed by selecting the required transaction in Traces tab
|
Default value: false |
| webtransaction.trace.input.params.ignore |
- To skip capturing specific web request parameters like password, PIN or any confidential values, specify those parameter names for this key
- Use comma(,) to separate multiple entries. Values specified for this key are case-sensitive
- If no value is specified, all request parameters will be recorded
|
Default value: password, authKey |
| transaction.skip.listening |
- Web transactions of the specified URL patterns will be skipped while tracking
- Use comma(,) to separate multiple entries
Example: transaction.skip.listening=*.jpeg, will skip listening to transactions ending with .jpeg
|
Default value: *.css, *.js, *.gif, *.jpg, *.jpeg, *.bmp, *.png |
| transaction.tracking.request.interval |
- A kind of sampling. If said 20, APM Insight will only track request after every 20 requests of same kind. i.e it will track 1st, 21st, 41st.. request of its kind.
- The request count maintained will be reset after every one minute.
|
Default value: 1 (request) |
| include.components |
- By default, APM Insight groups transaction into different components like STRUTS, SERVLET, MYSQL, etc.
- Custom components can be added by specifying the package name in below mentioned format : packagename/.*:Component_Name
- All packages and classes under the specified package will be grouped into specified component.
- For Ex: include.components=com/test/custom/.*:CUSTOM, all packages and classes under the package com/test/custom/ will be grouped into CUSTOM component.
- Use comma(,) to separate multiple entries.
- The package name will default be included for instrumentation and you need NOT give this in include.package separately.
|
|
| apminsight.log.dir |
- Directory path where the APM Insight log should be stored.
- Use forward slash(/) as path separator
Example: D:/Tomcat/apminsight
- Defaults to the directory where APM Insight agent is installed if commented or mentioned incorrectly or unable to create the configured directory.
|
|
| apminsight.log.level |
- The log level at which the APM Insight agent should record information.
- Supported levels are SEVERE,WARNING, INFO and FINE.
|
Default value: INFO (level) |
