HOWTO: Monitor a Process in Linux using vRealize Operations – Endpoint Operation Management – Part 2

This is Part Two of a series on Monitoring Processes in Linux using VMware vRealize Operations Endpoint Operations Management.

Part 1 – Creating the MultiProcess Object for a single Linux Machine
Part 2 – Creating a MultiProcess Object for a Linux Machine (via Inventory Explorer)
Part 3 – Creating Object Relationships
Part 4 – Identifying the correct process.query string

Creating a MultiProcess Object for a Linux Machine (via Inventory Explorer)

Log into vRealize Operations using an appropriate account

Select Administration

Select Inventory Explorer

Click Add Object

At the Add Object dialog, complete the following:

  • Enter the Display Name (crond)
  • Select EP Ops Adapter from the Adapter Type dropdown
  • Select EP Ops Adapter < instance id> from the Adapter Instance dropdown
  • Select MultiProcess from the Object Type dropdown
  • Update the process.query field to show State.Name.eq=crond

Click OK

Once you have added all the MultiProcess object you desire, they should be displayed within the Inventory Explorer under Object Types > MultiProcesses

Now all that is left is to configure the appropriate Objects Relationships.

This will be covered in Part 3.

3 Comments

  1. Hi Christopher – I tried creating linux process monitor in inventory explorer (Version 6.6.1.8317356) as you did here, but it keeps returning with “Failure to create resource”. Is there some other requirement that I’m missing to be able to build process monitors in Inventory explorer?

    Backstory: I’ve been looking for way to monitor processes on active/active nodes where the services can move from one node to the the other, or active / passie nodes where services are only running when the node is running the service. Had no luck finding a way to code specific process monitoring on the agent, and was hoping this might work by having a bank of process monitors in the inventory manager for the service that I could then relate to both nodes.

    Thanks,

    Rabin

    1. Hi – Sorry I have been on PTO for the last 4 weeks so haven’t been monitoring the site. This article was based on a very early release of vROPs 6.1 so potentially it has changed. Let me take a look and see if i can find anything that may have changed.

      Chris

  2. Hi Christopher,
    VMWare support confirmed they tested this functionality on every release since 6.1 and it returns the same error. We’ve asked for it as a feature request as it would be very handy as you’ve shown here, but engineering confirmed it’s not a supported feature and it will not work this way now.

    If you find otherwise I’d definitely escalate your findings.

    Thanks!

    Rabin

Leave a Reply

Your email address will not be published. Required fields are marked *

This site uses Akismet to reduce spam. Learn how your comment data is processed.