How To: Add ESX host names in VMotion alarm emails

[jeffs_wwater]

Hi There

I have created an alarm to notify me when an Virtual Machine is VMotioned from one ESX host to another. It works well but I would like more information in the email.

Is it possible to put the ESX host name that the Virtual Machine has been VMotioned to and from in the Alarm email that is sent.


Thank You


Jeff Smith

[Gostev]

Hello Jeff, how did you setup such alarm - using the alarm based on Virtual Center event?

[jeffs_wwater]

Hi Gostev

I created an Alarm of type "Virtual Machine" (The Alarm is enabled)
it uses an "Event" Rule Type (The Rule is enabled)
it searches for the substring "Migrate" with a severity of "Information"
The Tolerance is "0" percent
and the Frequency is "1 "minute
The action is to email me
I do not suppress events.

I was hoping that when it emails me I would get the ESX host server information as well as the name of the VM being migrated.

Here is a copy of what is sent by Veeam Monitor

-------------
From: veeam@domain.com.au at VeeamServer [mailto:veeam@domain.com.au at VeeamServer]
Sent: Thursday, 2 April 2009 1:14 PM
To: IT
Subject: [Veeam Monitor] Alarm - VMotion of Server

Target: Windows 2003-SP1 - WINNT
Status: Information (Blue)
Alarm: VMotion of Server
Time: 04/02/09 13:14:18
Fired by event: Started: Migrates a Virtual Machine from one host to another

-------------

[Gostev]

Jeff, I don't have VMotion available in my own test lab, but can you please check you Virtual Center events if there is an event available that says something like "Migrating VM46 from ESX1 to ESX2 has been completed" (in other words, event that contains information you are looking to be receiving in email in its description). If there is such event then we should be able to provide a workaround for you to achieve what you want. Thanks!

[jeffs_wwater]

Hi Gostev

In VirtualCenter there are a number of events that have this information, here is an example

In the Events tab of VC for the Cluster, you get the event
Task: Migrate Virtual Machine
Migrating VM46 from esx01.domain.com.au to esx02.domain.com.au in DataCenter
Migrating VM46 off host esx01.domain.com.au in DataCenter
Changed resource allocation for VM46
Migration of VM46 from esx01.domain.com.au to esx02.domain.com.au completed

In the Events tab of VC for the Source server, there are events
Migrating VM46 from esx01.domain.com.au to esx02.domain.com.au in DataCenter
Task: Migrate Virtual Machine
Migrating VM46 off host esx01.domain.com.au in DataCenter

In the Events tab of VC for the Destination server, there are events
Changed resource allocation for VM46
Migration of VM46 from esx01.domain.com.au to esx02.domain.com.au completed

In the Events tab of VC for the VM, there are events
Task: Migrate Virtual Machine
Being migrated from esx01.domain.com.au to esx02.domain.com.au in DataCenter
Migrating VM46 off host esx01.domain.com.au in DataCenter

However in the Veeam Monitonr window there are only two events
Started: Migrate a virtual machines execution to a specific resource pool/host
Finished: MIgrate a virtual machine's execution to a specific resource pool/host

both of there were initiated by MigrateVM_Task

Is this the information you are after?


Jeff

[Gostev]

Jeff, yes this is exactly what I was after, thank you! My understanding that it is in fact possible to have any of these events to appear in Veeam Monitor - I will get the description of what needs to be done from devs and post it for you here tomorrow.

[Gostev]

Jeff, here's a description of what needs to be done. What you are doing with this is essentially overriding the default set of VC events retrieved by Veeam Monitor. Doing this will make the VC event "Migration of virtual machine {vm.name} from {sourceHost.name} to {targetHost.name} completed" to appear in Veeam Monitor, so that you could then base your alarm on it.

1. Log on to Veeam Monitor Server computer.

2. Open registry editor.

3. Create the following key:
HKEY_LOCAL_MACHINE\SOFTWARE\Veeam\Veeam Monitor for VMware Infrastructure 3\Service

4. Create new value "EventTypes" of "multi-string" type.

5. Populate it with the following list:

Code: Select all

AlarmEmailFailedEvent
AlarmScriptFailedEvent
AlarmSnmpFailedEvent
BadUsernameSessionEvent
ClusterOvercommittedEvent
DasAgentUnavailableEvent
DasHostFailedEvent
DatastoreDuplicatedEvent
DrsResourceConfigureFailedEvent
ErrorUpgradeEvent
GeneralHostErrorEvent
GeneralUserEvent
GeneralVmErrorEvent
HostAddFailedEvent
HostCnxFailedAccountFailedEvent
HostCnxFailedAlreadyManagedEvent
HostCnxFailedBadCcagentEvent
HostCnxFailedBadUsernameEvent
HostCnxFailedBadVersionEvent
HostCnxFailedCcagentUpgradeEvent
HostCnxFailedEvent
HostCnxFailedNetworkErrorEvent
HostCnxFailedNoAccessEvent
HostCnxFailedNoConnectionEvent
HostCnxFailedNoLicenseEvent
HostCnxFailedNotFoundEvent
HostCnxFailedTimeoutEvent
HostConnectionLostEvent
HostDasErrorEvent
HostLicenseExpiredEvent
HostReconnectionFailedEvent
HostUpgradeFailedEvent
InsufficientFailoverResourcesEvent
LicenseExpiredEvent
LicenseServerUnavailableEvent
MigrationErrorEvent
MigrationHostErrorEvent
MigrationResourceErrorEvent
NoAccessUserEvent
NoLicenseEvent
ResourceViolatedEvent
ScheduledTaskEmailFailedEvent
ScheduledTaskFailedEvent
ServerLicenseExpiredEvent
VcAgentUpgradeFailedEvent
VmCloneFailedEvent
VmDasUpdateErrorEvent
VmDateRolledBackEvent
VmDeployFailedEvent
VmDiskFailedEvent
VmFailedMigrateEvent
VmFailedRelayoutEvent
VmFailedRelayoutOnVmfs2DatastoreEvent
VmFailedToPowerOffEvent
VmFailedToPowerOnEvent
VmFailedToRebootGuestEvent
VmFailedToResetEvent
VmFailedToShutdownGuestEvent
VmFailedToStandbyGuestEvent
VmFailedToSuspendEvent
VmMacConflictEvent
VMotionLicenseExpiredEvent
VmPoweredOffEvent
VmPoweredOnEvent
VmRelocateFailedEvent
VmStaticMacConflictEvent
VmUpgradeFailedEvent
VmUuidConflictEvent
VmMigratedEvent

Note the last one - VmMigratedEvent - this is the new event that you need, all other events are all just a copy of events fetched by Veeam Monitor out of box.

6. Restart Veeam Monitor server.

Now you can build new alarm based on this event. By the way, keep in mind that you can use * and ? sign when specifying VC event mask. So you can do this for example: "Migration of virtual machine*completed".

[jeffs_wwater]

Hi Gostev

thanks for this, this seems to have done the job, I have now created a rule that gives me the following info in the body of the email

Target: Windows 2003-SP1
Status: Information (Blue)
Alarm: VMotion- Migration active
Time: 04/08/09 12:00:00
Fired by event: Migration of virtual machine Windows 2003-SP1 from esx01.domain.com.au to esx02.domain.com.au completed.

I hate to ask now, (however I am going to anyway), is it possible to get the "Fired by Event" text into the subject line of the email.

[Gostev]

Not in the current version, but I will ask developers to make this change in the upcoming 4.0 release.

[jeffs_wwater]

Thanks Gostev

I appreciate your efforts in all of this. I look forward to V4.0, however I am happy that I am now currently getting more out of V3.02.

Have a great Easter

Jeff

[Gostev]

I hate to ask now, (however I am going to anyway), is it possible to get the "Fired by Event" text into the subject line of the email.

This was implemented in Veeam Monitor 4.0, thanks for the feedback!