Pro.Monitor V6.7
Trouble shooting
Monitors Guide
Trouble shooting
Monitors Guide
The connections are an indicator of the database load and utilization. This monitor will watch for the number of RUNNING connections and send an alarm if too many are detected.
You can configure it to send an alarm when too many connections are open on a given instance It differentiates RUNNING connections from IDLE connections You can also monitor the connections of a given user or group of users
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 |
Connection status | Connection status |
User | If different than star (‘*’), only the connections of the given user will be taken into account |
Max Connection | The threshold of the connection alarm. If set to 0, the size won’t be monitored |
Aggregate | Defines how the connections are aggregated before comparing them to the threshold (see aggregate mode) |
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 |
---|---|---|---|
CONNECTION_COUNT_PER_USER | Connections | USER | Sends the number of connections per user |
CONNECTION_COUNT | Connections | HOST or USER | Sends the total number of connections per host |
CONNECTION_RUNNING_COUNT | Connections | HOST | Sends the total number of RUNNING connections per host |