jdbc_response probe appends "_r" suffix to suppression key for some alarms

Products

• DX Unified Infrastructure Management (Nimsoft / UIM)

Issue/Introduction

When the"useRobotAsSource" parameter is enabled in a jdbc_response probe profile, an unintended "_r"  suffix is appended to the end of the suppression key (SuppKey) for response time alarms. This behavior prevents proper alarm suppression and results in duplicate alarms for the same monitoring profile

 

Environment

*   Probe: jdbc_response 2.0.0 and prior
*   Parameter:  useRobotAsSource = yes
*   Product: DX Unified Infrastructure Management (Nimsoft / UIM)

Cause

This issue has been identified as a defect in the jdbc_response probe's suppression key formatting logic, where enabling the robot as the source incorrectly alters the suppression string.

Defect ID: DE666221

Resolution

This issue is currently under Engineering review. 

While waiting for a fixed probe version, you can utilize a nas pre-processor script to modify the suppression key before the alarm is published. This script could be configured to detect and strip the trailing "_r" suffix from incoming `jdbc_response` alarms.

For detailed steps on configuring a `nas` pre-processor rule, refer to: How to change suppression key through NAS auto operator/pre-processor