Idea ID: 1765375

Sub-Processes report in OMi

Status : Already Offered
Already Offered
See status update history
over 2 years ago

Currently operations agent is collecting data related to processes running on the OS but many time we could find the many sub process are having the same process name and from the report we could not find which sub process is causing the performance as all are listed with same process name.

idea is to operations agent capture more details and in OMi report to show process with sub-process details.



  • Hello Mgoyal , 


    Can you please let me know where exactly do we make the change so that the agent can report the process details in Process Drill down in Performance perspective ?

    Can you provide the exact Path of this file where this needs to be changed ?


    Bilal Aman

  • Hi Ganesh,

    Once you enable the parameter, you will have to edit the performance dashboard and add the metric in the graph (the ootb graph does not show proc cmd attribute). Please note that process name and process command line are two different attributes. I hope it helps.

    Thanks & Regards,

    Moderator, OpsB IdeaX

  • Dear Goyal,

    We have validated the same and could find the details would be avaible at agent database only but could not be reflected in OMi Process drilldown dashboard. You may please refer the case:SD02449800 , which we have created with MF for validation.


  • Please see my comments earlier, let us know if the suggested input does not address the need.

    Thanks & Regards,

    Moderator, OpsB IdeaX

  • Hi ,

    Thanks for providing the clarification. You mentioned the use of CMD column in order to differentiate different processes with the same name. This is already possible in agent but by default this column is not collected by agent. You can modify the parm file on the agent and refer to the following paremeter :

    # The following parameter enables logging of process command line arguments
    # in the Perf Agent databases. You can enable this by setting the value to 1.
    # By default, the value for this parameter is set to 0 and the
    # logging of process commands is disabled.

    #proccmd = 1

    This will then start logging the cmd and you can then use it in the process details dashboard in PD.

    This should address your requirement. If not, please suggest what else is missing.

    Thanks & Regards,

    Moderator, OpsB IdeaX