MongoDB Stay organized with collections Save and categorize content based on your preferences.

This document describes how to configure your Google Kubernetes Engine deployment so that you can use Google Cloud Managed Service for Prometheus to collect metrics from MongoDB. This document shows you how to do the following:

• Set up the exporter for MongoDB to report metrics.
• Access a predefined dashboard in Cloud Monitoring to view the metrics.
• Configure alerting rules to monitor the metrics.

These instructions apply only if you are using managed collection with Managed Service for Prometheus. If you are using self-deployed collection, then see the source repository for MongoDB for installation information.

These instructions are provided as an example and are expected to work in most Kubernetes environments. If you are having trouble installing an application or exporter due to restrictive security or organizational policies, then we recommend you consult open-source documentation for support.

For information about MongoDB, see MongoDB.

Prerequisites

To collect metrics from MongoDB by using Managed Service for Prometheus and managed collection, your deployment must meet the following requirements:

• Your cluster must be running Google Kubernetes Engine version 1.28.15-gke.2475000 or later.
• You must be running Managed Service for Prometheus with managed collection enabled. For more information, see Get started with managed collection.

• To use dashboards available in Cloud Monitoring for the MongoDB integration, you must use mongodb_exporter version 0.20 or later.

  For more information about available dashboards, see View dashboards.

Install the MongoDB exporter

We recommend that you install the MongoDB exporter, mongodb_exporter, by using the following config:

# Copyright 2023 Google LLC
#
# Licensed under the Apache License, Version 2.0 (the "License");
# you may not use this file except in compliance with the License.
# You may obtain a copy of the License at
#
#     https://www.apache.org/licenses/LICENSE-2.0
#
# Unless required by applicable law or agreed to in writing, software
# distributed under the License is distributed on an "AS IS" BASIS,
# WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
# See the License for the specific language governing permissions and
# limitations under the License.

apiVersion: apps/v1
kind: Deployment
metadata:
  name: mongodb-exporter
  labels:
    app.kubernetes.io/name: mongodb-exporter
spec:
  replicas: 1
  selector:
    matchLabels:
      app.kubernetes.io/name: mongodb-exporter
  template:
    metadata:
      labels:
        app.kubernetes.io/name: mongodb-exporter
    spec:
      containers:
      - name: exporter
        image: percona/mongodb_exporter:0.39
        args:
        - --mongodb.uri=mongodb://user:password@mongodb-service-name:27017
        - --collect-all
        ports:
        - name: prometheus
          containerPort: 9216
          protocol: TCP

The flag --collect-all is specified in the example and there are other flags available to tune metric collection.

To apply configuration changes from a local file, run the following command:

kubectl apply -n NAMESPACE_NAME -f FILE_NAME

You can also use Terraform to manage your configurations.

Define a PodMonitoring resource

For target discovery, the Managed Service for Prometheus Operator requires a PodMonitoring resource that corresponds to MongoDB in the same namespace.

You can use the following PodMonitoring configuration:

# Copyright 2023 Google LLC
#
# Licensed under the Apache License, Version 2.0 (the "License");
# you may not use this file except in compliance with the License.
# You may obtain a copy of the License at
#
#     https://www.apache.org/licenses/LICENSE-2.0
#
# Unless required by applicable law or agreed to in writing, software
# distributed under the License is distributed on an "AS IS" BASIS,
# WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
# See the License for the specific language governing permissions and
# limitations under the License.

apiVersion: monitoring.googleapis.com/v1
kind: PodMonitoring
metadata:
  name: mongodb
  labels:
    app.kubernetes.io/name: mongodb
    app.kubernetes.io/part-of: google-cloud-managed-prometheus
spec:
  endpoints:
  - port: prometheus
    scheme: http
    interval: 30s
    path: /metrics
  selector:
    matchLabels:
      app.kubernetes.io/name: mongodb-exporter

To apply configuration changes from a local file, run the following command:

kubectl apply -n NAMESPACE_NAME -f FILE_NAME

You can also use Terraform to manage your configurations.

Define rules and alerts

You can use the following Rules configuration to define alerts on your MongoDB metrics:

# Copyright 2023 Google LLC
#
# Licensed under the Apache License, Version 2.0 (the "License");
# you may not use this file except in compliance with the License.
# You may obtain a copy of the License at
#
#     https://www.apache.org/licenses/LICENSE-2.0
#
# Unless required by applicable law or agreed to in writing, software
# distributed under the License is distributed on an "AS IS" BASIS,
# WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
# See the License for the specific language governing permissions and
# limitations under the License.

apiVersion: monitoring.googleapis.com/v1
kind: Rules
metadata:
  name: mongodb-rules
  labels:
    app.kubernetes.io/component: rules
    app.kubernetes.io/name: mongodb-rules
    app.kubernetes.io/part-of: google-cloud-managed-prometheus
spec:
  groups:
  - name: mongodb
    interval: 30s
    rules:
    - alert: MongoDBConnectionUtilizationNearMax
      annotations:
        description: |-
          MongoDB connection utilization near max
            VALUE = {{ $value }}
            LABELS: {{ $labels }}
        summary: MongoDB connection utilization near max (instance {{ $labels.instance }})
      expr: mongodb_sys_netstat_Tcp_CurrEstab >= 50000
      for: 5m
      labels:
        severity: warning
    - alert: MongoDBDown
      annotations:
        description: |-
          MongoDB is down
            VALUE = {{ $value }}
            LABELS: {{ $labels }}
        summary: MongoDB is down (instance {{ $labels.instance }})
      expr: mongodb_up < 1
      for: 5m
      labels:
        severity: critical

To apply configuration changes from a local file, run the following command:

kubectl apply -n NAMESPACE_NAME -f FILE_NAME

You can also use Terraform to manage your configurations.

For more information about applying rules to your cluster, see Managed rule evaluation and alerting.

Verify the configuration

You can use Metrics Explorer to verify that you correctly configured MongoDB. It might take one or two minutes for Cloud Monitoring to ingest your metrics.

To verify the metrics are ingested, do the following:

1. In the Google Cloud console, go to the leaderboard Metrics explorer page:

   Go to Metrics explorer

   If you use the search bar to find this page, then select the result whose subheading is Monitoring.

2. In the toolbar of the query-builder pane, select the button whose name is code PromQL.
3. Enter and run the following query:
   

   up{job="mongodb", cluster="CLUSTER_NAME", namespace="NAMESPACE_NAME"}

View dashboards

The Cloud Monitoring integration includes the MongoDB Prometheus Overview dashboard. Dashboards are automatically installed when you configure the integration. You can also view static previews of dashboards without installing the integration.

To view an installed dashboard, do the following:

1. In the Google Cloud console, go to the dashboard Dashboards page:

   Go to Dashboards

   If you use the search bar to find this page, then select the result whose subheading is Monitoring.

2. Select the Dashboard List tab.
3. Choose the Integrations category.
4. Click the name of the dashboard, for example, MongoDB Prometheus Overview.

To view a static preview of the dashboard, do the following:

1. In the Google Cloud console, go to the [integrations-icon.png] Integrations page:

   Go to Integrations

   If you use the search bar to find this page, then select the result whose subheading is Monitoring.

2. Click the Kubernetes Engine deployment-platform filter.
3. Locate the MongoDB integration and click View Details.
4. Select the Dashboards tab.

Troubleshooting

For information about troubleshooting metric ingestion problems, see Problems with collection from exporters in Troubleshooting ingestion-side problems.