datastore usage on disk alarm in vsphere 6

DATASTORE USAGE ON DISK ALARM IN VSPHERE 6 HOW TO

DataSources that currently support this functionality are: Currently the tag integration only works on DataSources applied to vCenter devices. This is optional and can be enabled by setting a device property named esx.tags to true. Some of the VMware DataSources are capable of pulling in vCenter tags as instance properties. The CIM provider is disabled – see this VMware knowledge base article.You may be able to obtain a hardware specific bundle either from VMware or your hardware vendor. Your hardware is not supported by ESXi for hardware monitoring.No further configuration is needed to activate hardware monitoring – if you do not see hardware monitoring within LogicMonitor, check that hardware status is available from the Virtual Infrastructure client.

Within LogicMonitor, you need to define the properties esx.user and esx.pass on the global, group or device level, matching the read only user you created in vSphere.įor LogicMonitor to provide ESXi hardware monitoring, you need to add the individual ESXi hosts to LogicMonitor – hardware status is not available by monitoring only vCenter. Configuring VMware Credentials in LogicMonitor However, it’s important to note that a key difference between ESXi host and vCenter is that vCenter credentials are formatted as (e.g. If vCenter is not integrated with AD, you will create a new read-only using a process similar to that for creating an ESXi host user (described in the previous set of steps). Your credentials for vCenter will be in the format of (e.g. Simply create a user with read-only permissions for your vCenter environment in AD and add it to the corresponding AD group. If vCenter is integrated with Active Directory (AD), you will find a group in vCenter that has a corresponding group in AD. Note: Your credentials for ESXi hosts will be in the format of username/password (e.g. For more information on how this is configured, please see VMware’s vSphere documentation. The credentials for ESXi users that have been added at the vCenter level will not be inherited down to clustered hosts.

You must repeat this process on each individual ESXi host you want to add to LogicMonitor for monitoring.

Ensure that the Propagate to Child Objects option is checked and click OK. In the Assigned Role section, select the “Read-only” role from the drop-down menu.

Select the LogicMonitor user you added.

In the Users section, click Add, and then select the LogicMonitor userid for this permission.

From the Permissions tab, add a new permission by right-clicking and clicking Add Permission.From the Users tab, create a userid for the LogicMonitor Collector by right-clicking anywhere in the users table and clicking Add.Using the vSphere Client, log in to the ESXi host that you would like to add to LogicMonitor as a host.The following set of steps walk you through the process of creating a read-only user for an ESXi host that has rights to use the VMware API. Setup Requirements Creating a Read-only User for an ESXi Host or vCenter ServerĪs highlighted in the next two sections, the process of creating a user varies depending upon whether you intend to monitor standalone ESXi hosts or a vCenter server.

DATASTORE USAGE ON DISK ALARM IN VSPHERE 6 HOW TO

In this support article, we outline how to set up ESXi host and/or vCenter server monitoring. LogicMonitor uses the VMware API to provide comprehensive monitoring of VMware vCenter or standalone ESXi hosts.

Datastore usage on disk alarm in vsphere 6