<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom" xmlns:content="http://purl.org/rss/1.0/modules/content/"><channel><title>Operations on Why did IT fail</title><link>https://www.why-did-it.fail/categories/operations/</link><description>Recent content in Operations on Why did IT fail</description><generator>Hugo -- gohugo.io</generator><language>en</language><copyright>Copyright © 2026 Dominik Textoris (formerly Zorgnotti). All Rights Reserved.</copyright><lastBuildDate>Fri, 12 Apr 2024 00:00:00 +0000</lastBuildDate><atom:link href="https://www.why-did-it.fail/categories/operations/index.xml" rel="self" type="application/rss+xml"/><item><title>New in Operations - Payload templates scope Enhancements</title><link>https://www.why-did-it.fail/blog/2024-01-vrops-payload/</link><pubDate>Fri, 12 Apr 2024 00:00:00 +0000</pubDate><guid>https://www.why-did-it.fail/blog/2024-01-vrops-payload/</guid><description>A significant new enhancement in VMware Aria Operations 8.17.1 is the Payload Templates Scope Enhancements.
Essentially, this feature allows you not only to include an object that is affected by an issue in a notification but also to include its descendant objects.
Why is this feature significant?
Consider a scenario where there is an outage on one ESXi host. This issue is primarily a concern for the infrastructure teams responsible for operations, but it also impacts the workloads and could potentially affect service levels.</description></item></channel></rss>