This monitor catches Xian events that notifies when the MySQL incoming traffic if has changed its state.
Incoming traffic is over threshold.
The total amount of incoming traffic is above the maximum threshold configured in Xian Network Manager 2012.
Increase of traffic due to peak load or persistent demand.
Evaluate the type of overload. Occasional peaks are not to worry. Otherwise, use an application server to limit concurrency for some particular operations, as well as block reloads or kill old queries from the same session; or use multiple database servers, one for areas that generate low database load and another for areas that generate high load.
Monitors the incoming traffic to the data base.
Target | Jalasoft.Xian.Common.Elements.ThirdParty.MySQL.JsXInstanceElement | ||
Parent Monitor | System.Health.PerformanceState | ||
Algorithm | WorstOf | ||
Category | StateCollection | ||
Enabled | True | ||
Alert Generate | True | ||
Alert Severity | MatchMonitorHealth | ||
Alert Priority | Low | ||
Alert Auto Resolve | True | ||
Remotable | True | ||
Accessibility | Public | ||
Alert Message |
|
<AggregateMonitor ID="Jalasoft.Xian.SmartManagementPacks.MySQLServers.MySQLIncomingTraffic.1.1" Accessibility="Public" Enabled="true" Target="ThirdParty_MySQL!Jalasoft.Xian.Common.Elements.ThirdParty.MySQL.JsXInstanceElement" ParentMonitorID="SystemHealth!System.Health.PerformanceState" Remotable="true" Priority="Normal">
<Category>StateCollection</Category>
<AlertSettings AlertMessage="MySQLIncomingTraffic_AlertMessage">
<AlertOnState>Warning</AlertOnState>
<AutoResolve>true</AutoResolve>
<AlertPriority>Low</AlertPriority>
<AlertSeverity>MatchMonitorHealth</AlertSeverity>
<AlertParameters>
<AlertParameter1>$Data/Context/Params/Param[3]$</AlertParameter1>
</AlertParameters>
</AlertSettings>
<Algorithm>WorstOf</Algorithm>
</AggregateMonitor>