A user asked about a monitoring trigger which only works for error events, and a workaround was suggested – creating a scheduled task which is triggered by the information event. This task then creates an error or warning event. The Academy can be found at https://cuacademy.controlup.com/
Read the entire ‘Monitoring Trigger Not Working for Information Events’ thread below:
Hi @all,
we are using parts of CU Realtime Standard / predefined Trigger for monitoring our XenApp Environment called "Citrix XenDesktop Error Events"
This trigger generates E-Mails when there are errors shown in the Applog and Source is "Citrix Broker Service". Sometimes we
become messages that Delivery Controller etc loosing connection to the license server. This can happen when Veeam is deleting
snapshots after backup -> short network interrupt. After successfull reconnect to the license server a entry in the application
is shown "EventID 1150 , "The Citrix Broker Service successfully contacted the license server …" But not as error, it`s
a information. But trigger, monitoring event entries are only working with "error" state.
Any ideas ?
You can create a scheduled task on the server which is triggered by the Information event and then creates an error or warning event.
Silly but solid workaround…
Yes i know…not comfortable but it works.
Continue reading and comment on the thread ‘Monitoring Trigger Not Working for Information Events’. Not a member? Join Here!
Categories: All Archives, ControlUp for VDI