All documents

Managed – FPT Database Engine

    Notification
    Notification
    Updated on 10 Jan 2026

    The Notification feature helps users receive alerts for key events and service statuses related to their clusters. These notifications can be delivered via email or through third party channels, ensuring you are promptly informed about backup jobs, resource thresholds, scaling events, and other critical database operations.

    Currently, the notification system supports the following alert categories:

    • Backup Service & Restore Alerts – notifications for enabling/disabling backup service, backup job success/failure, and restore job results.
    • Resource Alerts – notify when vCPU, RAM, or Disk usage reaches defined thresholds.
    • Vertical Scaling Alerts – notifications for automatic scaling events (e.g., increase in CPU/RAM/Disk).

    This guide helps you set up and manage notifications to effectively track important events in FPT Database Engine on the FPT Cloud Portal.

    Step 1: Access to Notification Setting page

    Sign in to FPT Cloud Portal. From the left navigation menu, select “Database Platform” → choose your DB engine category (Relational, Non‑Relational, etc.). Select the target Cluster ID. Switch to the “Notification” tab on the cluster details page.

    • In case the feature is not enabled:

    • This applies if the notification feature for the service has been enabled and configured:

    Step 2: Enable notification

    If the Notification feature is not enabled (status "Inactive"), you must enable it before configuring the alert recipient list.

    On the “Notification” tab, click the setting icon next to Notification Management to enable the notification feature. Confirm the action in the warning dialog to complete the activation.

    Step 3: Create alert rules

    After enabling Notification, you can configure the alert recipient list for supported services. Click Add New Alert List (the plus icon next to the Notification List) to open the dialog for adding alerts.

    Enter the configuration information:

    • Type: Select the notification delivery method used to send alert messages to recipients. Available options:
      • Email: Send notifications via email.
      • Telegram: Send notifications via Telegram.
    • Current Services Notification:Select the DBaaS services that will trigger notifications when related jobs or events are completed or executed. Available options:
      • Backup – Backup job notifications.
      • Restore – Restore job notifications.
      • Resource – Resource usage notifications.
      • Vertical Scaling – Scale up notification.
    • Current Recipient List:
      • If Type = “Email” -> Enter the email address that will receive alert notifications.
      • If Type = “Telegram” -> Enter the telegram channel that will receive alert notifications.
    • Alert conditions for Current Services Notification = “Resource”:
      • vCPU more than (%): Specify the CPU usage threshold (percentage). An alert is triggered when vCPU usage exceeds this value.
      • RAM more than (%): Specify the memory usage threshold (percentage). An alert is triggered when RAM usage exceeds this value.
      • Storage more than (%): Specify the storage usage threshold (percentage). An alert is triggered when disk usage exceeds this value.
      • An alert will be sent when any one of the configured conditions is met. If all three conditions are met, multiple alert notifications will be sent.

    After entering all the information, click "Add" to save the configuration.

    All configured alerts appear in the Notification List on the Notification tab. You can view recipients, types, monitored services, and status (enabled/disabled). The following management operations can be performed on a configured alert:

    • Edit Alert List – click the edit (pencil) icon next to an alert list to update recipients or monitored services.
    • Disable Alert – temporarily turn off specific notifications without deleting the rule.
    • Enable Alert – re‑enable a previously disabled alert.

    Best Practices:

    • Configure alerts before enabling auto scaling
    • Use reasonable thresholds to avoid alert flooding
    • Assign alerts to operational and DBA teams
    • Combine alerts with monitoring dashboards for full observability