Idea Details

Clustered Node Display Name

Last activity 06-03-2019 08:42 PM
Matthew Spiewak's profile image
06-24-2015 10:43 AM

Our PAM environment consists of one domain orchestrator and a clustered node to that domain orchestrator.  When a process starts it will run on either the domain orchestraor (node1) or the clustered node (node2).  However, no matter which node the process actually runs on, all the operators in it's dataset for AgentName list the domain orchestrator server name.  This makes it very difficult to troubleshoot when issues arise as we cannot tell which one of our servers the process actually ran on.



I would like for the operator dataset to display the actual server name that it ran on rather than obscuring everything under the name of the domain orchestrator.


02-11-2019 01:42 PM



In our Environment we have a custom operator that we created that runs at the start of every (parent) process.  It checks all the nodes that are available in CAPA, and the first one that returns that it is available is returned as the ActiveNode. 


Once we set the ActiveNode variable, all the scripts/operators in that process are set with their Execution Target set to the Process.ActiveNode variable. This way the entire process then runs on the same node, and if there is an issue it is much easier to troubleshoot.


Also, if we have steps that create temp files, or access files that were created in a previous step, we don't have to worry about making sure they are running on the same node, as they will always be by default.


Hope this helps!



06-25-2015 08:12 AM

We currently do to put in a runscript operator with the command "hostname" to help us troubleshoot and find out which node a process actually runs on.  However, that is is pain to have to add to every process, the operator should just display the acutal node name.  The value displayed for AgentName is not even the loadbalancer name it is server name of the domain orchestrator.  It is misleading to show that server name when the process may be running on other servers.

06-25-2015 03:24 AM

Ideally, we want end user to know about the loadbalancer rather than individual node information on which the process ran. However, you could implement it as part of your use case by means of RunProgram/RunScript operator with command "hostname" and check the option to enable the output to a dataset variable.