Monitoring IBM InfoSphere CDC

After you install the Instana host agent, the IBM InfoSphere CDC sensor is automatically installed. You can view metrics that are related to IBM InfoSphere CDC sensor in the Instana UI after you configure IBM InfoSphere CDC sensor as outlined in the Configuring IBM InfoSphere CDC section.

Supported IBM InfoSphere CDC version

Instana now supports metrics and configuration data for IBM InfoSphere CDC 11.4.

Configuring IBM InfoSphere CDC

The Instana agent uses the following configuration to connect to the IBM InfoSphere Access server. You can update the configuration in the <agent_install_dir>/etc/instana/configuration.yaml agent configuration file:

#IBMInfoSphereCDC
com.instana.plugin.ibminfospherecdc:
  remote: # multiple configurations supported
    - host: '' # hostname or IP of IBM InfoSphere CDC
      port: '' # port number to connect to IBM InfoSphere CDC
      user: '' # username to access the IBM InfoSphere CDC
      password: '' # password to access the IBM InfoSphere CDC
      poll_rate: 30 # default poll rate in seconds is 30
      availabilityZone: "" #Availabilty Zone

Viewing metrics

To view the metrics, do the following steps:

  1. From the navigation menu in the Instana UI, select Infrastructure.

  2. On the Infrastructure map, select your IBM InfoSphere CDC, and click the IBM InfoSphere CDC node slice.

  3. To display the InfoSphere CDC node dashboard, click Open Dashboard.

    The dashboard includes all the metrics that you selected for the InfoSphere CDC.

    You can click any subscription in the Subscription table to view the subscription-related metrics.

Performance metrics

You can view the following metrics for the IBM InfoSphere CDC.

Source engine metrics

The source engine metrics group helps to analyze replication activities that are specific to the source engine.

The following metrics are provided in each entry of this metric group:

Metric Description Granularity
Source pre-filter inserts The number of inserts processed for all in-scope tables by the source engine 30 seconds
Source pre-filter updates The number of updates that are processed for all the in-scope tables by the source engine 30 seconds
Source pre-filter deletes The number of deletes that are processed for all the in-scope tables by the source engine 30 seconds
Source post-filter inserts The number of inserts that are sent to the target after the filtering of rows 30 seconds
Source post-filter updates The number of updates that are sent to the target after the filtering of rows 30 seconds
Source post-filter deletes The number of deletes that are sent to the target after the filtering of rows 30 seconds
Rows evaluating derived columns The number of rows with at least one derived expression 30 seconds
Rows calling source database The number of rows with at least one call out to the source database 30 seconds
Rows calling user exits The number of rows with call out to user functionality 30 seconds
Source latency - seconds The latency of source engine in seconds 30 seconds
Source MBCS conversions - bytes The number of input bytes that are converted by character conversion in source engine 30 seconds
Source Thread CPU - milliseconds per second The number of threads that a CPU uses for source engine 30 seconds

Target metrics

The target metrics group helps to analyze replication activities that are specific to the target engine and the target database.

The following metrics are provided in each entry of this metric group:

Metric Description Granularity
Target "source" inserts The number of record operations that are received from the source as inserts 30 seconds
Target "source" updates The number of record operations that are received from the source as updates 30 seconds
Target "source" deletes The number of record operations that are received from the source as deletes 30 seconds
Target apply inserts The number of inserts that are attempted in the database 30 seconds
Target apply updates The number of updates that are attempted in the database 30 seconds
Target apply deletes The number of deletes that are attempted in the database 30 seconds
Target apply Thread CPU - milliseconds per second The number of threads that a CPU uses to replicate activities that are specific to the target database 30 seconds
Target engine Thread CPU - milliseconds per second The number of threads that a CPU uses for target engine 30 seconds
Rows calling target database The number of rows with at least one call out to the target database 30 seconds
Rows evaluating expressions The CPU time spent that is in evaluating expressions 30 seconds
Rows calling user exits The number of rows with call out to user functionality 30 seconds
Target apply latency - seconds The latency of target engine in seconds 30 seconds
Target MBCS conversions - bytes The number of input bytes that are converted by character conversion in target engine 30 seconds

Communications metrics

The communications metrics group helps to analyze variances in the flow of data during replication activities for both source and target engines.

The following metrics are provided in each entry of this metric group:

Metric Description Granularity
Source network latency - millisecond The roundtrip time for processing between the source engine and the target engine 30 seconds
Source communications bytes processed The number of bytes that are sent on the network from the source engine 30 seconds
Source missing round trip response The number of times the replication engine failed to receive a response within 30 seconds 30 seconds
Target network latency - millisecond The roundtrip time for processing between the target engine and the source engine 30 seconds
Target communications bytes processed The number of bytes received from the network from the target engine 30 seconds
Target missing round trip response The number of times the replication engine missed receiving a reply within 30 seconds 30 seconds
Keep alive sent The number of alive messages that are sent as a test of the network connection when there is no current replication activity 30 seconds
Keep alive received The number of alive messages that are received as a test of the network connection when there is no current replication activity 30 seconds
Bytes sent The number of bytes that are sent for a subscription 30 seconds
Bytes received The number of bytes that are received for a subscription 30 seconds

Log metrics

The log metrics group helps to analyze replication activities that are specific to the Log Parser and Log Reader.

The following metrics are provided in each entry of this metric group:

Log Metrics Description Granularity
Log Parser Disk reads - bytes The physical bytes that are read from the disk 30 seconds
Log Parser Disk writes - bytes The physical bytes that are written to the disk 30 seconds
Log Parser Disk size - bytes The current staging store size on the disk 30 seconds
Log Parser Thread CPU - milliseconds per second The number of threads that a CPU uses for log parser 30 seconds
Log Reader Thread CPU - milliseconds per second The number of threads that a CPU uses for log reader 30 seconds
Log Reader Source database bytes processed The number of all log data bytes that are processed by the log reader for the current subscription 30 seconds
Log Reader Physical bytes read The physical bytes that are read by the log reader 30 seconds

Troubleshooting

You might encounter the following issues while you set up the IBM InfoSphere CDC sensor:

User already connected to datastore

The following exception in the log indicates that the user is trying to connect to a datastore that is already connected by the same user.

Could not connect to the datastore. The datastore may be unavailable or your credentials may be invalid.

User <user> is already connected to datastore <datastore>.

To resolve this issue, the user must log out from the management console.