APM Insight Configuration

• 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

• 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.

• 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

• 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

• 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.

• Enabling this option will listen to all SQL Queries which gets executed.
• If this option is disabled, no Database Metrics will be collected.

True

• 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.

• 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.

• 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.

• Enabling this option will collect the stacktrace whenever any sql query executed above this threshold time value.

• 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

• 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

• 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

• 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.

• Charset encoding to use while capturing HTTP request input parameters, if enabled

• Record CPU time for every HTTP request, if enabled.

• Trace snapshot will be taken for all HTTP request(s) which has total external components (like MYSQL, MEMCACHED, etc) call count equal or higher than the configured number.

• Time interval for the agent to collect the JVM related data like Memory Usage, Cpu Usage, etc.
• For example, if value is set to 3, agent will collect data for every 3 minutes.

• On setting this value to true, agent will be upgraded automatically to the latest available version.

• Directory path where the APM Insight log should be stored.
• Use forward slash(/) as path separator
  Example: D:/apminsight
• Defaults to the directory where APM Insight agent is installed if commented or mentioned incorrectly or unable to create the configured directory.

• The log level at which the APM Insight agent should record information.
• Supported levels are SEVERE,WARNING, INFO and FINE.