MongoDB Atlas 🔗
Description 🔗
The MongoDB Atlas receiver fetches metrics from MongoDB Atlas by using their monitoring APIs. Database metrics are dimensionalized by project and database attributes, for example, project_name
and database_name
.
Use the MongoDB Atlas receiver in place of the SignalFx Smart Agent mongodb-atlas
cluster monitor, since the Smart Agent is now deprecated. For details, see the deprecation notice.
The supported pipeline type is metrics.
Benefits 🔗
After you configure the integration, you can access these features:
View metrics using the built-in dashboard. For information about dashboards, see View dashboards in Observability Cloud.
View a data-driven visualization of the physical servers, virtual machines, AWS instances, and other resources in your environment that are visible to Infrastructure Monitoring. For information about navigators, see Splunk Infrastructure Monitoring navigators.
Access Metric Finder and search for metrics sent by the monitor. For information about Metric Finder, see Use the Metric Finder.
Installation 🔗
Follow these steps to deploy this integration:
Follow the steps to deploy the Splunk Distribution of OpenTelemetry Collector to your host or container platform:
Configure the receiver, as described in the Configuration section.
Restart the Splunk Distribution of OpenTelemetry Collector.
Configuration 🔗
Include the MongoDB Atlas receiver in the receivers
section of your configuration file, as shown in the following example:
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.
In this example, both values are pulled from the environment.
To complete the integration, include the receiver in theservice/pipelines/metrics/receivers
section of your configuration file. For example:
service:
pipelines:
metrics:
receivers: [mongodbatlas]
Configuration options 🔗
The following table shows the configuration options:
Option |
Description |
Required |
---|---|---|
|
The public key acts as the username when making API requests. You can obtain the public key from the API Keys tab of the MongoDB Atlas Project Access Manager. |
Yes |
|
The private key acts as the password when making API requests. You can obtain the private key from the API Keys tab of the MongoDB Atlas Project Access Manager. |
Yes |
|
The duration that specifies the interval between measurement data points. The default value is |
No |
|
See the options described below. |
No |
|
The default value is |
No |
|
The default value is |
No |
|
The default value is |
No |
|
The default value is |
No |
Metrics 🔗
These are the metrics available for this integration. All metrics are emitted by default.
To disable any metric, apply the following configuration:
metrics:
<metric_name>:
enabled: false
Name |
Category |
Description |
Unit |
Type |
Attributes |
---|---|---|---|---|---|
mongodbatlas.db.counts |
Default |
Database feature size aggregate of MongoDB metrics |
|
Gauge (Double) |
|
mongodbatlas.db.size |
Default |
Database feature size aggregate of MongoDB metrics |
|
Gauge (Double) |
|
mongodbatlas.disk.partition.IOPS.average |
Default |
Disk partition IOPS aggregate of MongoDB metrics |
|
Gauge (Double) |
|
mongodbatlas.disk.partition.IOPS.max |
Default |
Disk partition IOPS aggregate of MongoDB metrics |
|
Gauge (Double) |
|
mongodbatlas.disk.partition.latency.average |
Default |
Disk partition latency aggregate of MongoDB metrics |
|
Gauge (Double) |
|
mongodbatlas.disk.partition.latency.max |
Default |
Disk partition latency aggregate of MongoDB metrics |
|
Gauge (Double) |
|
mongodbatlas.disk.partition.space.average |
Default |
Disk partition space aggregate of MongoDB metrics |
|
Gauge (Double) |
|
mongodbatlas.disk.partition.space.max |
Default |
Disk partition space aggregate of MongoDB metrics |
|
Gauge (Double) |
|
mongodbatlas.disk.partition.usage.average |
Default |
Disk partition usage (%) aggregate of MongoDB metrics |
|
Gauge (Double) |
|
mongodbatlas.disk.partition.usage.max |
Default |
Disk partition usage (%) aggregate of MongoDB metrics |
|
Gauge (Double) |
|
mongodbatlas.disk.partition.utilization.average |
Default |
Disk partition utilization (%) MongoDB metrics |
1 |
Gauge (Double) |
|
mongodbatlas.disk.partition.utilization.max |
Default |
Disk partition utilization (%) MongoDB metrics |
|
Gauge (Double) |
|
mongodbatlas.process.asserts |
Default |
Number of assertions per second aggregate of MongoDB metrics |
|
Gauge (Double) |
|
mongodbatlas.process.background_flush |
Default |
Amount of data flushed in the background MongoDB Metric |
|
Gauge (Double) |
|
mongodbatlas.process.cache.io |
Default |
Cache throughput (per second) aggregate of MongoDB metrics |
|
Gauge (Double) |
|
mongodbatlas.process.cache.size |
Default |
Cache sizes aggregate of MongoDB metrics |
|
Sum(Double) |
|
mongodbatlas.process.connections |
Default |
Number of current connections MongoDB metric |
|
Sum(Double) |
|
mongodbatlas.process.cpu.children.normalized.usage.average |
Default |
CPU usage for child processes, normalized to pct aggregate of MongoDB metrics |
|
Gauge (Double) |
|
mongodbatlas.process.cpu.children.normalized.usage.max |
Default |
CPU usage for child processes, normalized to pct aggregate of MongoDB metrics |
|
Gauge (Double) |
|
mongodbatlas.process.cpu.children.usage.average |
Default |
CPU usage for child processes (%) aggregate of MongoDB metrics |
|
Gauge (Double) |
|
mongodbatlas.process.cpu.children.usage.max |
Default |
CPU usage for child processes (%) aggregate of MongoDB metrics |
|
Gauge (Double) |
|
mongodbatlas.process.cpu.normalized.usage.average |
Default |
CPU usage, normalized to pct aggregate of MongoDB metrics |
|
Gauge (Double) |
|
mongodbatlas.process.cpu.normalized.usage.max |
Default |
CPU usage, normalized to pct aggregate of MongoDB metrics |
|
Gauge (Double) |
|
mongodbatlas.process.cpu.usage.average |
Default |
CPU usage (%) aggregate of MongoDB metrics |
|
Gauge (Double) |
|
mongodbatlas.process.cpu.usage.max |
Default |
CPU usage (%) aggregate of MongoDB metrics |
|
Gauge (Double) |
|
mongodbatlas.process.cursors |
Default |
Number of cursors aggregate of MongoDB metrics ``CURSORS_TOTAL_OPEN, CURSORS_TOTAL_TIMED_OUT |
|
Gauge (Double) |
|
mongodbatlas.process.db.document.rate |
Default |
Document access rates aggregate of MongoDB metrics |
|
Gauge (Double) |
|
mongodbatlas.process.db.operations.rate |
Default |
DB operation rates aggregate of MongoDB metrics |
|
Gauge (Double) |
|
mongodbatlas.process.db.operations.time |
Default |
DB operation times aggregate of MongoDB metrics |
|
Sum (Double) |
|
mongodbatlas.process.db.query_executor.scanned |
Default |
Scanned objects aggregate of MongoDB metrics |
|
Gauge (Double) |
|
mongodbatlas.process.db.query_targeting.scanned_per_returned |
Default |
Scanned objects per returned aggregate of MongoDB metrics |
|
Gauge (Double) |
|
mongodbatlas.process.db.storage |
Default |
Storage used by the database aggregate of MongoDB metrics |
|
Gauge (Double) |
|
mongodbatlas.process.fts.cpu.usage |
Default |
Full text search CPU (%) aggregate of MongoDB metrics |
|
Gauge (Double) |
|
mongodbatlas.process.global_lock |
Default |
Number and status of locks aggregate of MongoDB metrics |
|
Gauge (Double) |
|
mongodbatlas.process.index.btree_miss_ratio |
Default |
Index miss ratio (%) MongoDB metric |
|
Gauge (Double) |
|
mongodbatlas.process.index.counters |
Default |
Indexes aggregate of MongoDB metrics |
|
Gauge (Double) |
|
mongodbatlas.process.journaling.commits |
Default |
Journaling commits MongoDB metric |
|
Gauge (Double) |
|
mongodbatlas.process.journaling.data_files |
Default |
Data file sizes MongoDB metric |
|
Gauge (Double) |
|
mongodbatlas.process.journaling.written |
Default |
Journals written MongoDB metric |
|
Gauge (Double) |
|
mongodbatlas.process.memory.usage |
Default |
Memory usage aggregate of MongoDB metrics |
|
Gauge (Double) |
|
mongodbatlas.process.network.io |
Default |
Network IO aggregate of MongoDB metrics |
|
Gauge (Double) |
|
mongodbatlas.process.network.requests |
Default |
Network requests MongoDB metric |
|
Sum(Double) |
|
mongodbatlas.process.oplog.rate |
Default |
Execution rate by operation MongoDB metric |
|
Gauge (Double) |
|
mongodbatlas.process.oplog.time |
Default |
Execution time by operation aggregate of MongoDB metrics |
|
Gauge (Double) |
|
mongodbatlas.process.page_faults |
Default |
Page faults aggregate of MongoDB metrics |
|
Gauge (Double) |
|
mongodbatlas.process.restarts |
Default |
Restarts in last hour aggregate of MongoDB metrics |
|
Gauge (Double) |
|
mongodbatlas.process.tickets |
Default |
Tickets aggregate of MongoDB metrics |
|
Gauge (Double) |
|
mongodbatlas.system.cpu.normalized.usage.average |
Default |
System CPU normalized to pct aggregate of MongoDB metrics |
|
Gauge (Double) |
|
mongodbatlas.system.cpu.normalized.usage.max |
Default |
System CPU normalized to pct aggregate of MongoDB metrics |
|
Gauge (Double) |
|
mongodbatlas.system.cpu.usage.average |
Default |
System CPU usage (%) aggregate of MongoDB metrics |
|
Gauge (Double) |
|
mongodbatlas.system.cpu.usage.max |
Default |
System CPU usage (%) aggregate of MongoDB metrics |
|
Gauge (Double) |
|
mongodbatlas.system.fts.cpu.normalized.usage |
Default |
Full text search disk usage (%) aggregate of MongoDB metrics |
|
Gauge (Double) |
|
mongodbatlas.system.fts.cpu.usage |
Default |
Full-text search (%) |
|
Gauge (Double) |
|
mongodbatlas.system.fts.disk.used |
Default |
Full text search disk usage MongoDB metric |
|
Gauge (Double) |
|
mongodbatlas.system.fts.memory.usage |
Default |
Full-text search aggregate of MongoDB metrics |
|
Sum (Double) |
|
mongodbatlas.system.memory.usage.average |
Default |
System memory usage aggregate of MongoDB metrics |
|
Gauge (Double) |
|
mongodbatlas.system.memory.usage.max |
Default |
System memory usage aggregate of MongoDB metrics |
|
Gauge (Double) |
|
mongodbatlas.system.network.io.average |
Default |
System Network IO aggregate of MongoDB metrics |
|
Gauge (Double) |
|
mongodbatlas.system.network.io.max |
Default |
System Network IO aggregate of MongoDB metrics |
|
Gauge (Double) |
|
mongodbatlas.system.paging.io.average |
Default |
Swap IO aggregate of MongoDB metrics |
|
Gauge (Double) |
|
mongodbatlas.system.paging.io.max |
Default |
Swap IO aggregate of MongoDB metrics |
|
Gauge (Double) |
|
mongodbatlas.system.paging.usage.average |
Default |
Swap usage aggregate of MongoDB metrics |
|
Gauge (Double) |
|
mongodbatlas.system.paging.usage.max |
Default |
Swap usage aggregate of MongoDB metrics |
|
Gauge (Double) |
|
Metric attributes 🔗
The following table lists the attributes for each metric:
Name |
Description |
---|---|
|
MongoDB assertion type |
|
Database index effectiveness |
|
Whether read into or written from |
|
Cache status |
|
Whether process is acting as replica or primary |
|
CPU state |
|
Whether cursor is open or timed out |
|
Network traffic direction |
|
Measurement type for disk operation |
|
Disk measurement type |
|
Status of documents in the database |
|
Type of command |
|
Which queue is locked |
|
Type of memory issue encountered |
|
Memory usage type |
|
MongoDB object type |
|
Type of database operation |
|
Oplog type |
|
Objects or indexes scanned during query |
|
Views on database size |
|
Type of ticket available |
Get help 🔗
If you are not able to see your data in Splunk Observability Cloud, try these tips:
Submit a case in the Splunk Support Portal
Available to Splunk Observability Cloud customers
-
Available to Splunk Observability Cloud customers
Ask a question and get answers through community support at Splunk Answers
Available to Splunk Observability Cloud customers and free trial users
Join the Splunk #observability user group Slack channel to communicate with customers, partners, and Splunk employees worldwide
Available to Splunk Observability Cloud customers and free trial users
To learn how to join, see Get Started with Splunk Community - Chat groups
To learn about even more support options, see Splunk Customer Success.