Monitoring the database transactions

Number of transactions

Set the threshold on this attribute to get notified about the number of transactions in the PostgreSQL database. By default, this attribute will not generate an alarm or warning event. For more information about this attribute, see Number of transactions attribute page.

For more information about setting an alarm or warning event for this attribute, or changing the default attribute range, see Defining a monitoring policy.

Event generated by the KM

You can see the event in the TrueSight console in Monitoring > Events.

Suggested action

The KM event indicates that you might want to increase the time delay for transactions to accommodate the number of transactions in the PostgreSQL database.

Number of transactions per second

Set the threshold on this attribute to get notified about the number of transactions per second in the PostgreSQL database. By default, this attribute will not generate an alarm or warning event. For more information about this attribute, see Number of transactions per second attribute page.

For more information about setting an alarm or warning event for this attribute, or changing the default attribute range, see Defining a monitoring policy.

Event generated by the KM

You can see the event in the TrueSight console in Monitoring > Events.

Suggested action

The KM event indicates that you might want to increase the time delay for transactions to accommodate the number of transactions per second in the PostgreSQL database.

Maximum transaction age

Set the threshold on this attribute to get notified about the number of transactions per second in the PostgreSQL database. By default, this attribute will not generate an alarm or warning event. For more information about this attribute, see Maximum transaction age attribute page.

For more information about setting an alarm or warning event for this attribute, or changing the default attribute range, see Defining a monitoring policy.

Event generated by the KM

You can see the event in the TrueSight console in Monitoring > Events.

Suggested action

The KM event indicates that you might want to increase the time delay for transactions to accommodate the maximum transaction age in the PostgreSQL database.