This monitor catches Xian events that notifies when the Threads open has changed its state.
Threads open is over threshold.
The number of threads that are currently open is above the maximum threshold configured in Xian Network Manager 2012.
The number of active threads or clients has increased past your parameters due to demand.
Monitor the origin of queries. If you want to limit the number of threads, you should limit the number of connections. Clients that send several queries to the server could use persistent connections and you can use the max_user_connections variable to limit overall connections or limit per user.
Monitors the number of open threads.
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.ThreadsOpen.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="ThreadsOpen_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>