"DB2 on Windows" pattern not updating the Name field of DB2 Instance CI


Description

When running Discovery on a server that hosts DB2 Instance, the Name field of the instance (cmdb_ci_db2_instance) is not updated or modified. Even though the discovery run completed without issue.

Release or Environment

Any

Cause

Below is the logic used during DB2 instance discovery.

  1. IP Based Discovery (Horizontal) is scheduled to run against the server/host that hosts DB2 Instance.
  2. Name modification is commonly done via the Extension Section of DB2 on Windows Pattern. This is done to override the default naming of DB2@hostname, which is confusing if you have multiple DB2 instances running on the same host.
  3. The host along with DB2 Instance CIs seem to update successfully by the discovery, run from point #1 above.
  4. However, when checking DB2 Instance CI, the "Name" field is not updated with the customised name format.

During the IRE processing, DB2 instance uses 'DB2 Instance rule by ServiceWatch' reconciliation rule.  This rule will block update on the DB2 Instance CI if the source is not ServiceWatch.

Resolution

This is expected behavior

It is also mentioned in the documentation that DB2 Instance should be only discovered using Service Mapping (Top Down).

Some customers might only have Discovery plugin installed in their environment. Out of the box, DB2 on Windows Pattern is not triggered when running Horizontal Discovery.

If the customer want to use this pattern for Horizontal Discovery, Reconciliation rule 'DB2 Instance rule by ServiceWatch' needs to be disabled.