Our vBulletin migration is complete.
Welcome vBulletin users! All content and user information from the Micro Focus Forums (vBulletin) site has been migrated to this site. READ MORE.

Sub-Processes report in OMi

Sub-Processes report in OMi

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.

6 Comments
Micro Focus Expert
Micro Focus Expert
Status changed to: New Idea

Hi,

I'm not quite clear which report are you referring to? OMi itself has no reports. Could you please share more details for better understanding?

Thanks & Regards,

Moderator, OpsB IdeaX

Contributor.. ganesh2 Contributor..
Contributor..

Dear,

In OMi, we have performance perspective OOTB dashboard. Under which we have "Process Drilldown" report as part of "Standard Dashboard". In the Process Drilldown report , details about all the processes along with its usage details are available. What we sugegsted is, since in many Middleware softwares are based on Java. All processes are listed as Java and from the report it is not possible to under stand which process actually is causing the issue. unless we have the processid but that would be not avaible for the historic data , if the process is restarted.

So we are suggesting to provide more details that the java process invokes, the details that  were availble at the OS level. i.e., if we execute the command, ps-ef, all processes with details are listed. the same details i.e., CMD column values would be helpful and very useful for analysis.

Micro Focus Expert
Micro Focus Expert

Hi @ganesh2 ,

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

Micro Focus Expert
Micro Focus Expert
Status changed to: Already Offered

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

Thanks & Regards,

Moderator, OpsB IdeaX

Contributor.. ganesh2 Contributor..
Contributor..

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.

Regards 

Micro Focus Expert
Micro Focus Expert

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

The opinions expressed above are the personal opinions of the authors, not of Micro Focus. By using this site, you accept the Terms of Use and Rules of Participation. Certain versions of content ("Material") accessible here may contain branding from Hewlett-Packard Company (now HP Inc.) and Hewlett Packard Enterprise Company. As of September 1, 2017, the Material is now offered by Micro Focus, a separately owned and operated company. Any reference to the HP and Hewlett Packard Enterprise/HPE marks is historical in nature, and the HP and Hewlett Packard Enterprise/HPE marks are the property of their respective owners.