VeeamONE alert email and VCenter alert email comparison ?

[albertwt]

Hi All VeeamONE experts and users,

It’s been a long time since I get exposed to Veeam product where I used to implement and manage the backup and recovery product since the early days in 2009.

Now I get confused myself after implementing the Veeam ONE email alerting for VMware. It seems that the email alert based on the specific metric is somehow overlapped between the VCenter generated alarm and Veeam ONE email alert.

Can anyone here please clarify which email alert that should be used in VeeamONE and which one that supposed to be kept on VCenter ?

[albertwt]

Hi,

Can anyone here please shed some light of what is the difference between Veeam VM alert and the builtin VCenter alarm alert ?
I'm quite confused as to which one I should enable and which one to be disabled to avoid confusion.

Thanks

[Shestakov]

Hi Albert,
You are correct there are some overlap, some of our clients combine them, but I believe that all needed alarms can be found in Veeam One Alarm Management.
Veeam One contains 150+ predefined alarms for monitoring VMware vSphere environments and vCloud Director operations framework, 14 Veeam B&R alarms, 12 internal alarms all can be customized for your particular needs. Also you can add your own alarms. Thank you.

[albertwt]

Hi Albert,
You are correct there are some overlap, some of our clients combine them, but I believe that all needed alarms can be found in Veeam One Alarm Management.
Veeam One contains 150+ predefined alarms for monitoring VMware vSphere environments and vCloud Director operations framework, 14 Veeam B&R alarms, 12 internal alarms all can be customized for your particular needs. Also you can add your own alarms. Thank you.

Ah I see,

So in this case the VCenter and VeeamONE alarm, do they complement each other or VeeamONE superceded the default VCenter alarm ?

[Shestakov]

In this case Veeam One supersedes vCenter`s alarms.
To be correct, Veeam One includes all vCenter`s alarms plus some additional ones. Although we don`t exactly copy alarms from vCenter, Veeam One alarms do pretty same job.
So, for your infrastructure monitoring you can rely just on Veeam One.

[albertwt]

Cool, thanks for the clarification.

In this case I can safely turn off the VCenter alarm and use the VeeamONE alerting.

[albertwt]

Vitaly,

Where can I get the list from Veeam website of which Alarm that is available in Veeam as opposed to the default VCenter alarm ?

[albertwt]

In this case Veeam One supersedes vCenter`s alarms.
To be correct, Veeam One includes all vCenter`s alarms plus some additional ones. Although we don`t exactly copy alarms from vCenter, Veeam One alarms do pretty same job.
So, for your infrastructure monitoring you can rely just on Veeam One.

Hi Shestakov,

I did export all of theVCenter alarm into excel spreadsheet and from my VCenter 5.1 Update 1, it shows total of 144 alarms that VMware VCenter can supports out of the box.
while for the VeeamONE, exporting the alarm into the .XML format and then counting on the </Alarm> attributes, only gives 149 total so I assume that Veeam ONE only give 5 additional alarm that VCenter can do.

can you please let me know or share the link or documentation of the total number of VeeamONE alarm can supports ?

FYI: here's the alarm that VCenter can supports

Code: Select all

Alarm that monitors a Storage DRS recommendation
Alarm that monitors when a datastore cluster is out of space
Cannot connect to storage
Cannot find vSphere HA master agent
Datastore capability alarm
Datastore cluster has datastores that belong to different SRM Consistency Groups.
Datastore cluster is out of space
Datastore in a datastore cluster is visible in more than one datacenter
Datastore is in multiple datacenters
Datastore usage on disk
Default alarm for incorrectly configured VMKernel NIC
Default alarm that is triggered when virtual machine Consolidation Needed status is set
Default alarm that triggers if a pre-4.1 host is connected to a SIOC-enabled datastore
Default alarm that triggers if an unmanaged I/O workload is detected on a SIOC-enabled datastore
Default alarm that triggers when the capability status changes for volume(s) backing the datastore.
Default alarm that triggers when the thin provisioning threshold on the storage array is exceeded for volume(s) backing the datastore.
Default alarm to alert when there are insufficient cluster resources for vSphere HA to guarantee failover
Default alarm to alert when vCenter Server has been unable to connect to a vSphere HA master agent for a prolonged period
Default alarm to alert when vSphere HA failed to failover a virtual machine
Default alarm to alert when vSphere HA failed to reset a virtual machine
Default alarm to alert when vSphere HA is in the process of failing over virtual machines
Default alarm to alert when vSphere HA reset a virtual machine
Default alarm to monitor batteries.  See the host's Hardware Status Tab for more details.
Default alarm to monitor changes in overall health status. See vCenter Service Status on the Home view for more details.
Default Alarm to monitor changes in the Fault Tolerance Secondary vLockStep interval
Default alarm to monitor changes in the Fault Tolerance state of a virtual machine
Default alarm to monitor changes in vSphere Distributed Switch MTU matched status.
Default alarm to monitor changes in vSphere Distributed Switch MTU supported status.
Default alarm to monitor changes in vSphere Distributed Switch teaming matched status.
Default alarm to monitor changes in vSphere Distributed Switch vlan trunked status.
Default alarm to monitor changes to service and extension health status
Default alarm to monitor datastore disk usage
Default alarm to monitor fans.  See the host's Hardware Status Tab for more details.
Default alarm to monitor health of a host as reported by vSphere HA
Default alarm to monitor host connection and power state
Default alarm to monitor host connection failure
Default alarm to monitor host connectivity to storage device
Default alarm to monitor host CPU usage
Default alarm to monitor host error and warning events
Default alarm to monitor host memory usage
Default alarm to monitor host service console memory swap rates
Default alarm to monitor if a host cannot exit standby mode
Default alarm to monitor if a license capacity is exceeded
Default alarm to monitor if a user-defined license threshold is exceeded
Default alarm to monitor if a virtual machine cannot migrate, relocate, or is orphaned
Default alarm to monitor if host license edition is not allowed.
Default alarm to monitor if license inventory is not compliant
Default alarm to monitor if no compatible hosts are available to place Secondary VM
Default alarm to monitor license errors
Default alarm to monitor loss of network uplink redundancy on a virtual switch
Default alarm to monitor memory.  See the host's Hardware Status Tab for more details.
Default alarm to monitor network connectivity on a virtual switch
Default alarm to monitor network uplink redundancy degradation on a virtual switch
Default alarm to monitor objects.  See the host's Hardware Status Tab for more details.
Default alarm to monitor power.  See the host's Hardware Status Tab for more details.
Default alarm to monitor powered on virtual machines
Default alarm to monitor processors.  See the host's Hardware Status Tab for more details.
Default alarm to monitor restarted virtual machines
Default alarm to monitor storage.  See the host's Hardware Status Tab for more details.
Default alarm to monitor system boards.  See the host's Hardware Status Tab for more details.
Default alarm to monitor temperature.  See the host's Hardware Status Tab for more details.
Default alarm to monitor time-outs when starting a Secondary VM
Default alarm to monitor virtual machine cpu usage
Default alarm to monitor virtual machine error and warning events
Default alarm to monitor virtual machine memory usage
Default alarm to monitor virtual machine total disk latency
Default alarm to monitor voltage.  See the host's Hardware Status Tab for more details.
Exit standby error
Health status changed alarm
Health status monitoring
Host Baseboard Management Controller status
Host battery status
Host connection and power state
Host connection failure
Host cpu usage
Host error
Host hardware fan status
Host hardware power status
Host hardware system board status
Host hardware temperature status
Host hardware voltage
Host IPMI System Event Log status
Host memory status
Host memory usage
Host processor status
Host service console swap rates
Host storage connectivity status
Host storage status
Insufficient vSphere HA failover resources
License capacity monitoring
License error
License inventory monitoring
License user threshold monitoring
Migration error
Monitors storage connectivity
Monitors the fullness of the IPMI System Event Log.  See the host's Hardware Status Tab for more details.
Monitors the status of the Baseboard Management Controller. See the host's Hardware Status Tab for more details.
Network connectivity lost
Network uplink redundancy degraded
Network uplink redundancy lost
NIC not configured correctly
No compatible host for Secondary VM
Pre-4.1 host connected to SIOC-enabled datastore
SRM Consistency Group Violation
Status of other host hardware objects
Storage DRS is not supported on Host.
Storage DRS recommendation
The alarm that monitors and alerts when Storage DRS is not supported on a host.
The host license edition is not compatible with the vCenter Server license edition.
The VCenter Alarm for VM snapshot size reminder
Thin-provisioned volume capacity threshold exceeded.
Timed out starting Secondary VM
Unmanaged workload detected on SIOC-enabled datastore
Virtual machine Consolidation Needed status
Virtual Machine CPU Ready
Virtual machine cpu usage
Virtual machine error
Virtual machine Fault Tolerance state changed
Virtual Machine Fault Tolerance vLockStep interval Status Changed
Virtual machine memory usage
Virtual Machine OS Restarted
Virtual Machine Powered On
Virtual Machine snapshot size
Virtual machine total disk latency
VKernel Host CPU Utilization
'VKernel Host CPU Utilization' above 95% for 5 minutes. 
VKernel Host Memory Utilization
'VKernel Host Memory Utilization' above 95% for 5 minutes. 
'VKernel VM CPU Ready' above 3000 ms for 5 minutes. 
VKernel VM CPU Utilization
'VKernel VM CPU Utilization' above 95% for 5 minutes. 
VKernel VM Disk Latency
'VKernel VM Disk Latency' above 50 ms for 5 minutes. 
VKernel VM Memory Utilization
'VKernel VM Memory Utilization' above 95% for 5 minutes. 
vSphere Distributed Switch MTU matched status
vSphere Distributed Switch MTU supported status
vSphere Distributed Switch teaming matched status
vSphere Distributed Switch vlan trunked status
vSphere HA failover in progress
vSphere HA host status
vSphere HA virtual machine failover failed
vSphere HA virtual machine monitoring action
vSphere HA virtual machine monitoring error

[Shestakov]

Albert,
Here is a link to the information about Veeam ONE Monitor alarms and rules.
And here is a link about alarms configuration.
Aslo you can easily find and review any alarm in Veeam One Monitor>Alarm Management using navigation pane or search tool.
What particular alarms are you interested in?

[albertwt]

Albert,
Here is the link to the information about Veeam ONE Monitor alarms and rules.
And here is the link about alarms configuration.
Aslo you can easily find and review any alarm in Veeam One Monitor>Alarm Management using navigation pane or search tool.
What particular alarms are you interested in?

Shestakov,

I'm trying to compare side by side between Veeam ONE and the VCenter alarm so that I can show to the management that we are using the most complete alarm system and no missing items unmonitored.

[Shestakov]

I see your point, Albert.
The thing is, some alarms in fact have a bit different names although do same job. Reviewing them one by one can take a while, but Veeam One contains all vCenter alarm capabilities.
Or, to be over-cautious, you can enable both Veeam One and vCenter alarms for the first time, make sure they double each other and leave just Veeam One.
Thanks.

[albertwt]

I see your point, Albert.
The thing is, some alarms in fact have a bit different names although do same job. Reviewing them one by one can take a while, but Veeam One contains all vCenter alarm capabilities.
Or, to be over-cautious, you can enable both Veeam One and vCenter alarms for the first time, make sure they double each other and leave just Veeam One.
Thanks.

Cool, thanks for the clarification.
So in this case what could possible make the VeeamONE alarm stops firing ?

[Vitaliy S.]

Broken vCenter Server (no API, no events) or not responding ESXi hosts in case you're using standalone connections.

[albertwt]

Broken vCenter Server (no API, no events) or not responding ESXi hosts in case you're using standalone connections.

Cool, so in this case I guess there is no caveats in turning off all VCenter alarm and rely solely on VeeamONE.
if there is one scenario please let us know or PM me.

Thanks,

[Vitaliy S.]

Yes, you can rely on Veeam ONE to monitor your critical services in the virtual infrastructure.