Is it just me or is there no way to remove the vrops integration for vrli
↧
Re: vRLI alerts sent to vrops
↧
No data for Trends View in vROPS Report PDF Format
I am not getting the trends view data in vROPS reports. anyone who can help?
↧
↧
Re: No data for Trends View in vROPS Report PDF Format
Can you please provide much more information? There is nothing to go on here.
↧
Old Data Receiving
Hi all,
I have a Large 6.6.1 cluster. We have 5 Master/Data nodes and 4 Remote Collectors. There are 4 vCenter adapters and 1 vSAN adapter.
I switched from the MPSD to the vSAN adapter this past Monday. I have removed the old MPSD adapter and have confirmed the objects it monitored have been removed as well.
Since switching over to the vSAN adapter, I have noticed that pretty much all of the objects in that instance have a collection status of "Old Data Receiving". Some objects are collecting, some have old data. I know the "Old Data Receiving" means data is not current and it is behind by 5 polling cycles.
My questions:
- Does this status simply mean there is no new data?
- Should I be concerned with not receiving actual data to trigger the alerts?
Thanks for any and all help!
↧
Re: vRLI alerts sent to vrops
You mean unconfigure? You can't just yank those bits out of vRLI.
↧
↧
monitor windows process
I've found information on how to monitor a Windows Service, however not on how to monitor a Windows process. It appears as though it can be done with an endpoint agent, however I'd like to be able to do it natively within vROM. We are using version 6.6.
Symantec goes rouge and consumes tons of CPU time on some of our servers and we'd like to use vROM alert us to this issue.
↧
Re: monitor windows process
To be able to monitor with that granularity, you need the Endpoint Operations agent installed inside your Windows/Linux system.
↧
Re: Old Data Receiving
Dumb question but the VSAN performance service is turned on for the VSAN clusters?
From the 6.5 docs:
When you create a vSAN cluster, the performance service is disabled. Turn on vSAN performance service to monitor the performance of vSAN clusters, hosts, disks, and VMs.
About this task
When you turn on the performance service, vSAN places a Stats database object in the datastore to collect statistical data. The Stats database is a namespace object in the cluster's vSAN datastore.
Prerequisites
- All hosts in the vSAN cluster must be running ESXi 6.5 or later.
- Before you enable the vSAN performance service, make sure that the cluster is properly configured and has no unresolved health problems.
Procedure
- Navigate to the vSAN cluster in the vSphere Web Client navigator.
- Click the Configure tab.
- Under vSAN, select Health and Performance.
- Click Edit to edit the performance service settings.
- Select the Turn On vSAN performance service check box.
- Select a storage policy for the Stats database object and click OK.
↧
Re: vRLI alerts sent to vrops
yep i mean unconfigure
There is no x or a remove button anywhere
If you remove all the fields and un-tick everything and save it you get a save error but if you navigate away and back to this it has saved it and unconfigured it.
↧
↧
Canceled alerts
Is there a way to stop a canceled alert alert from being sent REST or/and Email
↧
Re: monitor windows process
Thank you for your response. I tried previously to perform this task, however I could not navigate the path in vROM 6.6, as it looked promising:
↧
Re: monitor windows process
Because that path is only present when the Endpoint Operations (EpOps) agent is installed.
↧
Re: vRLI alerts sent to vrops
I get you, no I don't think there's an unconfigure option. There might be a procedure behind the scenes to clean it out, but I haven't seen it.
↧
↧
Re: Canceled alerts
What's going on here, exactly? You have an alert that has already been canceled, yet it continues to send over the REST and email plug-in as if it were active??
↧
Re: Canceled alerts
I have created an alert. We send it to a SHIM server that formats the vrops REST payload into a format our upstream service recognises. That is then sent to an ENS system that then creates automatic tickets in ore ticketing system.
I know a bit long winded but that is the way we have to do it.
Once the ticket is closed that is the end of it. What i dont want to do is flood our SHIM or the upstream service with canceled alerts in vrops. What i would like to do if possible is not send canceled alert payloads to the SHIM at all because as long as the ticket is closed no one cares if the alert is canceled in vrops
↧
Re: vRLI alerts sent to vrops
I am just of the phone with our VMware TAM and he has given me the supported way to remove the integration. VMware being great on documentation have not made it public.
In short
- untick the enable alerts integration and launch in context
- save
- delete the hostname and user name
- tick update password
- save
I have added a feature request to add an x to the config like the vsphere integration and my TAM is talking to the product team for a stupid long process
↧
The vRealize Operations Manager correlation algorithms calculate a greater than 90% chance (above the noise threshold) that there is a problem with this Object.
I get this alert on a daily basis from vROPs Self-Monitoring Alerts that I have setup per vbulosity: VMware vROps - vROps Self-Monitoring Alerts and Notifications
Alert Definition Name: Early Warning Alert
Alert Definition Description: The vRealize Operations Manager correlation algorithms calculate a greater than 90% chance (above the noise threshold) that there is a problem with this Object.
Object Type : vC-Ops-Suite-API
Alert Impact: health
Alert State : critical
Alert Type : Application
Alert Sub-Type : Availability
Object Health State: critical
Object Risk State: info
Object Efficiency State: info
Control State: Open
Symptoms:
SYMPTOM SET - self
Symptom Name | Object Name | Object ID | Metric | Message Info |
Number of anomalies is high | vRealize Operations Manager Suite API- |
| vRealize Operations Generated|Self - Total Anomalies |
|
Recommendations:
- Examine the Object data for possible causes
Notification Rule Name: vROPs Self-Monitoring Alert Notification
Notification Rule Description:
Anyone else run into this alert or know the culprit?
vROPs Version: 6.6.0
↧
↧
Health Check Alerts for vROPs cluster
Who all has Health Check Alerts configured for their vROPs cluster?
I have a few alert notifications configured for vROPs cluster:
I used this article that I found: vbulosity: VMware vROps - vROps Self-Monitoring Alerts and Notifications
Then I setup some custom vROPs operations node alerting:
vROPs Node Down
Scope - vRealize Operations Node
Notification Trigger - One or more vrealize operations services on a node are down
vROPs Disk Space Alerts
Scope - vRealize Operations Node
Notification Trigger - Disk Space on Node is Low
What alerts have work for you? I just want to make sure we know when the cluster stops collecting, etc..
vROPs version: 6.6.0
↧
Re: Vrops Rest API and average over a time period
I haven't dug through this in depth or anything, so I don't know if an average for what you're looking for exists out of the box in vROPS. But you could create a super metric for each of the averages you want and let vROPS compute that for you as it collects. Then all you have to do is query that super metric on the datastores you're interested in. It should be fairly easy to create, and I believe you can set the period you want it to average over (i.e. past X collection cycles). The REST calls to grab metrics are pretty simple if you're just trying to grab basic vCenter objects like datastores.
↧
Re: Has anyone configured VROPS Kubernetes Adapter ?
I found that the error you got occurs when the username and password are wrong. When the version is wrong, say you're running 1.7 (only Kubernetes 1.5.2, 1.6.5, and 1.6.6) then the error says
Unable to establish a valid connection to the target system. Please check if the kubernetes version is supported.
If the URL is wrong, say https://kube-ip/api/ (it wants to append "/api/v1" to the end of the URL for you) the error will say
Unable to establish a valid connection to the target system. Error in fetching the health of Kubernetes master - https://kubeip/api/api/v1
If the IP is wrong it will say
Unable to establish a valid connection to the target system. Error trying to establish connection
If the protocol is wrong it will say
Unable to establish a valid connection to the target system. Error in fetching the health of Kubernetes master - http://kubeip/api/v1
If the protocol is not specified it will say
Unable to establish a valid connection to the target system. Unable to parse instance properties - no protocol: <kubeip>
Try going to https://<kubeip>/api and log in with the username and password you tried in the vROPS adapter to see if it has access to the API, if not then likely your problem is the credential being incorrect.
↧