Hi!

Have you seen this:

http://blogs.technet.com/b/kevinholman/archive/2007/12/12/adding-custom-information-to-alert-descriptions-and-notifications.aspx 

/henrik
Sendt fra min Samsung-enhed


-------- Oprindelig meddelelse --------
Fra: "Orlebeck, Geoffrey" <[email protected]>
Dato: 27/01/2016 23.30 (GMT+01:00)
Til: "'[email protected]'" <[email protected]>
Emne: [msmom] RE: Rule vs. Monitor: Alert Parameters for Log File Monitoring

I still haven’t come up with the appropriate Alert Parameter syntax for pulling the LogFileDirectory and LogFileName parameters out of a 2-state monitor. Anyone know? The following works as a rule using GenericCSVLog:

 

<AlertParameter1>$Data/EventData/DataItem/LogFileDirectory$</AlertParameter1>

<AlertParameter2>$Data/EventData/DataItem/LogFileName$</AlertParameter2>

 

 

Thanks,

Geoff

 

From: [email protected] [mailto:[email protected]] On Behalf Of Orlebeck, Geoffrey
Sent: Monday, January 25, 2016 10:51 AM
To: '[email protected]'
Subject: [msmom] Rule vs. Monitor: Alert Parameters for Log File Monitoring

 

I originally created a rule (Rule.xml attached) that fulfilled the original requestor’s desire of raising an alert when a certain entry is written to a log file. However, now the requestor asked for a 60min reset on the alert. My understanding is a monitor would be the better option since Rules do not affect health state. I attempted to port the original rule to a new monitor (see Monitor.xml), but it’s failing to replace the parameters (LogFileDirectory, LogFileName). Now I understand different Module Types (GenericCSVLog.FilteredEventProvider versus GenericCSVLog.SingleEventTimer2StateMonitorType) may not share the same structure. On the Rule, I can input the following Alert Parameters and the appropriate values are inserted in the Alert Description:

 

<AlertParameter1>$Data/EventData/DataItem/LogFileDirectory$</AlertParameter1>

<AlertParameter2>$Data/EventData/DataItem/LogFileName$</AlertParameter2>

 

However, on the Monitor those values do not get replaced. I found this on MSDN as it relates to a GenericCSVLogReader Module Type:

 

 

I can’t find the equivalent on MSDN for 2-State-Monitor GenericCSVLog Module Type.

 

·         Does anyone know what the format should be for the Monitor.xml to properly replace the Alert Parameters specifically for LogDirectory and LogFileName?

 

·         How/Where do you find such information? MSDN has the OpsMgr MP Development Kit (https://msdn.microsoft.com/en-us/library/jj130093.aspx) which helps in some cases. And perhaps what I’m looking for is readily available in MSDN, I’m just having issues finding it. I don’t want to come across as if I just throw my problems to this group to have them resolved for me. If there are resources the more advanced authors among us are using I’d love to have them in my tool bag, too. If it’s simply trial-and-error + experience + maintaining really good notes/documentation for future reference, I can work towards that. Just seems there is not as much readily available info with examples that help connect the dots in my brain when I run into these sorts of walls.

 

Thanks in advance!

 

-Geoff

Confidentiality Notice: This is a transmission from Community Hospital of the Monterey Peninsula. This message and any attached documents may be confidential and contain information protected by state and federal medical privacy statutes. They are intended only for the use of the addressee. If you are not the intended recipient, any disclosure, copying, or distribution of this information is strictly prohibited. If you received this transmission in error, please accept our apologies and notify the sender. Thank you.

 

Confidentiality Notice: This is a transmission from Community Hospital of the Monterey Peninsula. This message and any attached documents may be confidential and contain information protected by state and federal medical privacy statutes. They are intended only for the use of the addressee. If you are not the intended recipient, any disclosure, copying, or distribution of this information is strictly prohibited. If you received this transmission in error, please accept our apologies and notify the sender. Thank you.

Reply via email to