Pro.Monitor V6.7
Trouble shooting
Monitors Guide
Trouble shooting
Monitors Guide
Operations executed on the database occur within working threads. A long running thread can potentially indicate performance or optimization issues. This monitor will look for running threads and notify when a threads runs for too long
You can define a max runtime threshold in order to be notified if a thread is running for too long You can specify different thresholds per service
Parameter | Description |
---|---|
Active | If checked, the rule is enabled and will be processed |
Host | Can be used to restrict the monitoring to a given host (multi instance case). A star (‘*’) will match any host |
Service | Filters threads from a given service. A star (‘*’) will match any service |
Max duration (ms) | The threshold for the long running threads alarm |
Severity | Defines the level of severity of the alarm that will be generated if one of the thresholds is reached |
Auto clear | If set, the generated alarms will be automatically cleared from the console if the alarm condition is not fulfilled anymore |
Alarm tag | You can define some text to use as a prefix of the alarm message generated by the current rule |
Alarm | Defines if an alarm has to be generated for the given rule |
Metric | Defines if a metric has to be generated for the given rule |
metricId | metricUnit | metricTarget | metricDescription |
---|---|---|---|
THREADS_COUNT | Threads | HOST | Returns the number of running threads |