[DOC] Fix pmm-admin add mongodb command examples (PMM-14905)

documentation/docs/install-pmm/install-pmm-client/connect-database/mongodb.md

@@ -338,8 +338,7 @@ After configuring your database server, add a MongoDB service using either the u
         --username=pmm \
         --password=your_secure_password \
         --host=127.0.0.1 \
-        --port=27017 \
-        --enable-all-collectors
+        --port=27017
         ```
 
     === "Replica Set or Sharded cluster component"
@@ -348,9 +347,8 @@ After configuring your database server, add a MongoDB service using either the u
         --username=pmm \
         --password=your_secure_password \
         --host=127.0.0.1 \
-        --port=27017 \        
-        --cluster=my_cluster_or_rs_name \
-        --enable-all-collectors        
+        --port=27017 \
+        --cluster=my_cluster_or_rs_name
         ```
 
     === "Ignoring insecure server certificate"
@@ -359,39 +357,35 @@ After configuring your database server, add a MongoDB service using either the u
         --username=pmm \
         --password=your_secure_password \
         --host=127.0.0.1 \
-        --port=27017 \        
+        --port=27017 \
         --cluster=my_cluster_or_rs_name \
-        --enable-all-collectors \      
-        --tls-skip-verify        
-        ```     
-
+        --tls-skip-verify
+        ```
+
     === "With mongolog query source"
         ```sh
         pmm-admin add mongodb \
         --username=pmm \
         --password=your_secure_password \
+        --query-source=mongolog \
         --host=127.0.0.1 \
-        --port=27017 \        
-        --cluster=my_cluster_or_rs_name \
-        --enable-all-collectors \      
-        --query-source=mongolog         
-        ```        
+        --port=27017
+        ```
 
     === "SSL/TLS secured MongoDB"
         ```sh
         pmm-admin add mongodb \
         --username=pmm \
         --password=your_secure_password \
         --host=fqdn_of_your_mongo_host \
-        --port=27017 \          
+        --port=27017 \
         --tls \
         --tls-certificate-key-file=/path/to/client.pem \
         --tls-certificate-key-file-password=cert_password \  # If needed
         --tls-ca-file=/path/to/ca.pem \
         --authentication-mechanism=MONGODB-X509 \
         --authentication-database=$external \
-        --cluster=my_cluster_or_rs_name \
-        --enable-all-collectors        
+        --cluster=my_cluster_or_rs_name
         ```
 
     When successful, PMM Client will print `MongoDB Service added` with the service's ID and name. Use the `--environment` and `--custom-labels` options to set tags for the service to help identify them.
@@ -425,8 +419,7 @@ After configuring your database server, add a MongoDB service using either the u
     --password=your_secure_password \
     --host=127.0.0.1 \
     --port=27017 \
-    --agent-env-vars="LOG_LEVEL,OTHER_VAR" \
-    --enable-all-collectors
+    --agent-env-vars="LOG_LEVEL,OTHER_VAR"
     ```
 
     Only variables already set in the `pmm-agent` environment will be passed to the exporter.
@@ -449,7 +442,7 @@ After adding MongoDB service to PMM, verify that it's properly configured and co
         ```sh
         pmm-admin status
         ```
-        Look for `mongodb_mongolog_agent` - it should show the agent is running with mongolog as the query source.
+        Confirm that `mongodb_profiler_agent` appears in the output with status **Running** and query source `profiler`.
 
     === "Via web UI"
         To check the service from the UI:

documentation/docs/release-notes/3.9.0.md

@@ -63,13 +63,13 @@ For the full list of available collectors per database type, see [Connect MySQL
 
 - [PMM-14576](https://perconadev.atlassian.net/browse/PMM-14576): Fixed an issue where MongoDB backups completed successfully in PBM but PMM failed to detect this, reporting them as failed in the **Status** column on the **Backup > All Backups** page.
 
-- [PMM-14193](https://perconadev.atlassian.net/browse/PMM-14193), [PMM-15145](https://perconadev.atlassian.net/browse/PMM-15145): Fixed the built-in **MySQL Down**, **MongoDB Down**, **PostgreSQL Down**, **Valkey Down**, and **Redis Down** alerts incorrectly resolving to **Normal** when both the database and its PMM agent go down at the same time. The alert now correctly stays in **Firing** state even when metrics stop being reported.
+- [PMM-14193](https://perconadev.atlassian.net/browse/PMM-14193), [PMM-15145](https://perconadev.atlassian.net/browse/PMM-15145): Fixed built-in **MySQL Down**, **MongoDB Down**, **PostgreSQL Down**, **Valkey Down**, and **Redis Down** alerts incorrectly resolving to **Normal** when the monitored database service and its PMM agent went down at the same time. These alerts now correctly remain in **Firing** state when database availability metrics stop being reported.
 
 - [PMM-14519](https://perconadev.atlassian.net/browse/PMM-14519): Fixed MySQL services failing to connect when `--tls-skip-verify` was set on a database server with TLS disabled. PMM incorrectly treated `tls_skip_verify: true` as a request to use TLS, causing the agent to report `TLS requested but server does not support TLS` and stop collecting metrics.
 
 - [PMM-13910](https://perconadev.atlassian.net/browse/PMM-13910): Fixed **Top Hottest Collections by Read** and **Top Hottest Collections by Write** panels in the **MongoDB Sharded Cluster Summary** and **MongoDB Collections Overview** dashboards showing only internal collections instead of the busiest user collections.
 
-- [PMM-14193](https://perconadev.atlassian.net/browse/PMM-14193), [PMM-15145](https://perconadev.atlassian.net/browse/PMM-15145): Fixed built-in **MySQL Down**, **MongoDB Down**, **PostgreSQL Down**, **Valkey Down**, and **Redis Down** alerts incorrectly resolving to **Normal** when the monitored database service and its PMM agent went down at the same time. These alerts now correctly remain in **Firing** state when database availability metrics stop being reported.
+- [PMM-14905](https://perconadev.atlassian.net/browse/PMM-14905): Corrected `pmm-admin add mongodb` examples in the documentation by removing `--enable-all-collectors` from standard ADD commands. This flag enables additional collectors that add overhead and is not recommended for general use. The `mongolog` example now shows only the required options.
 
 - [PMM-15118](https://perconadev.atlassian.net/browse/PMM-15118): Fixed the **Oplog GB/Hour** panels in the **MongoDB ReplSet Summary**, **MongoDB Sharded Cluster Summary**, and **MongoDB Oplog Details** dashboards showing an empty metric name in the legend instead of the service name.