Dameng Database (DM8)¶

Installation and Configuration¶

Prerequisites¶

• Install DM8
• Install DEM

DEM, which stands for Dameng Enterprise Manager, is a web-based tool provided by Dameng, written in java, used to monitor the Dameng database.

The directory is $DM_HOME/web, where this directory contains the DEM installation manual (DEM.pdf) and the running program dem.war. Deployment can be carried out according to the manual.

Metric Exposure¶

DEM exposes metrics on port 8090 by default. You can view metric-related information through a browser at http://clientIP:8090/dem/metrics. If access fails, it indicates that the capability to expose metrics has not been enabled. Follow the steps below to enable it.

• Add Database

By default, after a successful installation of DEM, it does not directly monitor databases; configuration is required for the database to be monitored.

1. Click on the menu Intelligent Inspection -> Resource Monitoring, switch the bottom Tab to Database,

2. Click Add Single Instance/Cluster, fill in the details of the database to be monitored.

3. Configure Prometheus

4. Click on the menu System Management -> System Settings, select prometheus_metric_nodes under the Other Features module,

5. Select the databases that need to be monitored. Click the Confirm button to complete the configuration.

6. Verification

View metric-related information through a browser at http://clientIP:8090/dem/metrics. The port is the DEM access port, which may vary. Use the actual port as appropriate.

DataKit Collector Configuration¶

Since DEM can directly expose a metrics url, collection can be performed using the prom collector.

Adjustments are as follows:

urls = ["http://clientIP:8090/dem/metrics"]
source = "dm"
interval = "10s"

Other configurations can be adjusted as needed

, parameter adjustment description:

• urls: Prometheus Metrics address, fill in the corresponding component-exposed Metrics url here.
• source: Collector alias, recommended for differentiation.
• interval: Collection interval.

Restart DataKit¶

systemctl restart datakit

Metrics¶