Monitor database with FMON

Monitoring gives you real-time visibility into a cluster's status, performance, and resource usage. It collects metrics and logs through FPT Monitoring and presents them on Grafana dashboards, so you can spot anomalies before they become incidents.

Prerequisites

Monitoring must be activated for your account by FPT Support. If it is not, the Monitor tab shows a screen asking you to contact the support team.

Open the Monitor tab

1. Log in to FPT Cloud Portal and select Database Platform → All Database.
2. Click the cluster ID, then open the Monitor tab.

Once monitoring is available, the tab lists the metrics and logs offered for your engine type. Anything not yet integrated with FPT Monitoring shows Integrated Status as Disabled.

Integrate or disconnect monitoring

In the Workspace List:

• Select Integrate for a workspace to start collecting its metrics and logs. Confirm in the dialog. Integrated Status changes to Enabled and FPT Monitoring begins collecting.
• Select Disintegrate to stop collection. Confirm in the dialog. Integrated Status returns to Disabled.

View workspace information

Once Integrated Status reads Enabled, click the workspace name to open its detail page. It holds the dashboard URL, contact points, datasources, and the credentials you need for Grafana.

View metrics and logs

1. On the workspace detail page, click the dashboard URL to open the Grafana login page.

   

2. Enter the Basic Authentication – Username and Basic Authentication – Password shown on the workspace detail page, then click Login.

   

Metrics

1. Click Toggle Menu, then select Dashboards.

2. Select the template matching your engine type to see its folders.

   

3. Open a folder to view its metrics.

   

Logs

1. Click Toggle Menu, then select Explore.

   

2. Select Loki as the data source.

   

3. In the label filter, choose the label you want to filter on.

   

4. In the value field, choose the object to view logs for.

   

The matching log entries appear below the query.

Next steps

• Configure auto scaling to act on what the metrics show
• View Action Logs for operation history rather than engine metrics
• Configure parameters