APM Insight Configuration

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

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

• Port number of application instances will be shown, if this option is enabled.

• Alerts will be sent whenever your application goes into Down state.
• Supported only for non-cloud monitors.

• Enabling this option will suppress the alerts for all instances. 
• All alerting modes including SMS, voice, instant messenger (IM), mobile and web browser push notifications will be disabled.

•  If you enable this option, alphanumeric values in the DB operation names will be replaced with a question mark (?).

•  You can select the different levels of log message from the drop-down menu. Based on the log level selected, the log messages printed in the agent log (at the user machine) will vary.

• 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

• Enter the list of exceptions that need not be tracked.

• Provide regex patterns or transaction names that can be skipped from tracking. Multiple entries should be comma separated values.

• Provide a list of alphanumeric keywords that should not be grouped together in the transaction names.

  For example, if you configure v1, v2, index1, index2, the transactions api/v2/web3/index2.html and api/v1/web3/index1.html will be obfuscated as api/v2/*/index2.html and api/v1/*/index1.html.

• Provide a regex pattern of the transactions that can be grouped under a single transaction name.

• Provide a list of prefixes that need to be grouped under a single prefix name.
• Syntax: Transaction Prefix = New Prefix
• For example, nestle, snickers, orion = chocolate
  In the above given example, nestle/quantity/order, snickers/quantity/order, orion/quantity/order will be replaced by chocolate/quantity/order.

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

• Sampling factor helps in tracking sampled transactions.
• If set to 5, APMInsight tracks only 1 in 5 requests of the same kind

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

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

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

• When enabled, memory allocations for all web transactions will be captured.

• 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

•  Enabling this option captures the HTTP headers of the trace (which can be viewed on the Trace Details tab).

• To skip capturing specific HTTP headers, mention them.
• Use comma(,) to separate multiple entries.
• If no value is specified, all HTTP headers are captured.

Java- Accept, Cookie, Cache-Control, Connection, Host, Accept-Encoding, X-Site24x7-Id, X-SITE24X7-RUM-APPKEY, X-SITE24X7-RUM-TRACEID, Site24x7SyntheticKey

.NET, PHP, Node.js, Python- X-Site24x7-Id, X-SITE24X7-RUM-APPKEY, X-SITE24X7-RUM-TRACEID, Site24x7SyntheticKey

• This is the list of HTTP error codes, like 400, 401, and 500, that will not be tracked.

• Captures Bytes in and out in network requests, if this option is enabled.

• Enabling this option, APM Insight agent starts tracking background transactions
• All transactions other than HTTP are considered as background transactions

• Enabling this option, the agent collects traces for slow background transactions, provided bgtransaction.tracking.enabled is set to true

• Traces will be collected for background transactions whose response time have crossed the specified threshold value, provided bgtransaction.trace.enabled is set to true

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

• Record CPU time for every background transaction, if enabled.

• Memory allocated for background transactions will be captured, if this option is enabled.

• Sampling factor for background transactions
• If value is set to 1, agent tracks every transaction. If value is set to n, agent tracks 1 in n transactions of same kind

• 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 whether 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 port number in which your application is running on the server.
• Each port number ios treated as an individual instance and will be grouped under the same application name.