Come join our live training webinar every other Wednesday at 11am PST and hear LogicMonitor experts explain best practices and answer common questions. We understand these are uncertain times, and we are here to help!
LogicMonitor offers out-of-the-box monitoring for the VMware VeloCloud platform. Our monitoring suite uses the VeloCloud Orchestrator API and SNMP to query the VeloCloud resource for a wide variety of health and performance metrics.
As of October 2020, LogicMonitor’s VMware VeloCloud package is known to be compatible with VeloCloud Orchestrator API:
As VMware releases newer versions of VeloCloud Orchestrator API, LogicMonitor will test and extend coverage as necessary.
Add your VMware VeloCloud Orchestrator host into monitoring. The resource hostname is used to build URLs for API queries and should be formatted vcoX.velocloud.net to match the device’s respective portal in VeloCloud. For more information on adding resources into monitoring, see Adding Devices.
LogicMonitor must provide the appropriate credentials in order to successfully access the VeloCloud resource’s data. These credentials must belong to an enterprise user account in VeloCloud that has been assigned the following minimum privileges:
The following custom properties must be set on the VMware VeloCloud resource within LogicMonitor. For more information on setting properties, see Resource and Instance Properties.
From the LogicMonitor public repository, import all VMware VeloCloud LogicModules, which are listed in the LogicModules in Package section of this support article. If these LogicModules are already present, ensure you have the most recent versions.
Once the LogicModules are imported (assuming all previous setup requirements have been met), data collection will automatically commence.
DataSources in this suite assign instance-level properties that can be used for instance grouping if desired. By default, these DataSources are not set to automatically create instance level groups during Active Discovery, but the following table highlights a few common instance-level grouping options that you can implement if desired.
For more information on updating DataSource configurations for the purpose of enabling automated instance grouping, see Instance Groups.
By default, the DataSources in this suite are not set to auto delete instances so that users can maintain historical data for SLA purposes. However, if this is not your preference, you can update this Active Discovery setting to automatically remove edges and links that are no longer active, as outlined in What Is Active Discovery?.
The modules in this package are designed with a debug mode embedded in the scripts. If issues occur, turn on debug mode in the script by setting the variable debug to “true” to get more information in the output when testing the script in the Collector Debug Facility. For more information on testing scripts in the Collector Debug Facility, see Script Troubleshooting.
LogicMonitor’s package for VMware VeloCloud consists of the following LogicModules. For full coverage, please ensure that all of these LogicModules are imported into your LogicMonitor platform.
The DataSources in this package do not include predefined datapoint thresholds (that is, no alerts will trigger based on collected data). This is because the technology owner has not provided KPIs that can be reliably extended to the majority of users. If you’d like to receive alerts for collected data, you’ll need to manually create custom thresholds, as discussed in Tuning Static Thresholds for Datapoints.
In This Article