WilliamLam.com

  • About
    • About
    • Privacy
  • VMware Cloud Foundation
  • VKS
  • Homelab
    • Resources
    • Nested Virtualization
  • VMware Nostalgia
  • Apple

Publishing and consuming custom events with VMware Event Broker Appliance (VEBA)

09.15.2021 by William Lam // Leave a Comment

One of the really exciting features that will be included in the upcoming release of the VMware Event Broker Appliance (VEBA) v0.7 release (currently in Tech Preview) is the support for incoming webhooks! This will allow customers to easily build event-driven automation for non-vSphere based events and even non-VMware events while still maintaining a consistent consumption experience. If you are interested in learning more about the upcoming VEBA v0.7 release, Michael Gasch and myself will be doing a LIVE VMworld Session - VEBA Revolutions - Unleashing the Power of Event-Driven Automation #CODE2773 that you should definitely add to your schedule builder!

Webhook support can easily be enabled during the initial VEBA appliance deployment using a few new OVF properties or configured through the VMware Event Router configuration when deploying to an existing Kubernetes cluster using kubectl or Helm. Once the webhook endpoint is running, users can simply publish their custom events as a conformant CloudEvent and VEBA will ensure these custom events are immediately available for consumption by function authors. This means any product and/or service that can construct a custom HTTP payload including headers will be able to take advantage of this new VEBA feature! I also want to mention that this is NOT the only way to produce custom events that VEBA can ingest, but is certainly one simple way.

To help make this concept more concrete, I wanted to see how we could integrate VMware Cloud events into VEBA by using this new webhook mechanism and using the VMware Cloud Notification Gateway. Below is a diagram to help illustrate what is happens when a VMware Cloud event is generated and how it can be consumed by VEBA. The beauty of this type of a solution is the "Event Producer" does not have to know anything about the "Event Consumer" or how they might consume the data. The producer simply pushes events into VEBA and if there is a consumer who cares about a specific event and wishes to do something about it, they can create a function that will listen for a specific event(s) and perform an operation like sending to Slack as an example.

  1. Event is produced by VMware Cloud and pushed by the VMware Cloud Notification Gateway (NGW)
  2. A conformant CloudEvent payload is constructed from VMware Cloud event by NGW service
  3. NGW forwards the custom CloudEvent to VEBA's webhook endpoint (https://[VEBA-FQDN]/webhook)
  4. VEBA functions can now react to these custom CloudEvents (e.g. SDDC Provisioned Event)

[Read more...]

Categories // VMware Cloud, VMware Cloud on AWS Tags // Notification Gateway, VEBA, VMware Cloud, VMware Cloud on AWS, VMware Event Broker Appliance

How to modernize your vSphere Alarm actions using the VMware Event Broker Appliance (VEBA)?

07.06.2021 by William Lam // Leave a Comment

The VMware Event Broker Application/Appliance (VEBA) solution makes it extremely easy for customers to build Event-Driven Automation that can react to over 1800+ vSphere-based Events using your favorite scripting or programming language of choice that includes PowerCLI, PowerShell, Python and Go to just name a few.

The benefits of VEBA can extend beyond just vSphere Events and can also be used with both new and existing vSphere Alarms. In fact, vSphere Alarms is just another a type of vSphere Event, which then makes it super easy to work with if you are already familiar with VEBA. Similar to the "triggers" that are supported with vSphere Events, the available options for extensibility in vCenter Server is super limited.


In addition to the limited options for extending vCenter Server, there are also valid security concerns with resource utilization and opening up access to run arbitrary scripts directly on the VCSA, which we all know is a bad practice for so many reasons. What if we could easily extend the actions to a vSphere Alarm to send notifications to Slack or Microsoft Teams, automatically file an IT Ticket or run specific automation or remediations tasks!?

[Read more...]

Categories // Automation, vSphere Tags // alarm, Knative, VEBA, VMware Event Broker Appliance

VMware Event Broker Appliance (VEBA) v0.6 is now available!

04.20.2021 by William Lam // Leave a Comment

I am super excited today to announce the release of version v0.6 of the VMware Event Broker Appliance (VEBA)! The team and I have been heads down for the past several months working on a number of exciting and brand new capabilities that I think both, existing and new customers, will really enjoy.

In addition to the core team and community contributions, I would also like to welcome and thank two of our newest contributors to the VEBA project, both making significant contributions to our v0.6 release:

  • Denis Chorbadzhiyski (Engineer on the vSphere UI team at VMware)
  • Dimitar Milov (Engineer on the PowerCLI team at VMware)

Release v0.6 is an important milestone for the team and for the VEBA project. VEBA now leverages an end-to-end VMware OSS stack by default, which also provides a strong architectural foundation for future product updates and innovations. We could not be more excited to share this release with our community 🥳 and below are just some of the key feature highlights.

Embedded Knative


Knative is a Kubernetes-based platform to deploy and manage modern serverless workloads. Support for Knative in VEBA was first introduced in our v0.5 release last December and only supported an external Knative deployment. With this latest release, VEBA now supports an embedded Knative deployment which includes the full Knative Serving and Eventing components which is automatically configured within VEBA.

[Read more...]

Categories // Automation, vSphere Tags // Knative, VEBA, VMware Event Broker Appliance

  • « Previous Page
  • 1
  • 2
  • 3
  • 4
  • 5
  • Next Page »

Search

Thank Author

Author

William is Distinguished Platform Engineering Architect in the VMware Cloud Foundation (VCF) Division at Broadcom. His primary focus is helping customers and partners build, run and operate a modern Private Cloud using the VMware Cloud Foundation (VCF) platform.

Connect

  • Bluesky
  • Email
  • GitHub
  • LinkedIn
  • Mastodon
  • Reddit
  • RSS
  • Twitter
  • Vimeo

Recent

  • Programmatically accessing the Broadcom Compatibility Guide (BCG) 05/06/2025
  • Quick Tip - Validating Broadcom Download Token  05/01/2025
  • Supported chipsets for the USB Network Native Driver for ESXi Fling 04/23/2025
  • vCenter Identity Federation with Authelia 04/16/2025
  • vCenter Server Identity Federation with Kanidm 04/10/2025

Advertisment

Privacy & Cookies: This site uses cookies. By continuing to use this website, you agree to their use.
To find out more, including how to control cookies, see here: Cookie Policy

Copyright WilliamLam.com © 2025

 

Loading Comments...