You can add the macro ${WindowsEventMessages} to your "Component' alerts. if the macro isn't applicable to the component that is alerted on then the macro will not appear in the message text. When/if the alert triggered is for a Windows Event Log Monitor the macro will populate properly and contain the full text of the Windows Event Log in the message body.
Thanks aLTeReGo. So for a generic component monitor, I'd need to add something like, "if this alert is triggered by a Windows Event Log Monitor, the event(s) may appear below" kind of a heading? There isn't a more elegant way of doing it, correct?
Any idea why Application custom properties are no longer available as trigger conditions, and not populating in alerts? Breaks my alerts escalation logic.