Advanced Configuration

Use the Advanced Configuration page to control communications settings and advanced features such as event forwarding.

After you click icon System Configuration > Advanced Configuration, the following configuration categories are displayed in the Advanced Configuration page.
UI Integration
For products that integrate with the Cloud APM console, you can add or edit the URL for launching the integrated application. The fields are populated with any URLs that were set during the integration configuration procedure.
  • Log Analysis URL is used to launch IBM® Operations Analytics - Log Analysis for searching through application logs from the Application Performance Dashboard. For more information, see Searching log files.
  • Enable Subnode Events, for agents with subnodes, controls whether subnodes are shown in the Events tab. When subnode events are enabled, the node and subnode for which an event was opened are displayed. Specifically, if you want to display log file monitoring situations in the Events tab, you must ensure that Subnode events are enabled. Default: False.
  • Dashboard Refresh Rate controls the frequency of the Application Performance Dashboard automatic refresh. You can adjust the setting to any value from 1 to 60 minutes. The setting affects resource status that is displayed in the navigator and Status Overview tab. It has no affect on the Events tab entries. Default: 1 minute.
Event Manager

The Event Manager controls the forwarding of events using Simple Mail Transfer Protocol, as well as email notifications. If you enter a value for Target Email Addresses, an email will be sent for each open, close, and stop event. You can use the Event Manager fields to configure your events from Cloud APM to automatically open tickets in IBM Control Desk. For additional configuration tasks, see Integrating with Control Desk Integrating with Control Desk.

If you configure the SMTP forwarder to use SSL, you must add the SMTP Server’s signing CA certificate to the Cloud APM server keystore. Add the CA certificate to the default keystore using the JVM keytool command:
install_dir/java/jre/bin/keytool -importcert\ 
-noprompt \
-alias your_CA cert_alias \
-file path_to_your_CA_cert_file (*.cer)
 -keystore /install_dir/wlp/usr/servers/min/resources/security/key.jks \
-storepass ccmR0cKs! \
-storetype jks \
-trustcacerts

To view a sample email, see Event email.

  • Target Email Addresses specifies the email addresses that events are forwarded to. Separate each address with a comma (,), such as annette@ibm.com,jim@ibm.com,owen@ibm.com.
  • Cloud Event Management Webhook is the Webhook url that is generated in Cloud Event Management when you configure the integration between IBM Cloud Application Performance Management and Cloud Event Management. You must paste the generated Webhook url here so that events are forwarded from Cloud APM.

If you are forwarding events to an EIF (Event Integration Facility) receiver, you can customize the EIF slots such as to add an attribute to the EIF event. For more information, see Customizing an event to forward to an EIF receiver. For information about forwarding your events to the IBM Netcool/OMNIbus event manager, see Integrating with Netcool/OMNIbus.

Tracking Analytics Service
The settings that are used for the Tracking Analytics Service. The settings apply only to the Cloud APM, Advanced offering and if you are configuring transactions tracking in your environment.
  • Connection Pool Size is the number of concurrent Db2® connections that the Tracking Analytics Service holds in the connection pool for the Top N query. Increase this value if you are experiencing slow query times due to a large number of concurrent Cloud APM console users. Default: 10.
  • Pseudo Nodes enable the visualization of services that are not instrumented. Default: True.
  • Query Timeout in Seconds is the number of seconds before each "Top N" (where N is a number, as in Top 5 or Top 10) query take before timing out. The timeout value can be increased if needed for applications that have a higher workload and have larger expected query times. Default: 120 seconds.
  • DB2 Query Re-optimization Enabled should not normally need to be changed. The parameter affects the Db2 query optimizer. In some environments, turning off the optimizer might improve performance for some sets of transactions. Default: False.
Agent Subscription Facility
The Agent Subscription Facility includes the agent REST (Representative State Transfer) interface and Central Configuration Services HTTP server. The REST interface is used by agents and data collectors to send monitoring data that is persisted in the Db2 server and threshold events. The Central Configuration Services HTTP server handles requests from agents for their configuration files, such as threshold definitions. Use these parameters for configuring the communications between the Agent Subscription Facility and the Cloud APM server.
  • Missed Poll Limit (Fast Heart Beat) is the maximum number of times that a monitoring agent with a 60-second or lower heartbeat interval fails to connect before it is marked offline. Default: 30 intervals.
  • Missed Poll Limit (Slow Heart Beat) is the maximum number of times that a monitoring agent with a heartbeat interval that is greater than 60 seconds fails to connect before it is marked offline. Default: 3 intervals.
  • Transaction Time Out is the amount of time, in seconds, that the server waits for a response to a request. Default: 120 seconds.
  • Remove Offline System Delay determines the number of minutes to wait before removing the display of a managed system that is offline. In the Application Performance Dashboard, offline managed systems are indicated by the unknown status indicator. The managed system continues to display, even if you uninstall the agent, until the delay time has passed. For more information, see Viewing and removing offline agents. Default: 5760 minutes (4 days).
Thresholds Enablement
Your monitoring agents each come with a set of predefined thresholds that are enabled and started with the agent. These predefined thresholds are assigned to the default system resource group for the agent.
  • Choose action to define policy for predefined best practice thresholds controls whether the predefined thresholds for your managed resources are enabled or disabled by default. Set the field to Disable All if you do not want to run the predefined thresholds. The Disable All setting removes the assignment of the system group from all predefined thresholds. A threshold with no group assigned is distributed to no monitored systems and remains stopped until it is distributed to a resource group. If you decide later that you want to turn on the predefined thresholds, set the field to Enable All.
For more information about the predefined thresholds and custom thresholds, see Background information and Examples of disabled thresholds.