<ser:alertRules> <ser:alertRule name="slow" enabled="true"> <aler:description>slow</aler:description> <aler:AlertFrequency>every-time</aler:AlertFrequency> <aler:AlertSeverity>normal</aler:AlertSeverity> <aler:StopProcessing>false</aler:StopProcessing> <aler:Condition type="statistics"> <aler:config aggregation-interval="10" xsi:type="mon:monitoringConditionType" xmlns:mon="http://www.bea.com/wli/monitoring/alert/condition/monitoringstatistic"> <mon:monCondExpr> <mon:function>max</mon:function> <mon:lhs>Project$PVtest/PVtest/Transport/response-time</mon:lhs> <mon:lhs-operand-type xsi:nil="true"/> <mon:lhsDisplayName>Response Time</mon:lhsDisplayName> <mon:operator>></mon:operator> <mon:rhs>600000</mon:rhs> </mon:monCondExpr> </aler:config> </aler:Condition> <aler:AlertDestination ref="PVtest/pier"/> <aler:AlertSummary>slow</aler:AlertSummary> </ser:alertRule> </ser:alertRules>where PVtest/pier is an AlertDestination. The horrifying thing is that if I import into eclipse this sbconfig.jar, the alertRules is emptied. You can find some reference in the comments here and here. Of course I am shocked and horrified, because this is horrible and horrific. So if you want to have those SLA, you must be very careful with Eclipse....
Wednesday, August 27, 2014
OSB and SLA alerts in Eclipse
When you define a SLA alert in the OSB Console (sbconsole) this xml is added you your .proxy file :
Subscribe to:
Post Comments (Atom)
No comments:
Post a Comment