Log Service:Collect monitoring data from MongoDB databases

Procedure

1. Log on to the Log Service console.
2. In the Log Application section, click Full-stack Monitoring.
3. On the Full-stack Monitoring page, click the instance.
4. On the Data Import page, enable MongoDB.

   If this is your first time to create a Logtail configuration for host monitoring, turn on the switch to go to the configuration page. If you have created a Logtail configuration, click the icon to go to the configuration page.

5. Create a machine group.
   • If a machine group is available, click Use Existing Machine Groups.
   • If no machine groups are available, perform the following steps to create a machine group. In this example, an Elastic Compute Service (ECS) instance is used.
     1. On the ECS Instances tab, select Manually Select Instances. Then, select the ECS instance that you want to use and click Execute Now.

        For more information, see Install Logtail on ECS instances.

        Important If you want to install Logtail on an ECS instance that belongs to a different Alibaba Cloud account, a server in an on-premises data center, or a server of a third-party cloud service provider, you must manually install Logtail V0.16.50 or later on the server. For more information, see Install Logtail on a Linux server. After you manually install Logtail, you must configure a user identifier on the server. For more information, see Configure a user identifier.
     2. After Logtail is installed, click Complete Installation.
     3. In the Create Machine Group step, configure Name and click Next.

        Log Service allows you to create IP address-based machine groups and custom identifier-based machine groups. For more information, see Create an IP address-based machine group and Create a custom identifier-based machine group.

   Important Make sure that the server on which you want to install Logtail can connect to the MongoDB database whose monitoring data you want to collect.
6. Select the new machine group from Source Server Groups and move the machine group to Applied Server Groups. Then, click Next.
   Important If you apply a machine group immediately after you create the machine group, the heartbeat status of the machine group may be FAIL. This issue occurs because the machine group is not connected to Log Service. To resolve this issue, you can click Automatic Retry. If the issue persists, see What do I do if no heartbeat connections are detected on Logtail?
7. In the Specify Data Source step, configure the following parameters and click Complete.

   Parameter	Description
   Configuration Name	The name of the Logtail configuration. You can enter a custom value.
   Cluster Name	The name of the MongoDB cluster. You can enter a custom value. After you configure this parameter, Log Service adds a cluster=Cluster name tag to the MongoDB monitoring data that is collected by using the Logtail configuration. Important Make sure that the cluster name is unique. Otherwise, data conflicts may occur.
   Server List	The information about the MongoDB database. Address: the address of the MongoDB database. You can enter the IP address, hostname, or domain name of the server that hosts the database. Port: the port number of the MongoDB database. Default value: 3717. Account: the username of the account that you use to connect to the MongoDB database. Note We recommend that you create a dedicated account to monitor the data of the MongoDB database and grant the account only the permissions that are required to monitor data. Password: the password of the account that you use to connect to the MongoDB database. You can add information about multiple MongoDB databases based on your business requirements.
   Custom Tags	The custom tags that are added to the collected MongoDB monitoring data. The tags are key-value pairs. After you configure this parameter, Log Service adds the custom tags to the MongoDB monitoring data that is collected by using the Logtail configuration.

   After you complete the configurations, Log Service automatically creates assets such as Metricstores. For more information, see Assets.