1 Reply Latest reply on Nov 12, 2018 4:11 AM by Andrew Waters

    List of VMWare vCenter events OOB discovery captures.

    Amrendra Kumar Singh
      Share This:

      Hi All,

       

      I have a use case where I need to trigger discovery scan for below mentioned vCenter events. (We may not use all of them.)

       

       

      Object NameRemarks
      VmBeingClonedEventyes
      VmBeingClonedNoFolderEventyes
      VmBeingCreatedEventyes
      VmBeingDeployedEventyes
      VmBeingHotMigratedEventyes
      VmClonedEventyes
      VmCloneEventyes
      VmCloneFailedEventyes
      VmCreatedEventYes
      VmDeployedEventYes
      VmEmigratingEventYes
      VmEventGeneral dataobject
      VmOrphanedEventYes
      VmPoweredOffEventYes – optional
      VmPoweredOnEventYes – optional
      VmReconfiguredEventYes
      VmRegisteredEventYes
      VmRelayoutSuccessfulEventYes
      VmRelocateSpecEventYes
      VmRenamedEventYes
      VmResourcePoolMovedEventYes – optional
      VmResourceReallocatedEventYes – optional

       

       

      As per now, for past one month we have collected below mentioned event from OOB vCenter event source.

       

      Event Type
      vim.event.VmRelocatedEvent
      vim.event.VmBeingRelocatedEvent
      vim.event.VmRemovedEvent
      vim.event.VmMigratedEvent
      vim.event.VmBeingHotMigratedEvent
      vim.event.VmRenamedEvent
      vim.event.DrsVmMigratedEvent
      vim.event.VmAutoRenamedEvent
      vim.event.VmRenamedEvent

       

       

      Question: -

      1. Does OOB vCenter event collection is limited to the events mentioned above?

      2. If I want to collect the events like "VmCloneEvent" or "VmBeingHotMigratedEvent", can I do it using OOB vCenter event?

       

      Thank you.

        • 1. Re: List of VMWare vCenter events OOB discovery captures.
          Andrew Waters

          The events collected depends upon the metadata event_source and events_to_collect value. If you write a pattern including this then the system will also collect events of the named type.

           

          So for example if you add a pattern with

          ...

          metadata

            event_source := 'vCenter';

            events_to_collect := 'vim.event.VmCloneEvent';

          end metadata;

          ...

          triggers

            on event := ExternalEvent created where type := 'vim.event.VmCloneEvent';

          end triggers.

          ...

          will mean the system tries to capture VmCloneEvent events from vCenters. Be aware that vCenter can create a lot of events so be careful about the events you want. Additionally you may not be able to access the system specified in the event. It may not actually yet be available from the vCenter. For example just because you get a vmCreateEvent does not mean the VM has actually booted and is available.

          2 of 2 people found this helpful