PEGA0026 alert: Time to connect to database exceeds limit
The PEGA0026 alert is triggered when the time to acquire a database connection has exceeded the operation time threshold.
Example message text
Time to acquire a connection has exceeded the alert threshold of 100 ms1: 152 ms2. DBName [pegarules]3 Connection 4 Status [New] Type [JDBC URL Common]5 Conn Mgr [Pega]
1. Threshold - The thresholds can change based on user setting.
2. Time - The time varies based on the connection time.
3. DBName - The database name differs from database to database.
4. Connection - Connection is the number ID of that connection.
5. Type - The Type portion of this alert contains the data source type the alert originated from in addition to important configuration information specific to that type.
6. Status - Status is no longer used with new connection manager. It appears as "[NEW]" in PEGA0026 alerts.
Everything else, like
Conn Mgr is hard-coded for the new Pega connection manager.
Default prconfig.xml settings
<env name="alerts/database/acquireConnectionAlertMS” value="100” />
The threshold for acquiring an existing, already-open database connection. The syntax value Initial [False] indicates an existing connection. 100 milliseconds is the default.
<env name="alerts/database/acquireInitialConnectionAlertMS" value="10000” />
The threshold for opening an initial database connection, when the Pega 7 Platform sends the database account user ID and passwords to the database. The syntax value Initial [True] indicates an initial connection. The default interval is 10,000 milliseconds (10 seconds).
Reasons for the alert
An initial connection time might take several seconds and not be an issue.
Acquiring a new connection (
Status: [New]) might take longer than an existing connection, but still be reasonably close to the
Acquiring existing connections should be fast and within the threshold. If requestors are unable to acquire a connection within the threshold interval, you might need a larger pool of connections.