Configure the Slow Query Threshold — MongoDB Cloud Manager
Configure the Slow Query Threshold¶
The Performance Advisor recognizes a query as slow if it takes longer
to execute than the value of
slowOpThresholdMs.
By default, this value is
100
milliseconds. You can change the
threshold with either the
profile
command or the db.setProfilingLevel()
mongosh
method.
Example
The following
profile
command example sets the threshold at 200
milliseconds:
If you are running MongoDB 3.6 or later, you can customize the
percentage of slow queries in your logs used by the Performance Advisor
by specifying the
sampleRate
parameter.
Example
This sets the slow query threshold to a lower value of 100
milliseconds but also sets the sample rate to 10%.
By default, the value of
profile
is
0
. MongoDB recommends
leaving this value unchanged since other values can negatively
impact database performance. To learn more, see the
profile command.
Manage the MongoDB Agent Functions — MongoDB Cloud Manager
Manage the MongoDB Agent Functions¶
On this page
Manage Backup Function
Activate Backup
Deactivate Backup
Manage Monitoring Function
Activate Monitoring
Deactivate Monitoring
Manage Automation Function
Activate Automation
Manage Backup Function¶
Activate Backup¶
From your
Context
menu, click the project that has the
hosts you want to configure.
Click
Deployments
.
Click
Servers
.
On the host where you want to activate Backup, click
ellipsis icon
.
Click
Activate Backup
.
From the banner, click
Review & Deploy
.
If you want to activate Backup, click
Confirm & Deploy
.
Otherwise click
Cancel
, then
Discard Changes
to cancel activating Backup.
Note
Only one host can backup a deployment at a time. On the
Server
tab, the host that is backing up the deployment displays
Backup - active
. Any other host with Backup
activated displays
Backup - standby
.
Deactivate Backup¶
From your
Context
menu, click the project that has the
hosts you want to configure.
Click
Deployments
.
Click
Servers
.
On the host where you want to deactivate Backup, click
ellipsis icon
.
Click
Deactivate Backup
.
From the banner, click
Review & Deploy
.
If you want to activate Backup, click
Confirm & Deploy
.
Otherwise click
Cancel
, then
Discard Changes
to cancel deactivating Backup.
Manage Monitoring Function¶
Activate Monitoring¶
From your
Context
menu, click the project that has the
hosts you want to configure.
Click
Deployments
.
Click
Servers
.
On the host where you want to activate Monitoring, click
ellipsis icon
.
Click
Activate Monitoring
.
From the banner, click
Review & Deploy
.
If you want to activate Monitoring, click
Confirm & Deploy
.
Otherwise click
Cancel
, then
Discard Changes
to cancel activating Monitoring.
Note
Only one host can monitor a deployment at a time. On the
Server
tab, the host that is monitoring the deployment displays
Monitoring - active
. Any other host with Monitoring
activated displays
Monitoring - standby
.
Multiple Monitoring Agents
You can
activate Monitoring
on multiple MongoDB Agents to distribute monitoring assignments and
provide failover. Cloud Manager distributes monitoring assignments among up
to 100 running MongoDB Agents. Each MongoDB Agent running active
Monitoring monitors a different set of MongoDB processes. One
MongoDB Agent running active Monitoring per project is the primary
Monitor. The primary Monitor reports the cluster’s status to Cloud Manager.
As MongoDB Agents have Monitoring enabled or disabled, Cloud Manager
redistributes assignments. If the primary Monitor fails, Cloud Manager
assigns another MongoDB Agent running active Monitoring to be the
primary Monitor.
If you run more than 100 MongoDB Agents with active Monitoring, the
additional MongoDB Agents run as standby MongoDB Agents. A standby
MongoDB Agent is idle, except to log its status as a standby and
periodically ask Cloud Manager if it should begin monitoring.
If you install multiple Monitoring Agents, ensure that
all
the
MongoDB Agents with active Monitoring can reach all the
mongod
processes in the deployment.
To activate Monitoring on multiple MongoDB Agents, repeat the
activation process
on multiple
MongoDB Agents.
Deactivate Monitoring¶
From your
Context
menu, click the project that has the
hosts you want to configure.
Click
Deployments
.
Click
Servers
.
On the host where you want to deactivate Monitoring, click
ellipsis icon
.
Click
Deactivate Monitoring
.
From the banner, click
Review & Deploy
.
If you want to deactivate Monitoring, click
Confirm & Deploy
.
Otherwise click
Cancel
, then
Discard Changes
to cancel activating Monitoring.
Manage Automation Function¶
Activate Automation¶
Automation is activated when you:
Deploy a
standalone MongoDB instance
Deploy a
replica set
Deploy a
sharded cluster
Import an existing MongoDB deployment
into Cloud Manager.
We recommend that you rotate the automation user’s password
periodically. Cloud Manager provides an automated procedure for password
rotation with no downtime.
Prerequisites¶
To enable password rotation for the automation user, you must meet the
following requirement:
SCRAM-SHA-1 or SCRAM-SHA-256 set up as a supported authentication
mechanism for the Automation.
Procedure¶
1
Navigate to the
MongoDB Users
tab for your deployment.¶
If it is not already displayed, select the organization that
contains your desired project from the
office icon
Organizations
menu in the
navigation bar.
If it is not already displayed, select your desired project
from the
Projects
menu in the navigation bar.
If it is not already displayed, click
Deployment
in
the sidebar.
Click the
Security
tab.
Click
MongoDB Users
.
2
On the line for the automation user, click
Rotate Password
.¶
3
Click
Review & Deploy
to review your changes.¶
4
Click
Confirm & Deploy
to deploy your changes.¶
Otherwise, click
Cancel
and you can make
additional changes.
The
Data Explorer
provides an
aggregation pipeline builder
to process your data. Aggregation pipelines transform your documents
into aggregated results based on selected
pipeline stages.
The MongoDB Atlas aggregation pipeline builder is primarily designed for
building pipelines, rather than executing them. The pipeline builder
provides an easy way to
export your pipeline
to execute in a driver.
To interact with data in the Cloud Manager UI:
Click
Deployment
in the left navigation.
Select the desired MongoDB deployment.
Select the
Data
tab.
Required Roles¶
To create and execute aggregation pipelines in the
Data Explorer
, you must have been granted at least the
Project
Data
Access
Read
Only
role.
To utilize the
$out
stage in your pipeline, you must
have been granted at least the
Project
Data
Access
Read/Write
role.
Access the Aggregation Pipeline Builder¶
1
Select the database for the collection.¶
The main panel and
Namespaces
on the left side list the
collections in the database.
click to enlarge
2
Select the collection on the left-hand side or in the main panel.¶
The main panel displays the
Find
,
Indexes
,
and
Aggregation
views.
3
Select the
Aggregation
view.¶
When you first open the
Aggregation
view, the
Data Explorer
displays an empty aggregation pipeline.
click to enlarge
Create an Aggregation Pipeline¶
1
Select an aggregation stage.¶
Select an aggregation stage from the
Select
dropdown in
the bottom-left panel.
click to enlarge
The toggle to the right of the dropdown dictates whether the
stage is enabled.
2
Fill in your aggregation stage.¶
Fill in your stage with the appropriate values. If
Comment Mode
is enabled, the pipeline
builder provides syntactic guidelines for your selected stage.
As you modify your stage, the
Data Explorer
updates the
preview documents on the right based on the results of the current
stage.
click to enlarge
3
Add additional stages to your pipeline as desired.¶
There are two ways to add additional stages to your pipeline:
Click the
Add Stage
button at the bottom of the pipeline
to add a new stage at the end of your pipeline:
Click the
plus icon
button on a stage to add a new stage
directly after the stage where the button was clicked.
To delete a pipeline stage, click the
trash icon
icon
on the desired stage.
4
Repeat steps 1 and 2 for each additional stage.¶
Collation¶
Use collation to specify
language-specific rules for string comparison, such as rules for lettercase and accent marks.
To specify a collation document, click
Collation
at
the top of the pipeline builder.
The
locale
field is mandatory; all other collation fields are
optional. For descriptions of the fields, see
Collation Document.
Import an Aggregation Pipeline from Text¶
You can import aggregation pipelines from plain text into the
pipeline builder to easily modify and verify your pipelines.
To import a pipeline from plain text:
1
Open the
New Pipeline from Text
dialog.¶
Click the arrow next to the plus icon at the top of the
pipeline builder.
Click
New Pipeline from Text
.
click to enlarge
2
Type or paste your pipeline in the dialog.¶
Your pipeline must match the syntax of the
pipeline
parameter of
the
db.collection.aggregate()
method.
3
Click
Create New
.¶
4
Click
Confirm
in the ensuing dialog.¶
Reset Your Pipeline¶
To return your pipeline to the initial blank state, click the plus icon
at the top of the pipeline builder.
Export an Aggregation Pipeline to Driver Language¶
You can use the aggregation pipeline builder to export your finished
pipeline to one of the supported driver languages; Java,
Node, C#, and Python 3. Use this feature to format and export pipelines
for use in your applications.
To export your aggregation pipeline:
1
Construct an aggregation pipeline.¶
For instructions on creating an aggregation pipeline, see
Create an Aggregation Pipeline
.
2
Click
Export to Language
at the top of the pipeline builder.¶
3
Select your desired export language.¶
In the
Export Pipeline To
dropdown, select your desired
language.
The
My Pipeline
pane on the left displays your
pipeline in
mongosh
syntax.
The pane on the right displays your pipeline in the selected
language.
4
Include import statements, if desired.¶
(Optional)
: Check the
Include Import Statements
option
to include the required import statements for the language selected.
5
Click the
Copy
button.¶
Click the
Copy
button at the top-right of the pipeline
to copy the pipeline for the selected language to your clipboard.
You can now integrate your pipeline into your application.
6
Click
Close
to return to the aggregation pipeline builder.¶
Aggregation Pipeline Settings¶
To modify the aggregation pipeline builder settings:
1
Click the
settings icon
icon at the top-right of the pipeline builder.¶
2
Modify pipeline settings as desired.¶
You can modify the following settings:
Setting
Description
Default
Comment Mode
When enabled, the
Data Explorer
adds helper
comments to each stage.
Note
Changing this setting only affects new stages and does not
modify stages which have already been added to your pipeline.
On
Number of Preview Documents
Number of documents to show in the preview for each stage.
The unique identifier for the
organization
whose information you want
to retrieve.
Request Query Parameters¶
The following query parameters are optional:
Name
Type
Description
Default
pageNum
integer
Page number (1-based).
1
itemsPerPage
integer
Number of items to return per page, up to a maximum of 500.
100
pretty
boolean
Displays response in a prettyprint format.
false
envelope
boolean
Specifies whether or not to wrap the response in an
envelope
.
false
name
string
Human-readable label of the project to use to filter the returned
list. Performs a case-insensitive search for a project, which is
prefixed by the specified
name
, within the organization.
Example
If you specify a
name
query parameter of
project1
,
Cloud Manager returns the project named
project1
, but would
not return a project named
project123
.
None
Request Body Parameters¶
This endpoint doesn’t use HTTP request body parameters.
Response¶
Response Document¶
The response
JSON
document includes an array of
result
objects, an array of
link
objects and a count of the total
number of
result
objects retrieved.
Name
Type
Description
results
array
Array includes one object for each item detailed in the
results Embedded Document section.
links
array
Array includes one or more links to sub-resources
and/or related resources. The relations between
URL
s are
explained in the
Web Linking Specification
.
totalCount
number
Integer count of the total number of items in the result set. It
may be greater than the number of objects in the
results
array if the entire result set is paginated.
results
Embedded Document¶
Each
result
is one project.
Name
Type
Description
activeAgentCount
integer
The number of active monitoring, automation, and Backups
in the project.
hostCounts
Document
Describes the host types and number of each host type
for the cluster.
hostCounts.arbiter
integer
The number of
arbiter
hosts in the cluster.
hostCounts.config
integer
The number of sharded cluster configuration server hosts in
the cluster.
hostCounts.master
integer
The number of
master
hosts in the cluster.
hostCounts.mongos
integer
The number of
mongos
hosts in the
cluster.
hostCounts.primary
integer
The number of
primary
hosts in the cluster.
hostCounts.secondary
integer
The number of
secondary
hosts in the cluster.
hostCounts.slave
integer
The number of
slave
hosts in the cluster.
id
string
The unique identifier for the project.
links
object array
One or more links to sub-resources and/or related resources. All
links
arrays in responses include at least one link called
self
. The relationships between
URL
s are explained in the
Web Linking Specification
.
name
string
The name of the cluster.
orgId
string
The unique identifier for the parent organization of the project.