Hi there Manivel! First of all, I would strongly suggest you to upgrade to vROps 8.x, since it includes the Service Discovery Management Pack and it would be usefull for you. Also vROps 6.7 is end of life (https://www.vmware.com/content/dam/digitalmarketing/vmware/en/pdf/support/product-lifecycle-matrix.p...)
In my experience, using Application Monitoring (Available in vROps 7.5) was easier to use and manage than EP agent.
I think VMware explains both ways very clearly here:
Application Monitoring: https://docs.vmware.com/en/vRealize-Operations-Manager/8.2/com.vmware.vcom.config.doc/GUID-D9692377-...
[Edit] I found an excelent step-by step in youtube: https://www.youtube.com/watch?v=DLj1_aFVblY
Please tell me how it goes!
Thanks much for response.Yes.We are going to upgrade the vrops to 8.x
I will confirm once the upgrade & testing is over.
Is there any option available to notify(service down) through E-mail ? For example Tomcat service is down.
Any ideas?
Thanks,
Manivel RR
Hi again! It's very simple!
First you need to create a Symptom, where you define the triggers and criticality.
Then, create an alert that will activate when the symptom conditions are triggered.
Activate symptoms and alerts in the policy
Then create a notification rule, where you can choose how you will be notified. (You may need to set up a SMTP server in Administration -> Settings -> Outbound settings)
Create symptoms and alerts: https://vnuggets.com/2018/08/28/vrealize-operations-6-7-symptoms-alerts/
Create notification rule:
https://support.bluemedora.com/s/article/vROps-E-mail-notification-for-all-Notification-Events
https://masteringvmware.com/how-to-create-email-alert-notification-in-vrealize-operations-manager/
Great.Thanks much.
I will check and let you know in another couple of days.
Thank you,
Manivel RR