Alarm not created when triggering sql_response run_profile callback

Products

• DX Unified Infrastructure Management (Nimsoft / UIM)

Issue/Introduction

When triggering the run_profile callback via the UIM API or Probe Utility (pu.exe), the sql_response probe may return a successful response (200), but a persistent alarm is not created in the Infrastructure Manager (IM) or Operator Console (OC).

Symptoms

• Executing the run_profile callback results in the alarm being cleared immediately after the test run.
• Alarms only persist when the profile runs on its configured interval (e.g., every 5 minutes).
• Manual runs via the probe GUI 'Run Now' button show the alarm in the test output but do not send it to the Alarm Server (nas).

 

Requirement

Is there any way to set to achieve that the sql_response probe would send an alarm for a specific profile on trigger? Eg. Generate alarms on demand (scheduled alarms on specific calendar days) executed by an API or script that executes the command  run_profile ?

Environment

• DX UIM 23.4.*
• sql_response probe 2.02 and higher

Cause

The run_profile callback and the 'Run Now' tool in the sql_response probe are designed for testing purposes only. They validate the query and threshold logic within the probe but are not intended to trigger a real, persistent alarm or profile execution on demand. This is current probe design.

Resolution

Since the run_profileis intended for testing only and not for generating alarm, To achieve scheduled alarms on specific calendar days (For example, as the 1st of every month), the following NAS Auto-Operator workaround can be used: 

1. Configure the sql_response profile with a daily schedule to ensure it runs every day.
2. Create an Exclude Pre-processing rule or a Close Auto-Operator profile in the nas probe to suppress this specific alarm daily.
3. Navigate to nas > Auto-Operator > Scheduler.
4. Create a new schedule with Mode: By Calendar.
5. Add the 1st day of each month to the calendar.
6. Set the action to Deactivate Profile (the exclusion/close profile) on those specific days.
7. Create a corresponding schedule to Activate Profile after the alarm period to resume suppression for the rest of the month.

This configuration ensures the alarm is only visible on the 1st of the month when the suppression rule is inactive.

Additional Information

sql_response (SQL Response Monitoring) Release Notes