Why do e2e alarms only display 'UnknownProbe' in the alarm Probe field?
search cancel

Why do e2e alarms only display 'UnknownProbe' in the alarm Probe field?

book

Article ID: 260688

calendar_today

Updated On:

Products

DX Unified Infrastructure Management (Nimsoft / UIM) CA Unified Infrastructure Management On-Premise (Nimsoft / UIM) CA Unified Infrastructure Management SaaS (Nimsoft / UIM)

Issue/Introduction

  • Need to know why e2e_appmon alarms do not show the e2e_appmon probe name in the Probe field.
  • e2e_appmon probe alarms displays the probe field name as 'UnknownProbe' instead of 'e2e_appmon'

Environment

  • Release: 20.4
  • e2e_appmon, any version
  • e2e_appmon_dev, any version

 

Cause

Currently 'working as designed., populating the alarm with the e2e_appmon probe name is not supported by the API calls, e.g., nimAlarm or nimAlarmSimple

Resolution

In the probe field, it shows UnknownProbe because it comes from within the script using the API function which does not allow specifying the probe name.

It is simply not part of/included in the e2e_appmon API functions.

This would qualify as an enhancement request.

Please refer to the e2e_appmon API techdocs:

e2e_appmon API

Additional Information

Suggest entering an enhancement request to have nimAlarm and nimAlarmSimple API calls enhanced to set the probe name.

How to raise an enhancement request for UIM