MongoDB Atlas receiver 🔗

The MongoDB Atlas receiver allows the Splunk Distribution of OpenTelemetry Collector to collect metrics from MongoDB Atlas through its monitoring API. The supported pipeline types are metrics and logs. See Configure pipelines for more information.

Database metrics are dimensionalized by project and database attributes, for example, project_name and database_name.

Note

Use the MongoDB Atlas receiver in place of the SignalFx Smart Agent mongodb-atlas monitor type.

Get started 🔗

Follow these steps to configure and activate the component:

Deploy the Splunk Distribution of OpenTelemetry Collector to your host or container platform:
Configure the MongoDB Atlas receiver as described in the next section.
Restart the Collector.

Sample configurations 🔗

To activate the MongoDB Atlas receiver, add mongodbatlas to the receivers section of your configuration file, as shown in the following example:

# In this example, both values are pulled from the environment.

receivers:
  mongodbatlas:
    public_key: ${MONGODB_ATLAS_PUBLIC_KEY}
    # You can obtain the public key from the API Keys tab of the MongoDB Atlas Project Access Manager.
    # This value is required.
    private_key: ${MONGODB_ATLAS_PRIVATE_KEY}
    # You can obtain the private key from the API Keys tab of the MongoDB Atlas Project Access Manager.
    # This value is required.

The following example shows how to collect logs:

receivers:
    mongodbatlas:
     logs:
       enabled: true
       projects:
         - name: "Your MongoDB project"
           collect_audit_logs: true
           collect_host_logs: true

To complete the configuration, include the receiver in the metrics or logs pipelines of the service section of your configuration file. For example:

service:
  pipelines:
    metrics:
      receivers: [mongodbatlas]
   logs:
      receivers: [mongodbatlas]

Settings 🔗

The following table shows the configuration options for the MongoDB Atlas:

Metrics 🔗

The following metrics, resource attributes, and attributes are available.

Activate or deactivate specific metrics 🔗

You can activate or deactivate specific metrics by setting the enabled field in the metrics section for each metric. For example:

receivers:
  samplereceiver:
    metrics:
      metric-one:
        enabled: true
      metric-two:
        enabled: false

The following is an example of host metrics receiver configuration with activated metrics:

receivers:
  hostmetrics:
    scrapers:
      process:
        metrics:
          process.cpu.utilization:
            enabled: true

Note

Deactivated metrics aren’t sent to Splunk Observability Cloud.

Troubleshooting 🔗

If you are a Splunk Observability Cloud customer and are not able to see your data in Splunk Observability Cloud, you can get help in the following ways.

Available to Splunk Observability Cloud customers 🔗

Submit a case in the Splunk Support Portal.
Call Splunk Customer Support.

Available to customers and free trial users 🔗

Ask a question and get answers through community support at Splunk Answers.
Join the Splunk #observability user group Slack channel to communicate with customers, partners, and Splunk employees worldwide. To join, see Chat groups in the Get Started with Splunk Community manual.

To learn about even more support options, see Splunk Customer Success.

Related Topics