Documentation forDatabase Performance Analyzer

Create a DPA Administrative alert

Administrative alerts are used to monitor the health of the database system. For example, you can configure an alert that is triggered when a database instance is not accessible or when any database parameter changes.

Some PostgreSQL administrative alerts can use data from multiple databases. Those alerts are identified here. To enable DPA to collect data from multiple databases in a PostgreSQL cluster, you must configure a foreign data wrapper.

  1. From the DPA menu in the upper-right corner, click Alerts.
  2. In the upper-right corner, click Manage alerts.
  3. Select Administrative as the Alert Category, select the Alert Type, and then click Create Alert.

    To find out more about each alert type, see DPA alert categories and types. Or select a type to display a description on the right.

  4. In the Alert Information section:

    1. Enter a unique name.

    2. If you want to disable the alert, clear the Active checkbox.
    3. Select the execution interval.

      The execution interval specifies how often the alert runs and the amount of data that DPA examines. For example, if the execution interval is 10 minutes, DPA executes the alert every 10 minutes and examines the last 10 minutes of data to determine whether to trigger the alert. DPA recommends an execution interval of at least 10 minutes to prevent unnecessary alerts from a temporary condition.

    4. Enter the notification text to be sent with the email notification. Include an explanation of the issue and the suggested resolution.

      If you apply a custom email template to this alert, the email notification includes the notification text if the email template contains one of the following variables:

      • Alert Notification text: [=alert.notificationText]
      • Results: [=dpa.body] (included by default)
  5. Under Database Instances, specify the database instances that the alert applies to. You can use a rule to identify instances that meet one or more conditions, or you can manually select the instances.

    • When you select a rule, DPA uses the rule conditions to determine which instances the alert monitors. If your environment changes, the list of instances is automatically updated.

      1. Click Use rule.

        The Rules page lists the existing rules.

      2. Select an existing rule, or create a new rule and then select it.

      3. Click Assign rule.

        The alert definition shows the selected rule name, rule expression, and a list of instances that currently meet the rule conditions.

    • If you manually select the database instances, the list is static.
      1. Click Select database instances.

        The Available database instances page lists database instances. If the alert type is specific to one type of database, the page lists only instances of that type.

      2. Use the Search bar to locate instances, or apply filters to refine the list.
      3. To select all instances in the list, click the checkbox above the list. To select individual instances, click the checkbox next to each instance.
      4. Click Assign and go back.

        The alert definition shows the list of selected instances.

  6. If any Alert Parameters are required for the alert type, enter the required value.

    For the SQL Server Backup Frequency, SQL Server Recovery Backup Assets Size, and SQL Server Backup Time Allotted alerts, select an Evaluation Option if you do not want DPA to include all previously backed up databases when it evaluates the alert. (For example, you might want to exclude databases used for testing that do not need regular backups.)

    • If you select Use TRACK_BACKUPS_FOR_DBS, set the TRACK_BACKUPS_FOR_DBS advance option for each selected database instance.

    • If you select Exclude DBs or Include DBs, enter a comma-separated list of the databases to exclude or include.

    If a PostgreSQL Administrative alerts can use data from multiple databases, the Alert Parameters section includes the Schema Name option. Leave the default value of Catalog to collect data from a single database. To include data from multiple databases, specify the schema or schemas that include the data. See Specifying schemas in an alert definition.

  7. Specify the thresholds for each alert level you want to enable.

    Some Administrative alerts have only one level.

    • Leave the Max value for the highest level blank to alert on anything above the minimum value for that level.

    • If you configure multiple levels, the Max value for lower levels must equal the Min value for the next higher level.

    • When you enter a Max value for a level, DPA alerts at that level when the value is greater than or equal to the Min value but less than the Max level. For example, if the Min value is 5 and the Max value is 10, DPA alerts at that level when the value is 5 or more, but less than 10.

  8. Select the person or group who gets notified when each alert level is triggered and when the alert is broken. (The alert status is set to Broken if an error occurs during execution.)

    To send notifications when the alert returns to Normal, select a recipient for Normal.

    • If you have not added the person or group as a contact in DPA, click Add Contact or Add Contact Group and create the contact or group.
    • Select an SNMP contact to send SNMP traps when the alert is triggered. Select an SNMP contact for Normal to send a clearing notification when the alert status returns to Normal.
  9. Verify or change the notification policy.

    To send notifications when the alert returns to Normal, the notification policy must be Notify when level changes.

  10. Select the email template that defines the contents of the email notifications sent by this alert.
  11. Click Email Preview to see an example of the email that will be generated using the selected email template and contact information.

    If the alert applies to multiple database instances, select an instance in the Email Preview dialog box and click OK. After reviewing the email, you can select a different database instance or click Cancel to close the Email Preview dialog box.

    The email sent to users might not exactly match the preview because some alert parameters cannot be evaluated during a preview.

  12. Click Test Alert to test the alert and view the current alert level. The test does not generate an email.
  13. Click Save.