Press "Enter" to skip to content

Working with Applications in vCOPS Part 1 – Using VIN

While I see allot of people use vCOPS to monitor and alert on general VMware infrastructure, I don’t see many places use it to look at applications.
Today we will be looking at one of the 2 methods for setting up applications in vCOPS and that is with the VMware Infrastructure Navigator (VIN) integration.

If you are running vCloud Advanced or enterprise suite you should be fully licensed for VIN. It has to be the most basic appliance to install so I will not be covering the install of it but what to do with it afterwards.

Today unlike most my post I will be using my brand spanking new test lab to demo this in. that way I dont need to blank out names and ip addresses.

1) After the install and if has been running for a couple of days so it has a good map of the VM dependencies you select a VM that you know to be part of an application. I will be using VMware vCAC as my “application” but it can be anything. Note This is only available through the web client.
vinapp01
Nice pretty application map, executives love this stuff!!!

2)Now hold ctrl button and click on all the VMs you want to be part of the application, they we be highlighted with dark blue if selected. (don’t worry if not all are visible we can manually add later)
Then click the create application button which I have highlighted in red below,
vinapp02

3) Enter the name and hit ok
vinapp03

4) you should now have display map of and this opens up the apility to remove/add vms and edit the name of the application.
vinapp04

5) now if you log into the vSphere ui of vCOPS you should now see Application and the new application you just created under the groups section like the below image.
vinapp05

6) Now its time to log into the vCOPS custom ui. Once logged in navigate to, environment overview -> resource kinds. You will notice there is now 2 application kinds First one is the vCOPS adapter Application which I will cover in Part 2 the second one is the VIN adapter Application. verify you can see your application in here.
vinapp06
vinapp07

Now its time to guide you through a pretty cool custom dashboard that will be used to monitor or view the application created through VIN. Att he end of this the dashboard should look like something similar to the image below.
vinapp08

1) Setup the widgets in the above image in a similar layout, obviously this is just a guide you can display or order it anyway you want. Below is the widget interactions
vinapp09

When we select the application under application over view it will change the below widgets.
vinapp10

When we choose the VM in the health tree it will change the below widgets.
vinapp11

2) for the application stats scoreboard we will need a custom xml files, The adapterkindkey for VIN is “VIN_Adapter” You will need to connect to the vCOPS UI server and navigate to /usr/lib/vmware-vcops/tomcat-enterprise/webapps/vcops-custom/WEB-INF/classes/resources/reskndmetrics using winscp and upload the new xml file. Download XML Files


vinapp13

3) For the Application VM stats we also use a custom XML file, this one is nothing fancy just standard VM metrics, Upload this to the same place as above.

vinapp12

3)You will notice I use super metrics for the Application Stats, the super metrics Im using are just converting KB to GB and MHz to GHz to make it more readable. I will not go into this here but is available on on of my other posts HERE When calling super metrics in an XML file you must use SM_id this ID will be shown on your supermetrics page in vCOPS.
Below is an image of one of my super metrics showing where to find the right metrics.
vinapp14

4) Below is the config setting for the Application overview. See how I have selected resource kind and the VIN application.
vinapp15

5)Below is the config settings for the Application Stats scoreboard, note the REs. Interaction Mode I have selected the xml file I created earlier.
vinapp16

6) Below is the Application Detail widget, This is default setting.
vinapp17

7) Below is the Application Health Tree widget, this is default also.
vinapp18

8) Applications Alerts widget, Below is the configuration for this. I have only changes the alert status to show active alerts only but you can specifiy what you would like shown.
vinapp19

9)Application VM Health widget configuration as the below image, Remember to select children as the mode.
vinapp20

10) Below is the configuration on the VM Service Health widget, again select children as the mode. This will show the services that VIN discovers on the VM.
vinapp21

11) Below is the configuration of the Application VM Stats scoreboard, see how the interaction mode is using the other custom xml file previously created
vinapp22

Thats it, This is just an example of what can be done, Obviously a custom desktop like this would be created for an application support team, The benefit of using VIN to create applications is that it will pick up the services being used too.

Cheers

5 Comments

  1. Blue Medora Staff
    Blue Medora Staff May 14, 2014

    Wow, what an incredibly detailed blog post that covers a topic I haven’t seen before —vCOPS with VMware Infrastructure Navigator integration.

    Thanks for your contribution to the vCOps community?

    • Scott Norris
      Scott Norris May 14, 2014

      Not a problem 🙂 Happy others can learn from it, Thank you very much for the comment.

  2. kris
    kris February 5, 2015

    Have you tested the updated version vRealize ops 6 ? integrating with Infrastructure navigator ?

    • Scott Norris
      Scott Norris February 5, 2015

      Hi Kris,

      Yes I have and it works pretty much the same. The only difference is that the applications that VIN detects running on the VM are no longer child objects but have been placed on the VM as properties. So this post should still hold true apart from the vm service health section.

      Under the VM when using VIN there will now be an application components running on VM property which can display the application and ports it uses.

      A nice addition is you can use the topology widget and display the VIN dependencies on which is a nice touch.

      As soon as I finish up writing a vROPS book ill start updating allot of content for vROPS 6, just not enough time 🙂

      Cheers

Leave a Reply

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

Anti SPAM BOT Question * Time limit is exhausted. Please reload CAPTCHA.