Answer:

The Actions will be removed once the Netprobe containing the alerts goes down or disconnects.

Verification:

User may check the gateway log for related messages.

• Scenario 1:

Entries:

<Mon May 27 10:45:08>  INFO: CommandManager Executing command '/PLUGIN:sampleNow' on DataItem '/geneos/gateway[(@name="current_production")]/directory/probe[(@name="probe_rhel_generic")]/managedEntity[(@name="rhel_generic")]/sampler[(@name="rhel_fkm_memleak")][(@type="")]/dataview[(@name="rhel_fkm_memleak")]', issued by user 'ActiveConsole2' on '192.168.100.140'
<Mon May 27 10:45:09>  INFO: ActionManager Action DataItem 'Email' generated (variable=/geneos/gateway[(@name="current_production")]/directory/probe[(@name="probe_rhel_generic")]/managedEntity[(@name="rhel_generic")]/sampler[(@name="rhel_fkm_memleak")][(@type="")]/dataview[(@name="rhel_fkm_memleak")]/rows/row[(@name="/home/gelo/ticket30341/Europe_01.txt")]/cell[(@column="status")])
<Mon May 27 10:45:09>  INFO: ActionManager Firing action 'Email'

Results:

Action fired and severity applied

• Scenario 2:

Entries:

<Mon May 27 10:46:09>  INFO: ProbeManager Netprobe probe_rhel_generic (192.168.100.82:6370) Down
<Mon May 27 10:46:09>  INFO: ProbeManager Releasing licence for probe_rhel_generic (192.168.100.82:6370)
<Mon May 27 10:46:09>  INFO: ProbeManager Releasing sampler licences for probe_rhel_generic (192.168.100.82:6370)

Results:
Netprobe went down

• Scenario 3:

Entries:

<Mon May 27 10:46:09>  INFO: ActionManager Action DataItem 'Email' removed (variable=/geneos/gateway[(@name="current_production")]/directory/probe[(@name="probe_rhel_generic")]/managedEntity[(@name="rhel_generic")]/sampler[(@name="rhel_fkm_memleak")][(@type="")]/dataview[(@name="rhel_fkm_memleak")]/rows/row[(@name="/home/gelo/ticket30341/Europe_01.txt")]/cell[(@column="status")])

Results:

Action removed

Related articles:

• Gateway Rules, Actions and Alerts (link to documentation)

If you need further help:

• Please contact our support team via the chat service box on any of our websites or raise a support request.
  
• Make sure you provide us with:
  • Background of the issue or request.
  • Use cases, requirements, business impact, etc.
  • Encountered error messages.
  • Log files or diagnostic files.
  • Screenshots.
  • And other important information relevant to your inquiry.