search cancel

Processes probe execute a script command arguments variables

book

Article ID: 131044

calendar_today

Updated On:

Products

DX Unified Infrastructure Management (Nimsoft / UIM)

Issue/Introduction

This article talks about passing variables from the probe in the command arguments


Is there a way to pass variables from the probe in the command arguments?

We are trying to pass the PID in the command arguments in the "Execute a Script", but it is not accepting $pid, etc. It is just passing "$pid" not the PID of the process.

 

Environment

Any process probe version

Resolution

Currently the action stab does not provide access to variables to be used on any of the lines in that section.
these are all going to static entries.

you might want to think about either:

  1. setting up each process as its own profile so the start command can be setup individually.
  2. look at parsing information out of your alarm and then using a lua script to send a start command back to nexec.

Additional Information

How to get top 5 processes and attach on Alarm message (notes)

 

 How to use the nexec probe to execute a command?

https://knowledge.broadcom.com/external/article?articleId=35012