WilliamLam.com

  • About
    • About
    • Privacy
  • VMware Cloud Foundation
    • VMware Cloud Foundation 9.1
    • VMware Cloud Foundation 9.0
  • VKS
  • Homelab
    • Hardware Options
    • Hardware Reviews
    • Lab Deployment Scripts
    • Nested Virtualization
    • Homelab Podcasts
  • VMware Nostalgia
  • Apple

Google Chat space notification for failed vCenter Server Appliance (VCSA) backups using VEBA

01.22.2024 by William Lam // Leave a Comment

It is always good idea to verify that your vCenter Server Appliance (VCSA) backups are occurring and if there are any failures, you are notified about them immediately!

As alluded to at the end of that blog post, you can easily build event-driven automation using the popular VMware Event Broker Appliance (VEBA) solution, triggering notifications based on several types of VCSA backup events:

  • com.vmware.applmgmt.backup.job.failed.event
  • com.vmware.applmgmt.backup.job.finished.event
  • com.vmware.applmgmt.backup.job.start.event

I recently built a PowerShell function that would send a notification to a Google Chat space by enabling their incoming webhook integration as you can seen from the screenshot below:


While the message customization is not as extensive as using Slack (e.g. supporting advanced layouts and emoji), it does get the job done and you will know immediately when a backup has failed or when it has started or has completed.

Note: For existing VEBA users (pre-v0.8 release), the function.yaml needs to be updated to trigger off of the subject keyword rather than the type, which is due to replacing the event router with Tanzu Sources for vSphere. You also need to ensure the prefix of "com.vmware.vsphere" is removed along with trailing "v0" as this is the next syntax for vCenter Events once VEBA v0.8 is released.

spec:
  broker: default
  filter:
    attributes:
      subject: com.vmware.applmgmt.backup.job.failed.event

Categories // Uncategorized Tags // vami, VCSA

Heads Up - New image identifier required by VM Service in vSphere 8.0 Update 2

09.27.2023 by William Lam // Leave a Comment

I have been a huge fan of the VM Service capability, which has been an integral part of vSphere with Tanzu since its inception with the release of vSphere 7.0 Update 2. The VM Service had another major update last year that enabled further customization of workloads with the Sphere 8.0 release. What makes the latest update so exciting for vSphere with Tanzu users is that in vSphere 8.0 Update 2,ย the VM Service now officially supports deploying Microsoft Windows VMs and can also create VMs using all the rich VM configuration options that the vSphere platform supports!

I just got to try out the new VM Service feature yesterday and deployed a Windows OVF that I had built almost a year ago, which I have waiting for this feature to finally ship! ๐Ÿ˜€


I typically save my VM Service YAML manifest files so that I can easily reuse them but after performing the kubectl apply, I noticed nothing was being deployed and when I went to retrieve more details by running:

kubectl get vm -o yaml

I noticed the following error message:

message: 'Failed to get the VM''s image: windows-desktop-10'

[Read more...]

Categories // Uncategorized

How to setup private GitLab on a Synology for Project Keswick?

09.26.2023 by William Lam // 3 Comments

My recent blog post on setting up a custom vSphere Content Library on my Synology gave me another idea that I had been thinking about regarding Project Keswick, which was announced back at VMware Explore Las Vegas.

If you have network connectivity to the Keswick Cloud Service, you can easily associate a Git repository, which is used for host configurations and workload deployments using GitOps using Github or even a privately managed Gitlab instance. For organizations that have additional compliance, security or air-gapped requirements, using the Keswick Cloud Service may not be an option. With that said, Project Keswick also supports an advanced deployment option where the association of a Git repository, such as GitLab, can also be accomplished without requiring the use of the Keswick Cloud Service.

While I have had experience using both Github as well as GitLab, which VMware uses to host its own code repository, I have actually never setup my own GitLab instance before. I thought this would be a great learning opportunity, especially with the ability to run additional add-on applications on a Synology.

After a bit of researching online, I found that GitLab can easily run as a Container workload and it just so happens that the Synology DiskStation Manager (DSM) has a package for running containers creatively called Container Manager and below are the step by step instructions for setting up GitLab running on Synology DSM 7.2.

[Read more...]

Categories // Uncategorized Tags // GitLab, Synology

  • « Previous Page
  • 1
  • …
  • 3
  • 4
  • 5
  • 6
  • 7
  • …
  • 124
  • 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

  • Quick Tip: Resolving OVFTool "Failed to Send File" Errors on macOS 06/13/2026
  • VCF 9.1 - Are You Using the Correct ESXCLI Command to Enable NVMe Tiering? 06/12/2026
  • VCF 9.1 - OCuLink External Graphics (eGPU) Passthrough with vSphere Kubernetes Service (VKS) 06/12/2026
  • VCF 9.1 - Quick Tip: Uninstalling Optional Day-N Components 06/11/2026
  • VCF 9.1 - Deploying VCF Operations for Networks to non-Management Network 06/10/2026
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 © 2026

Loading Comments...