2025 yılında vebadan ölüm: ABD'nin Kuzey Arizona bölgesinde bir kişinin pnömonik vebadan öldüğü bildirildi.

Veba, insanlarda artık çok nadir görülüyor. ABD'de yıllık yaklaşık 7 vaka kaydediliyor. Federal sağlık yetkililerine göre bunların çoğu batıdaki eyaletlerde ortaya çıkıyor.

Yerel sağlık yetkililerine göre Coconino bölgesinde yaşanan ölüm, 2007'den bu yana pnömonik veda kaynaklı ilk ölüm… https://www.eshahaber.com.tr/haber/2025-yilinda-vebadan-olum-241007.html?utm_source=dlvr.it&utm_medium=mastodon EshaHaber.com.tr #veba #pnömonikveba #sağlık #hıyarcıklıveba #Coconino

Finally resolved the Github Action for automating our releases, there was format/syntax change in Goreleaser 😡

Thank you Michael Gasch for your continued support! 🙏

We now have a new VMware Event Broker v0.8.0 release!

#VEBA

[New] - Google Chat space notification for failed vCenter Server Appliance (VCSA) backups using VEBA https://williamlam.com/2024/01/google-chat-space-notification-for-failed-vcenter-server-appliance-vcsa-backups-using-veba.html

👆While message customization isn't as extensible as Slack you can now use #VEBA to send alert when VCSA backup fail to Google Chat space

I ♥️ Event-Driven Automation!

Given we now use Google Chat for work ... figured it would be good to have a VMware Event Broker Appliance (#VEBA) function for sending notifications to a given Space, especially useful for when VCSA backups fail and you can get notified immediately!

Thanks to r/Is-Not-El some VMware Fling downloads (non-auth) have been archived & still be downloaded using: https://archive.org/download/flings.vmware.com

🔸#ESXionARM Fling can still be downloaded from https://customerconnect.vmware.com/downloads/get-download?downloadGroup=ESXI-ARM

🔹#VEBA OVA can be DL'ed via Archive or built https://github.com/vmware-samples/vcenter-event-broker-appliance

flings.vmware.com directory listing

#vSphere80U2 now has over 2K+ Events in vCenter Server https://github.com/lamw/vcenter-event-mapping/blob/master/vsphere-8.0u2.md

That's a LOT of #EventDrivenAutomation potential with #VEBA 😎 Quick diff, shows a lot more new core storage/vSAN events along with bunch of other operational events that would benefit admins

vcenter-event-mapping/vsphere-8.0u2.md at master · lamw/vcenter-event-mapping

Contribute to lamw/vcenter-event-mapping development by creating an account on GitHub.

GitHub
Just had great convo w/another happy #VEBA user who easily built #EventDrivenAutomation based on vSphere Tag (attach/detach) to enrich their VMs w/additional metadata from ServiceNow. Very humbling to see what our users have been able to do! Truly unlimited potential

Tanzu Sources for Knative integration w/VMware Event Broker Appliance (#VEBA) PR has been merged! https://github.com/vmware-samples/vcenter-event-broker-appliance/pull/1075 🥳🙌

Huge milestone as we march towards our v0.8 release, still more to do (update examples, docs & website) but good start!

feat: Integrate Tanzu Sources (vSphere/Horizon) for Knative by lamw · Pull Request #1075 · vmware-samples/vcenter-event-broker-appliance

Summary This change refactors VEBA to now use Tanzu Sources for Knative when configuring either vSphere or Horizon sources and maintains event-router for Webhook processor configurations. In additi...

GitHub

For my Friday exploration today ... will be playing around with Tanzu Sources for Knative https://github.com/vmware-tanzu/sources-for-knative with VMware Event Broker Appliance (VEBA)

This would allow #VEBA users to take f(n) from OSS->Commercial (but does require tiny tweak due to schema differences)

GitHub - vmware-tanzu/sources-for-knative: VMware-related event sources for Knative.

VMware-related event sources for Knative. Contribute to vmware-tanzu/sources-for-knative development by creating an account on GitHub.

GitHub

Speaking of #VEBA ... I've seen an uptick in new users doing some really cool #EventDrivenAutomation with some pretty large vSphere environments 🤯

The use cases are truly endless once you understand the potential of the platform!