MongoDB Agent Reference · MongoDB 2.x Lock Details Use the MongoDB 2.x Lock Details page to know the following details: v The table view that pr ovides information about the database

Monitoring Agent for MongoDBVersion 08.19.03.00

Reference

IBM

Monitoring Agent for MongoDBVersion 08.19.03.00

Reference

IBM

NoteBefore using this information and the product it supports, read the information in “Notices” on page 77.

This edition applies to version 08.19.03.00 of the Monitoring Agent for MongoDB and to all subsequent releases andmodifications until otherwise indicated in new editions.

© Copyright IBM Corporation 2014, 2019.US Government Users Restricted Rights – Use, duplication or disclosure restricted by GSA ADP Schedule Contractwith IBM Corp.

Contents

Chapter 1. Monitoring Agent forMongoDB . . . . . . . . . . . . . . 1

Chapter 2. Dashboards . . . . . . . . 3Default dashboards . . . . . . . . . . . . 3Widgets for the Default dashboards. . . . . . . 4Custom views . . . . . . . . . . . . . 21

Chapter 3. Thresholds . . . . . . . . 23Predefined thresholds . . . . . . . . . . . 23Customized thresholds . . . . . . . . . . 25

Chapter 4. Attributes . . . . . . . . . 27Data sets for the monitoring agent. . . . . . . 28Attribute descriptions . . . . . . . . . . . 29

Collection Storage data set . . . . . . . . 29Database Names data set . . . . . . . . . 31General Shard Information data set . . . . . 32Global Status data set . . . . . . . . . . 34Locks data set . . . . . . . . . . . . 34MII Copy for APM UI One data set . . . . . 35MII Copy for APM UI Two data set . . . . . 38

MMAPv1 Details data set . . . . . . . . 41Mongo Inst DB Lock data set . . . . . . . 44Mongo Inst IO Info data set . . . . . . . . 46Mongo Instance Information data set . . . . . 53Mongod Listing data set . . . . . . . . . 56MongoDB Locks data set . . . . . . . . . 59Performance Object Status data set . . . . . 62Response Times data set . . . . . . . . . 65Router Location data set . . . . . . . . . 66RT Copy for APM UI data set . . . . . . . 67Take Action Status data set . . . . . . . . 68Thread Pool Status data set . . . . . . . . 69WiredTiger Details data set . . . . . . . . 71

Accessibility features . . . . . . . . 75

Notices . . . . . . . . . . . . . . 77Trademarks . . . . . . . . . . . . . . 79Terms and conditions for product documentation. . 79IBM Online Privacy Statement . . . . . . . . 80

Index . . . . . . . . . . . . . . . 81

© Copyright IBM Corp. 2014, 2019 iii

iv MongoDB Agent Reference

Chapter 1. Monitoring Agent for MongoDB

The Monitoring Agent for MongoDB offers a central point of management for your MongoDBenvironment or application.

The software provides a comprehensive means for gathering the information that is required to detectproblems early and to prevent them. Information is standardized across the system. You can monitormultiple servers from a single console. By using the MongoDB Agent you can easily collect and analyzeMongoDB specific information.

Installing and configuring the agent

Install the monitoring agent on the system where the application that you want to monitor is located.

For more information, see the following documentation in IBM Knowledge Center:v IBM Cloud Application Performance Managementv IBM Cloud Application Performance Management, Private

© Copyright IBM Corp. 2014, 2019 1

http://www.ibm.com/support/knowledgecenter/SSMKFH

http://www.ibm.com/support/knowledgecenter/SSHLNR

2 MongoDB Agent Reference

Chapter 2. Dashboards

Open the Application Performance Dashboard in the Cloud APM console to see a status summary of allyour applications. As you drill down to dashboards for specific applications and their supportingelements, more details are available about the selected item.

Use the MongoDB Agent dashboards to proactively monitor your MongoDB deployment. Each dashboardpage contains views with key performance indicators.

When an application that includes MongoDB managed resources is selected, the navigator and the StatusOverview tab show MongoDB in the Components group:v Click Components to see a single MongoDB group widget that is displayed along with a group widget

for every other data source type in the application.v Click the MongoDB subgroup to see a group widget for each managed resource in the application.v Click inside a MongoDB group widget or click a MongoDB managed resource from the navigator

Instances section to open a dashboard with KPIs from the selected managed resource.

For more information about the KPIs, click

in the view or click

in the dashboard banner.

Default dashboardsMongoDB

The summary dashboard presents a high level status of the MongoDB system. If any KPI has acritical or warning status, click inside the group widget to drill down to a dashboard with detailsabout the MongoDB instance.

inMemory Storage Engine DetailsUse the inMemory Storage Engine Details page to know the following details:v The table view that provides details about the cache memory of the storage enginev The line charts that provide historical data (for last 4 hours) of the transaction and session

statistics, cache usage, and concurrent transactions

Input Output InformationUse the Input Output Information page to know the following details:v The table view that provides the cursor details.v The line charts that provide historical data (for last 4 hours) of the queued operations, active

connections, data flow, and data access of the selected host.

MMAPv1 Storage Engine DetailsUse the MMAPv1 Storage Engine Details page to know the following details:v The table view that provides information about the background operations of the MMAPv1

storage engine.v The line charts that provide historical data (for last 4 hours) of the last flush time, average

flush time, journaling data, and the journaling time.

MongoDB 2.x Lock DetailsUse the MongoDB 2.x Lock Details page to know the following details:v The table view that provides information about the database locks.v The line charts that provide historical data (for last 4 hours) of the database locks.

MongoDB 3.x Lock DetailsUse the MongoDB 3.x Lock Details page to know the following details:


v The table view that lists the available types of locks.v The line charts that provide historical data (for last 4 hours) of the deadlocks, lock acquisitions,

and waiting time for the selected lock type.

You can use this detail page to view details of lock version 3.x, or later.

Overall System DetailsUse the Overall System Details page to know the following details about the MongoDB system:v Status information for all the mongod processes in your system.v The number of active and available connections to each Mongo instance in the MongoDB

setup.v Details about the collection size of each database in this MongoDB instance, filtered by the

capped value.v Details about the host, such as the number of faults, the hit ratio, and the type of the storage

engine.v The 5 most active database collections that are based on the total rate of operations that are

performed.v The total lock times among collections for each database.v The top 5 mongod processes that use the most resident memory.v The top 5 mongod processes that use the most virtual memory.

Replication DetailsUse the Replication Details page to know the following details:v The table views that provide details of the replication member and the oplog.v The line charts that provide historical data (for last 4 hours) of the replication lag and the space

that is used by the oplog.

WiredTiger Storage Engine DetailsUse the WiredTiger Storage Engine Details page to know the following details:v The table view that provides details about the cache memory of the storage engine.v The line charts that provide historical data (for last 4 hours) of the transaction and session

statistics, cache usage, and concurrent transactions.

Additional group widgetsThese pop-up group widgets are displayed after you click a group widget for more details. Somegroup widgets have links to more granular information in a popup widget, described here.

Widgets for the Default dashboardsMongoDB

The summary dashboard presents a high level status of the MongoDB system. If any KPI has acritical or warning status, click inside the group widget to drill down to a dashboard with detailsabout the MongoDB instance.

The following widgets are available in this dashboard:

Global MongoDB StatusThe Global MongoDB Status group widget displays a status summary with vital statisticsfor the MongoDB instance.

The following KPIs for the widget are derived from the attributes as described:v Connections used (%): The percentage of connections that are made out of the available

connections. This data is derived from the Percentage of Connecitons attribute in theKKJ MONGO INSTANCE INFORMATION data set.

v Global MongoDB status: The value of the global status. This data is derived from theStatus attribute in the KKJ GLOBAL STATUS data set.


v Highest capped collection usage (%): The percentage of data space that is being used.The value N/A means that the data is not applicable. This data is derived from thePercentage Size attribute in the KKJ COLLECTION STORAGE data set.

v Highest resident memory used (MB): The value of the resident memory (in MB). Thisvalue is approximately equivalent to the amount of RAM that is currently being usedby the database process. This data is derived from the RAM Approx MB attribute inthe KKJ MII COPY FOR APMUI ONE data set.

v Highest virtual memory used (MB): The amount of virtual memory (in MB) that isused by the mongod process. This data is derived from the Virtual Mem MB attributein the KKJ MII COPY FOR APMUI TWO data set.

v MongoDB instances (Critical): The number of nodes that are in critical state. The criticalstate is displayed in red color. This data is derived from the Host attribute in the KKJMONGOD LISTING data set.

v MongoDB instances (Normal): The number of nodes that are in normal state. Thenormal state is displayed in green color. This data is derived from the Host attribute inthe KKJ MONGOD LISTING data set.

v MongoDB instances (Warning): The number of nodes that are in warning state. Thewarning state is displayed in yellow color. This data is derived from the Host attributein the KKJ MONGOD LISTING data set.

inMemory Storage Engine DetailsUse the inMemory Storage Engine Details page to know the following details:v The table view that provides details about the cache memory of the storage enginev The line charts that provide historical data (for last 4 hours) of the transaction and session

statistics, cache usage, and concurrent transactions


Cache Details (MB)The Cache Details (MB) group widget shows details of the cache memory, such as thecache size, number of dirty bytes, and number of bytes that are written into the cachememory.

The following KPIs for the widget are derived from the attributes as described:v Cache Size: The maximum size (in MB) of the cache. For a storage engine other than

WiredTiger or In-Memory, the value is N/A (not applicable). This data is derived fromthe Max Bytes Configured attribute in the KKJ WIREDTIGER DETAILS data set.

v Dirty Bytes: The number of dirty data bytes in the cache (in MB). For a storage engineother than WiredTiger or In-Memory, the value is N/A (not applicable). This data isderived from the Dirty Bytes attribute in the KKJ WIREDTIGER DETAILS data set.

v Read Bytes: The number of bytes that are read from the cache (in MB). For a storageengine other than WiredTiger or In-Memory, the value is N/A (not applicable). Thisdata is derived from the Read Bytes attribute in the KKJ WIREDTIGER DETAILS dataset.

v Write Bytes: The number of bytes that are written into the cache (in MB). For a storageengine other than WiredTiger or In-Memory, the value is N/A (not applicable). Thisdata is derived from the Write Bytes attribute in the KKJ WIREDTIGER DETAILS dataset.

Cache Usage (history)The Cache Usage (history) group widget shows a line chart that provides historical dataof the available and used cache memory. By default, the line chart provides the historicaldata for the period of last 4 hours. You can change this time period by using the TimeSelector widget.

The following KPIs for the widget are derived from the attributes as described:

Chapter 2. Dashboards 5

v Cache Size: The maximum size (in MB) of the cache. For a storage engine other thanWiredTiger or In-Memory, the value is N/A (not applicable). This data is derived fromthe Max Bytes Configured attribute in the KKJ WIREDTIGER DETAILS data set.

v Cache Used: The size (in MB) of the data that is currently in the cache (in MB). For astorage engine other than WiredTiger or In-Memory, the value is N/A (not applicable).This data is derived from the Bytes in Cache attribute in the KKJ WIREDTIGERDETAILS data set.

v Interval time: The local time at the agent when the data was collected. This data isderived from the Timestamp attribute in the KKJ WIREDTIGER DETAILS data set.

Concurrent Transaction Tickets (history)The Concurrent Transaction Tickets (history) group widget shows a line chart thatprovides historical data of the percentage of available concurrent read and writeoperation tickets. By default, the line chart provides the historical data for the period oflast 4 hours. You can change this time period by using the Time Selector widget.

The following KPIs for the widget are derived from the attributes as described:v Interval time: The local time at the agent when the data was collected. This data is

derived from the Timestamp attribute in the KKJ WIREDTIGER DETAILS data set.v Read Available: The percentage of the concurrent read operation tickets that are

available. For a storage engine other than WiredTiger or In-Memory, the value is N/A(not applicable). This data is derived from the Percentage Read attribute in the KKJWIREDTIGER DETAILS data set.

v Write Available: The percentage of the concurrent write operation tickets that areavailable. For a storage engine other than WiredTiger or In-Memory, the value is N/A(not applicable). This data is derived from the Percentage Write attribute in the KKJWIREDTIGER DETAILS data set.

Failed Transaction (history)The Failed Transaction (history) group widget shows a line chart that provides historicaldata of the number of transactions that failed or were rolled back. By default, the linechart provides the historical data for the period of last 4 hours. You can change this timeperiod by using the Time Selector widget.

The following KPIs for the widget are derived from the attributes as described:v Failed: A counter for the transactions that failed due to the cache overflow. For a

storage engine other than WiredTiger or In-Memory, the value is N/A (not applicable).This data is derived from the Transaction Failed attribute in the KKJ WIREDTIGERDETAILS data set.


v Rollback: A counter for the transactions that were rolled back. For a storage engineother than WiredTiger or In-Memory, the value is N/A (not applicable). This data isderived from the Transaction Rolled Back attribute in the KKJ WIREDTIGER DETAILSdata set.

Session Statistics (history)The Session Statistics (history) group widget shows a line chart that provides historicaldata of the number of open cursors and open sessions. By default, the line chart providesthe historical data for the period of last 4 hours. You can change this time period byusing the Time Selector widget.


derived from the Timestamp attribute in the KKJ WIREDTIGER DETAILS data set.


v Open Cursor: The number of open cursors. For a storage engine other than WiredTigeror In-Memory, the value is N/A (not applicable). This data is derived from the OpenCursor attribute in the KKJ WIREDTIGER DETAILS data set.

v Open Session: The number of open sessions. For a storage engine other thanWiredTiger or In-Memory, the value is N/A (not applicable). This data is derived fromthe Open Session attribute in the KKJ WIREDTIGER DETAILS data set.

v TIMESTAMP: The local time at the agent when the data was collected. This data isderived from the Timestamp attribute in the KKJ WIREDTIGER DETAILS data set.

Transaction Details (history)The Transaction Details (history) group widget shows a line chart that provides historicaldata of the number of transactions that were started, committed, rolled back, and failed.By default, the line chart provides the historical data for the period of last 4 hours. Youcan change this time period by using the Time Selector widget.

The following KPIs for the widget are derived from the attributes as described:v Committed: A counter for the transactions that were committed since the server

startup. For a storage engine other than WiredTiger or In-Memory, the value is N/A(not applicable). This data is derived from the Committed Transactions attribute in theKKJ WIREDTIGER DETAILS data set.


v Transaction Begins: A counter for the transactions that were started since the serverstartup. For a storage engine other than WiredTiger or In-Memory, the value is N/A(not applicable). This data is derived from the Transaction Begins attribute in the KKJWIREDTIGER DETAILS data set.

Input Output InformationUse the Input Output Information page to know the following details:v The table view that provides the cursor details.v The line charts that provide historical data (for last 4 hours) of the queued operations, active

connections, data flow, and data access of the selected host.


Active Connections (history)The Active Connections (history) group widget shows a line chart that provides historicaldata of the number of active connections that perform read and write operations on theselected host for each collection period. By default, the line chart provides the historicaldata for the period of last 4 hours. You can change this time period by using the TimeSelector widget.


derived from the Timestamp attribute in the KKJ MONGO INST IO INFO data set.v Read: The total number of active client connections that perform read operations. For a

router, the value N/A means that the data is not applicable. This data is derived fromthe Total Active Readers attribute in the KKJ MONGO INST IO INFO data set.

v Write: The total number of active client connections that perform write operations. Fora router, the value N/A means that the data is not applicable. This data is derivedfrom the Total Active Writers attribute in the KKJ MONGO INST IO INFO data set.

Cursor DetailsThe Cursor Details group widget displays details of the cursor, such as the number ofpinned, timed out, no timeout, single-target, and multi-target cursors.

The following KPIs for the widget are derived from the attributes as described:


v Multi Target: The total number of cursors that only target more than one shard. ForMongoDB Single Instance (Type=3), the value -1 means that the data is not applicable.This data is derived from the MultiTarget Cursor attribute in the KKJ MONGO INSTIO INFO data set.

v No Time Out: The number of open cursors with the noTimeout option set to preventtimeout after a period of inactivity. For MongoDB Single Instance (Type=3), the valueN/A means that the data is not applicable. This data is derived from the No TimeoutCursor attribute in the KKJ MONGO INST IO INFO data set.

v Pinned: The number of pinned open cursors. For MongoDB Single Instance (Type=3),the value N/A means that the data is not applicable. This data is derived from thePinned attribute in the KKJ MONGO INST IO INFO data set.

v Single Target: The total number of cursors that only target a single shard. ForMongoDB Single Instance (Type=3), the value -1 means that the data is not applicable.This data is derived from the Single Target attribute in the KKJ MONGO INST IOINFO data set.

v Timed Out: The total number of cursors that have timed out since the server processstarted. For MongoDB Single Instance (Type=3), the value -1 means that the data is notapplicable. This data is derived from the Timeout Cursor attribute in the KKJ MONGOINST IO INFO data set.

Cursor Details (history)The Cursor Details (history) group widget shows a line chart that provides historical dataof the number of open and timed out cursors. By default, the line chart provides thehistorical data for the period of last 4 hours. You can change this time period by usingthe Time Selector widget.


derived from the Timestamp attribute in the KKJ MONGO INST IO INFO data set.v Open: The number of cursors that MongoDB maintains for clients. For MongoDB

Single Instance (Type=3), the value N/A means that the data is not applicable. Thisdata is derived from the Total Open Cursor attribute in the KKJ MONGO INST IOINFO data set.

v Timed Out: The total number of cursors that have timed out since the server processstarted. For MongoDB Single Instance (Type=3), the value -1 means that the data is notapplicable. This data is derived from the Timeout Cursor attribute in the KKJ MONGOINST IO INFO data set.

Data Access (history)The Data Access (history) group widget shows a line chart that provides historical data ofthe number of times that the database could or could not access an index from memoryand return the index value for each collection period. By default, the line chart providesthe historical data for the period of last 4 hours. You can change this time period byusing the Time Selector widget.

Note: For MongoDB version 3.x, or later, the line chart displays 0 (zero) for all the KPIs.

The following KPIs for the widget are derived from the attributes as described:v Hits: The number of times that the mongod process accessed the index and returned

the index value from memory since the last data collection. For a router, the value -1means that the data is not applicable. This data is derived from the Number of Hitsattribute in the KKJ MONGO INST IO INFO data set.

v Interval time: The local time at the agent when the data was collected. This data isderived from the Timestamp attribute in the KKJ MONGO INST IO INFO data set.


v Misses: The number of times that an operation attempted to access an index that wasnot in memory since the last data collection. For a router, the value -1 means that thedata is not applicable. This data is derived from the Number of Misses attribute in theKKJ MONGO INST IO INFO data set.

v Resets: The number of times that the index counters were reset since the last datacollection. This data is derived from the Number of Resets attribute in the KKJMONGO INST IO INFO data set.

Data Flow (history)The Data Flow (history) group widget shows a line chart that provides historical data ofthe bytes in and out, and the number of requests on the selected host for each collectionperiod. By default, the line chart provides the historical data for the period of last 4hours. You can change this time period by using the Time Selector widget.

The following KPIs for the widget are derived from the attributes as described:v Bytes In (KB): A counter for the network traffic (in KB) that is received by the database

since the last data collection. This data is derived from the BytesIN attribute in the KKJMONGO INST IO INFO data set.

v Bytes Out (KB): A counter for the network traffic (in KB) that is sent from the databasesince the last data collection. This data is derived from the BytesOUT attribute in theKKJ MONGO INST IO INFO data set.

v Interval time: The local time at the agent when the data was collected. This data isderived from the Timestamp attribute in the KKJ MONGO INST IO INFO data set.

v Number of Requests: A counter for the number of requests that are received by thedatabase server since the last data collection. This data is derived from the NumRequests attribute in the KKJ MONGO INST IO INFO data set.

Queued Operations (history)The Queued Operations (history) group widget shows a line chart that provides historicaldata of the number of operations that are waiting for the read or the write lock on theselected host for each collection period. By default, the line chart provides the historicaldata for the period of last 4 hours. You can change this time period by using the TimeSelector widget.


derived from the Timestamp attribute in the KKJ MONGO INST IO INFO data set.v Read Lock: The total number of operations that are waiting for the read lock. For a

router, the value N/A means that the data is not applicable. This data is derived fromthe Total Current Readers attribute in the KKJ MONGO INST IO INFO data set.

v Write Lock: The total number of operations that are waiting for the write lock. For arouter, the value N/A means that the data is not applicable. This data is derived fromthe Total Current Writers attribute in the KKJ MONGO INST IO INFO data set.

Server DetailsThe Server Details group widget displays details of the MongoDB Version, Uptime,Warning, Messages and Bits.

The following KPIs for the widget are derived from the attributes as described:v MongoDB Instance PID: The process identification (PID) number on which the

MongoDB instance is currently running. This data is derived from the PID attribute inthe KKJ MONGO INSTANCE INFORMATION data set.

v MongoDB Version: Version of the MongoDB instance that is currently running. Thisdata is derived from the Mongo Version attribute in the KKJ MONGO INSTANCEINFORMATION data set.


v Process Up Time: The time (in seconds) for which the mongos or mongod process hasbeen active. This data is derived from the UpTime attribute in the KKJ MONGOINSTANCE INFORMATION data set.

v Server Warnings: A counter for the number of warnings that were generated since theserver process started. This data is derived from the Warnings attribute in the KKJMONGO INSTANCE INFORMATION data set.

MMAPv1 Storage Engine DetailsUse the MMAPv1 Storage Engine Details page to know the following details:v The table view that provides information about the background operations of the MMAPv1

storage engine.v The line charts that provide historical data (for last 4 hours) of the last flush time, average

flush time, journaling data, and the journaling time.


Background Operation (history)The Background Operation (history) group widget shows a line chart that provideshistorical data of the average flush time and the time that is required to complete the lastflush operation. By default, the line chart provides the historical data for the period oflast 4 hours. You can change this time period by using the Time Selector widget.

The following KPIs for the widget are derived from the attributes as described:v Average Flush Time: The average time (in milliseconds) that the mongod processes

spend in writing or flushing data to the disk. For a storage engine other thanMMAPv1, the value is N/A (not applicable). This data is derived from the Time AvgMS attribute in the KKJ MMAPV1 DETAILS data set.

v Interval time: The local time at the agent when the data was collected. This data isderived from the Timestamp attribute in the KKJ MMAPV1 DETAILS data set.

v Last Flush Time: The time (in milliseconds) that the last flush operation took tocomplete. For a storage engine other than MMAPv1, the value is N/A (not applicable).This data is derived from the Time Last MS attribute in the KKJ MMAPV1 DETAILSdata set.

Background Operation DetailsThe Background Operation Details group widget shows details of the backgroundoperations. These details include the number of flushes, number of commits, total writetime, and the time that is required for the last flush operation to complete.

The following KPIs for the widget are derived from the attributes as described:v Commits: The number of transactions that are written to the journal during the last

journal group commit interval. For a storage engine other than MMAPv1, the value isN/A (not applicable). This data is derived from the Commits attribute in the KKJMMAPV1 DETAILS data set.

v Flushes: A counter for the number of times that the database flushes all the writeoperations to the disk. For a storage engine other than MMAPv1, the value -1 meansthat the data is not applicable. This data is derived from the Flushes attribute in theKKJ MMAPV1 DETAILS data set.

v Last Flush Time (ms): The time (in milliseconds) that the last flush operation took tocomplete. For a storage engine other than MMAPv1, the value is N/A (not applicable).This data is derived from the Time Last MS attribute in the KKJ MMAPV1 DETAILSdata set.

v Total Write Time (ms): The time (in milliseconds) that the mongod processes spend inwriting or flushing data to the disk. For a storage engine other than MMAPv1, thevalue -1 means that the data is not applicable. This data is derived from the Time TotalMS attribute in the KKJ MMAPV1 DETAILS data set.


Journaling Data (history)The Journaling Data (history) group widget shows a line chart that provides historicalinformation about the data that is written to the journal during the last journal groupcommit interval. By default, the line chart provides the historical data for the period oflast 4 hours. You can change this time period by using the Time Selector widget.


derived from the Timestamp attribute in the KKJ MMAPV1 DETAILS data set.v Journaled Data: The data (in MB) that is written to the journal during the last journal

group commit interval. For a storage engine other than MMAPv1, the value is N/A(not applicable). This data is derived from the Journaled MB attribute in the KKJMMAPV1 DETAILS data set.

v Write To Data Files: The data (in MB) that is written from the journal to the data filesduring the last journal group commit interval. For a storage engine other thanMMAPv1, the value is N/A (not applicable). This data is derived from theWriteToDataFilesMB attribute in the KKJ MMAPV1 DETAILS data set.

Journaling Time (history)The Journaling Time (history) group widget shows a line chart that provides historicalinformation about the time that is spent in executing journaling operations, such aspreparing to write, writing to the journal and the data files, and remapping thecopy-on-write memory mapped views. By default, the line chart provides the historicaldata for the period of last 4 hours. You can change this time period by using the TimeSelector widget.

The following KPIs for the widget are derived from the attributes as described:v Data File: The time (in milliseconds) that is spent in writing to the data files after

journaling. For a storage engine other than MMAPv1, the value is N/A (notapplicable). This data is derived from the Time WriteToDataFiles attribute in the KKJMMAPV1 DETAILS data set.

v Interval: The local time at the agent when the data was collected. This data is derivedfrom the Timestamp attribute in the KKJ MMAPV1 DETAILS data set.

v Journal: The time (in milliseconds) that is spent in actually writing to the journal. For astorage engine other than MMAPv1, the value is N/A (not applicable). This data isderived from the Time WriteToJournal attribute in the KKJ MMAPV1 DETAILS dataset.

v Prepare Log Buffer: The time (in milliseconds) that is spent in preparing to write to thejournal. For a storage engine other than MMAPv1, the value is N/A (not applicable).This data is derived from the Time PrepLogBuffer attribute in the KKJ MMAPV1DETAILS data set.

v Private View: The time (in milliseconds) that is spent in remapping the copy-on-writememory mapped views. For a storage engine other than MMAPv1, the value is N/A(not applicable). This data is derived from the Time RemapPrivateView attribute in theKKJ MMAPV1 DETAILS data set.

MongoDB 2.x Lock DetailsUse the MongoDB 2.x Lock Details page to know the following details:v The table view that provides information about the database locks.v The line charts that provide historical data (for last 4 hours) of the database locks.


Database Lock Information - Top 15 (Based on Waiting Time)The Database Lock Information - Top 15 (Based on Waiting Time) group widget showsdetails of the database lock. These details include the database name, locked time, and


acquiring time. Click the name in the Database column to view the holding and acquiringlock details for this database as line charts in separate group widgets.

The following KPIs for the widget are derived from the attributes as described:v Database: The name of the database for which the lock information is available. This

data is derived from the Database Name attribute in the KKJ MONGO INST DB LOCKdata set.

v Locked Time (ms): The total time (in milliseconds) for which the database is lockedsince the last data collection. For MongoDB version 3.x, or later, the value is N/A (notapplicable). This data is derived from the Total Time Locked attribute in the KKJMONGO INST DB LOCK data set.

v Waiting Time (ms): The total time (in milliseconds) that the database needs to acquire alock since the last data collection. For MongoDB version 3.x, or later, the value is N/A(not applicable). This data is derived from the Total Time Acquiring attribute in theKKJ MONGO INST DB LOCK data set.

Database Locked Time (history)The Database Locked Time (history) group widget shows a line chart that provideshistorical data of the time for which the locks are held by the database for the read andwrite operations. This historical data is displayed for the database that you select in theDatabase Lock Information group widget. By default, the line chart provides the historicaldata for the period of last 4 hours. You can change this time period by using the TimeSelector widget.


derived from the Timestamp attribute in the KKJ MONGO INST DB LOCK data set.v Lock Read: The time (in milliseconds) that is spent in holding the read lock on the

database since the last data collection. This data is derived from the Time LockedMicros Read attribute in the KKJ MONGO INST DB LOCK data set.

v Lock Write: The time (in milliseconds) that is spent in holding the write lock on thedatabase since the last data collection. This data is derived from the Time LockedMicros Write attribute in the KKJ MONGO INST DB LOCK data set.

Database Waiting Time (history)The Database Waiting Time (history) group widget shows a line chart that provideshistorical data of the time that is spent in waiting to acquire the read and write locks onthe database since the last data collection. This historical data is displayed for thedatabase that you select in the Database Lock Information group widget. By default, theline chart provides the historical data for the period of last 4 hours. You can change thistime period by using the Time Selector widget.


derived from the Timestamp attribute in the KKJ MONGO INST DB LOCK data set.v Lock Read: The time (in milliseconds) that is spent in waiting to acquire the read lock

on the database since the last data collection. This data is derived from the TimeAcquiring Micros Read attribute in the KKJ MONGO INST DB LOCK data set.

v Lock Write: The time (in milliseconds) that is spent in waiting to acquire the write lockon the database since the last data collection. This data is derived from the TimeAcquiring Micros Write attribute in the KKJ MONGO INST DB LOCK data set.

MongoDB 3.x Lock DetailsUse the MongoDB 3.x Lock Details page to know the following details:v The table view that lists the available types of locks.


v The line charts that provide historical data (for last 4 hours) of the deadlocks, lock acquisitions,and waiting time for the selected lock type.

You can use this detail page to view details of lock version 3.x, or later.


Deadlock Count Details (history)The Deadlock Count Details (history) group widget shows a line chart that provideshistorical data for the number of times that the lock acquisitions encountered deadlockssince the last data collection. This data is displayed for the lock type that you select in theLock Types group widget. By default, the line chart provides the historical data for theperiod of last 4 hours. You can change this time period by using the Time Selectorwidget.

The following KPIs for the widget are derived from the attributes as described:v Deadlock Count : A counter for the total number of times that the lock acquisitions

encountered deadlocks since the last data collection. For MongoDB version 2.x, thevalue -1 means that the data is not applicable. This data is derived from the AcquiringDeadlock Count attribute in the KKJ MONGODB LOCKS data set.

v Interval time: The local time at the agent when the data was collected. This data isderived from the Timestamp attribute in the KKJ MONGODB LOCKS data set.

Lock Acquisitions Waiting Time (history)The Lock Acquisitions Waiting Time (history) group widget shows a line chart thatprovides historical data of the total cumulative wait time (in microseconds) for the lockacquisitions. This data is displayed for the lock type that you select in the Lock Typesgroup widget. By default, the line chart provides the historical data for the period of last4 hours. You can change this time period by using the Time Selector widget.


derived from the Timestamp attribute in the KKJ MONGODB LOCKS data set.v Waiting time: The total cumulative wait time (in microseconds) for the lock acquisitions

since the last data collection. For MongoDB version 2.x, the value -1 means that thedata is not applicable. This data is derived from the Time AcquiringMicros attribute inthe KKJ MONGODB LOCKS data set.

Lock Count Details (history)The Lock Count Details (history) group widget shows a line chart that provides historicaldata of the number of times that the lock was acquired. This data is displayed for thelock type that you select in the Lock Types group widget. By default, the line chartprovides the historical data for the period of last 4 hours. You can change this timeperiod by using the Time Selector widget.


derived from the Timestamp attribute in the KKJ MONGODB LOCKS data set.v Locked : A counter for the total number of times that the lock was acquired in all the

lock type modes since the last data collection. For MongoDB version 2.x, the value -1means that the data is not applicable. This data is derived from the Acquiring Countattribute in the KKJ MONGODB LOCKS data set.

v Waiting : A counter for the total number of times that the lock acquisitions encounteredwaits because the locks were held in a conflicting mode since the last data collection.For MongoDB version 2.x, the value -1 means that the data is not applicable. This datais derived from the Acquiring Wait Count attribute in the KKJ MONGODB LOCKSdata set.


Lock TypesThe Lock Types group widget lists the types of available locks. When you click the locktype in the group widget, details of this lock type are displayed in the other groupwidgets of the MongoDB 3.x Lock Details page.

The following KPIs for the widget are derived from the attributes as described:v Name: The type of the lock. The value N/A means data is not applicable. This data is

derived from the Lock type attribute in the KKJ MONGODB LOCKS data set.

Overall System DetailsUse the Overall System Details page to know the following details about the MongoDB system:v Status information for all the mongod processes in your system.v The number of active and available connections to each Mongo instance in the MongoDB

setup.v Details about the collection size of each database in this MongoDB instance, filtered by the

capped value.v Details about the host, such as the number of faults, the hit ratio, and the type of the storage

engine.v The 5 most active database collections that are based on the total rate of operations that are

performed.v The total lock times among collections for each database.v The top 5 mongod processes that use the most resident memory.v The top 5 mongod processes that use the most virtual memory.


Collection Size Details - Top 15 (Based on Percentage)The Collection Size Details - Top 15 (Based on Percentage) group widget displays thestatus and details of the collection size of each database in this MongoDB instance,filtered by the capped value. Click a row to open a pop-up table with collection details.

The following KPIs for the widget are derived from the attributes as described:v Available (MB): The total amount of preallocated storage space (in MB) within the

collection. The value N/A means that the data is not applicable. This data is derivedfrom the Collection Storage Size attribute in the KKJ COLLECTION STORAGE dataset.

v Capped: Indicates whether the collection is capped. This data is derived from the IsCapped attribute in the KKJ COLLECTION STORAGE data set.

v Collection: The name of the collection. This data is derived from the Collection Nameattribute in the KKJ COLLECTION STORAGE data set.

v Database: The name of the database. This data is derived from the Database Nameattribute in the KKJ COLLECTION STORAGE data set.

v Percent: The percentage of data space that is being used. The value N/A means thatthe data is not applicable. This data is derived from the Percentage Size attribute in theKKJ COLLECTION STORAGE data set.

v Used (MB): The data size (in MB) of the collection. This data is derived from theCollection Size attribute in the KKJ COLLECTION STORAGE data set.

Lock InformationThe Lock Information group widget shows the total lock times, the waiting time, and thelocked count. Click the name in the Host column to open the Lock Details page.v For MongoDB database version 2.x, the MongoDB 2.x Lock Details page is displayed.v For MongoDB database version 3.x, or later, the MongoDB 3.x Lock Details page is

displayed.


The following KPIs for the widget are derived from the attributes as described:v Host: The name of the host on which the mongod or mongos process is running. This

data is derived from the Host Name attribute in the KKJ LOCKS data set.v Locked Count: A counter for the total number of times that the lock was acquired in all

lock type modes since the last data collection. The value -1 means that the data is notapplicable. This data is derived from the Acquiring Count Total attribute in the KKJLOCKS data set.

v Locked Time(ms): The time (in milliseconds) that is spent on holding the locks on alldatabases since the last data collection. The value -1 means that the data is notapplicable. This data is derived from the Time Locked Total attribute in the KKJLOCKS data set.

v Waiting Time(ms): The total time (in milliseconds) that all databases need to acquire alock since the last data collection. The value -1 means that the data is not applicable.This data is derived from the Time Acquiring Total attribute in the KKJ LOCKS dataset.

MongoDB Instance DetailsThe MongoDB Instance Details group widget displays information about the host, such asthe number of faults, the hit ratio, and the type of the storage engine.v Click the name in the Host column to view the Input Output Information page.v Click the name in the Storage Engine column to view the Storage Engine Detail page.

The following KPIs for the widget are derived from the attributes as described:v Active Connections: The total number of active client connections to the database. For a

router, the value N/A means that the data is not applicable. This data is derived fromthe Total Active Connections attribute in the KKJ MONGO INST IO INFO data set.

v Hit Ratio: The ratio of the number of hits to the number of accesses. For a router andMongoDB version 3.x, or later, the value N/A means that the data is not applicable.This data is derived from the Hit Ratio attribute in the KKJ MONGO INST IO INFOdata set.

v Host: The host name of the system. The MongoDB instance for the port, which you arechecking for input and output information, runs on this system. This data is derivedfrom the Host Name attribute in the KKJ MONGO INST IO INFO data set.

v Page Faults: A counter for the number of page faults since the last data collection thatrequire disk operations. For a router, the value N/A means that the data is notapplicable. This data is derived from the Page Faults attribute in the KKJ MONGOINST IO INFO data set.

v Queued Operations: The total number of queued operations that are waiting for a lock.For a router, the value N/A means that the data is not applicable. This data is derivedfrom the Total Current Queue attribute in the KKJ MONGO INST IO INFO data set.

v Storage Engine: The name of the storage engine that is used for a particular node. Fora router, the value -1 means that the data is not applicable. This data is derived fromthe Storage Engine attribute in the KKJ MONGO INST IO INFO data set.

Number of Connections - (Based on Percentage)The Number of Connections - (Based on Percentage) group widget displays the numberof active and available connections to each Mongo instance in the MongoDB setup.

The following KPIs for the widget are derived from the attributes as described:v Available: A counter for the number of available connections to the database. This data

is derived from the Available Connections attribute in the KKJ MONGO INSTANCEINFORMATION data set.


v Current: A counter for the number of connections to the database server from theclients. This data is derived from the Current Connections attribute in the KKJMONGO INSTANCE INFORMATION data set.

v Host: The host name of the system. The MongoDB process for the port, which you arechecking, runs on this system. This data is derived from the Host Name attribute in theKKJ MONGO INSTANCE INFORMATION data set.

v Percent: The percentage of connections that are made out of the available connections.This data is derived from the Percentage of Connecitons attribute in the KKJ MONGOINSTANCE INFORMATION data set.

Operations Information - Top 5 (Based on Total Rate)The Operations Information - Top 5 (Based on Total Rate) group widget displays the 5most active database collections that are based on the total rate of the performedoperations.

The following KPIs for the widget are derived from the attributes as described:v Commands: A counter for the number of commands that are issued to the mongod

instance since the instance was last started. This data is derived from the Commandsattribute in the KKJ MONGO INSTANCE INFORMATION data set.

v Deletes: A counter for the number of delete operations on the mongod instance sincethe instance was last started. This data is derived from the Deletes attribute in the KKJMONGO INSTANCE INFORMATION data set.

v Getmore: A counter for the number of getmore operations on the mongod instancesince the instance was last started. This data is derived from the Getmore attribute inthe KKJ MONGO INSTANCE INFORMATION data set.

v Host Name: The host name of the system. The MongoDB process for the port, whichyou are checking, runs on this system. This data is derived from the Host Nameattribute in the KKJ MONGO INSTANCE INFORMATION data set.

v Inserts: A counter for the number of insert operations on the mongod instance since theinstance was last started. This data is derived from the Inserts attribute in the KKJMONGO INSTANCE INFORMATION data set.

v Queries: A counter for the number of queries on the mongod instance since theinstance was last started. This data is derived from the Queries attribute in the KKJMONGO INSTANCE INFORMATION data set.

v Updates: A counter for the number of update operations on the mongod instance sincethe instance was last started. This data is derived from the Updates attribute in the KKJMONGO INSTANCE INFORMATION data set.

Replication Status of MongoDB InstancesThe Replication Status of MongoDB Instances group widget displays information of thereplication status for all the mongod processes in your system. Click the IP address in theHost column to view the Replication Detail page. If the process that is listed in theReplica Name column is Single Instance, the Replication Details page is not displayed.

The following KPIs for the widget are derived from the attributes as described:v Host: The host name or IP address of the system on which the MongoDB process is

running. This data is derived from the Host attribute in the KKJ MONGOD LISTINGdata set.

v Port: The port number of the listed mongod process. This data is derived from the Portattribute in the KKJ MONGOD LISTING data set.

v Replica Name: The name of the replication set, process type, or single instance. Thisdata is derived from the Name attribute in the KKJ MONGOD LISTING data set.

v Role: The role of the shard member, such as primary, secondary, or an arbiter. This datais derived from the Role attribute in the KKJ MONGOD LISTING data set.


v Status: Status that is based on the offline or online state of the MongoDB instance andvalue of the replication lag.

Resident Memory Usage - Top 5 (Based on Usage)The Resident Memory Usage - Top 5 (Based on Usage) group widget displays the top 5mongod processes that use the most resident memory.

The following KPIs for the widget are derived from the attributes as described:v Host Name: The host name of the system. The MongoDB process for the port, which

you are checking, runs on this system. This data is derived from the Host Nameattribute in the KKJ MONGO INSTANCE INFORMATION data set.

v MB: The value of the resident memory (in MB). This value is approximately equivalentto the amount of RAM that is currently being used by the database process. This datais derived from the RAM Approx MB attribute in the KKJ MONGO INSTANCEINFORMATION data set.

Virtual Memory Usage - Top 5 (Based on Usage)The Virtual Memory Usage - Top 5 (Based on Usage) group widget displays the top 5Mongo processes that use the most virtual memory.

The following KPIs for the widget are derived from the attributes as described:v Host Name: The host name of the system. The MongoDB process for the port, which

you are checking, runs on this system. This data is derived from the Host Nameattribute in the KKJ MONGO INSTANCE INFORMATION data set.

v MB: The amount of virtual memory (in MB) that is used by the mongod process. Thisdata is derived from the Virtual Mem MB attribute in the KKJ MONGO INSTANCEINFORMATION data set.

Replication DetailsUse the Replication Details page to know the following details:v The table views that provide details of the replication member and the oplog.v The line charts that provide historical data (for last 4 hours) of the replication lag and the space

that is used by the oplog.


Oplog DetailsThe Oplog Details group widget shows details of the oplog. These details include the sizeand used space of the oplog, the time interval between the latest and the oldest entry inthe oplog, and the error message, if any.

The following KPIs for the widget are derived from the attributes as described:v Error Message: Displays an error message if there are no entries in the oplog. For

MongoDB Single Instance (Type=3), the value is N/A (not applicable). This data isderived from the Error msg attribute in the KKJ MONGOD LISTING data set.

v Oplog Window (seconds): The time interval (in seconds) between the oldest and thelatest entries in the oplog. This value usually corresponds to the approximate amountof time that is available in the replication oplog of the primary. For MongoDB SingleInstance (Type=3), the value is N/A (not applicable). This data is derived from theOplog Window attribute in the KKJ MONGOD LISTING data set.

v Total Size (MB): The total size (in MB) of the oplog. For MongoDB Single Instance(Type=3), the value is N/A (not applicable). This data is derived from the Total Sizeattribute in the KKJ MONGOD LISTING data set.

v Used Size (MB): The total amount of space (in MB) that is used by the oplog. ForMongoDB Single Instance (Type=3), the value is N/A (not applicable). This data isderived from the Used size attribute in the KKJ MONGOD LISTING data set.


Oplog Used (history)The Oplog Used (history) group widget shows a line chart that provides historical data ofthe percentage space that is used by the oplog. By default, the line chart provides thehistorical data for the period of last 4 hours. You can change this time period by usingthe Time Selector widget.


derived from the Timestamp attribute in the KKJ MONGOD LISTING data set.v Used : The total percentage of space that is used by the oplog.This value may exceed

beyond 100 percent if the space used for oplog is greater than the space allocated, inwhich case specify an opLog size sufficient for the required operation in oplog. ForMongoDB Single Instance (Type=3), the value is N/A (not applicable). This data isderived from the Percentage Used attribute in the KKJ MONGOD LISTING data set.

Replication DetailsThe Replication Details group widget shows details of the replication member. Thesedetails include the name, IP address, port, role, replication lag, and the last operation.

The following KPIs for the widget are derived from the attributes as described:v Port: The port number of the listed mongod process. This data is derived from the Port

attribute in the KKJ MONGOD LISTING data set.v Replica Member: The host name or IP address of the system on which the MongoDB

process is running. This data is derived from the Host attribute in the KKJ MONGODLISTING data set.

v Replica Name: The name of the replication set, process type, or single instance. Thisdata is derived from the Name attribute in the KKJ MONGOD LISTING data set.

v Replication Lag (minutes): The timestamp (in minutes) for the last (that is the latest)operation in the oplog. For MongoDB Single Instance (Type=3), the value is N/A (notapplicable). This data is derived from the Replication Lag attribute in the KKJMONGOD LISTING data set.

v Role: The role of the shard member, such as primary, secondary, or an arbiter. This datais derived from the Role attribute in the KKJ MONGOD LISTING data set.

Replication Lag (history)The Replication Lag (history) group widget shows a line chart that provides historicaldata of the timestamp of the latest operation in the oplog. By default, the line chartprovides the historical data for the period of last 4 hours. You can change this timeperiod by using the Time Selector widget.


derived from the Timestamp attribute in the KKJ MONGOD LISTING data set.v Replication Lag: The timestamp (in minutes) for the last (that is the latest) operation in

the oplog. For MongoDB Single Instance (Type=3), the value is N/A (not applicable).This data is derived from the Replication Lag attribute in the KKJ MONGOD LISTINGdata set.

WiredTiger Storage Engine DetailsUse the WiredTiger Storage Engine Details page to know the following details:v The table view that provides details about the cache memory of the storage engine.v The line charts that provide historical data (for last 4 hours) of the transaction and session

statistics, cache usage, and concurrent transactions.



Cache Details (MB)The Cache Details (MB) group widget shows details of the cache memory, such as thecache size, number of dirty bytes, and number of bytes that are written into the cachememory.



v Dirty Bytes: The number of dirty data bytes in the cache (in MB). For a storage engineother than WiredTiger or In-Memory, the value is N/A (not applicable). This data isderived from the Dirty Bytes attribute in the KKJ WIREDTIGER DETAILS data set.

v Read Bytes: The number of bytes that are read from the cache (in MB). For a storageengine other than WiredTiger or In-Memory, the value is N/A (not applicable). Thisdata is derived from the Read Bytes attribute in the KKJ WIREDTIGER DETAILS dataset.

v Write Bytes: The number of bytes that are written into the cache (in MB). For a storageengine other than WiredTiger or In-Memory, the value is N/A (not applicable). Thisdata is derived from the Write Bytes attribute in the KKJ WIREDTIGER DETAILS dataset.

Cache Usage (history)The Cache Usage (history) group widget shows a line chart that provides historical dataof the available and used cache memory. By default, the line chart provides the historicaldata for the period of last 4 hours. You can change this time period by using the TimeSelector widget.



v Cache Used: The size (in MB) of the data that is currently in the cache (in MB). For astorage engine other than WiredTiger or In-Memory, the value is N/A (not applicable).This data is derived from the Bytes in Cache attribute in the KKJ WIREDTIGERDETAILS data set.


Concurrent Transaction Tickets (history)The Concurrent Transaction Tickets (history) group widget shows a line chart thatprovides historical data of the percentage of available concurrent read and writeoperation tickets. By default, the line chart provides the historical data for the period oflast 4 hours. You can change this time period by using the Time Selector widget.


derived from the Timestamp attribute in the KKJ WIREDTIGER DETAILS data set.v Read Available: The percentage of the concurrent read operation tickets that are

available. For a storage engine other than WiredTiger or In-Memory, the value is N/A(not applicable). This data is derived from the Percentage Read attribute in the KKJWIREDTIGER DETAILS data set.

v Write Available: The percentage of the concurrent write operation tickets that areavailable. For a storage engine other than WiredTiger or In-Memory, the value is N/A(not applicable). This data is derived from the Percentage Write attribute in the KKJWIREDTIGER DETAILS data set.


Failed Transaction (history)The Failed Transaction (history) group widget shows a line chart that provides historicaldata of the number of transactions that failed or were rolled back. By default, the linechart provides the historical data for the period of last 4 hours. You can change this timeperiod by using the Time Selector widget.

The following KPIs for the widget are derived from the attributes as described:v Failed: A counter for the transactions that failed due to the cache overflow. For a

storage engine other than WiredTiger or In-Memory, the value is N/A (not applicable).This data is derived from the Transaction Failed attribute in the KKJ WIREDTIGERDETAILS data set.


v Rollback: A counter for the transactions that were rolled back. For a storage engineother than WiredTiger or In-Memory, the value is N/A (not applicable). This data isderived from the Transaction Rolled Back attribute in the KKJ WIREDTIGER DETAILSdata set.

Session Statistics (history)The Session Statistics (history) group widget shows a line chart that provides historicaldata of the number of open cursors and open sessions. By default, the line chart providesthe historical data for the period of last 4 hours. You can change this time period byusing the Time Selector widget.


derived from the Timestamp attribute in the KKJ WIREDTIGER DETAILS data set.v Open Cursor: The number of open cursors. For a storage engine other than WiredTiger

or In-Memory, the value is N/A (not applicable). This data is derived from the OpenCursor attribute in the KKJ WIREDTIGER DETAILS data set.

v Open Session: The number of open sessions. For a storage engine other thanWiredTiger or In-Memory, the value is N/A (not applicable). This data is derived fromthe Open Session attribute in the KKJ WIREDTIGER DETAILS data set.

v TIMESTAMP: The local time at the agent when the data was collected. This data isderived from the Timestamp attribute in the KKJ WIREDTIGER DETAILS data set.

Transaction Details (history)The Transaction Details (history) group widget shows a line chart that provides historicaldata of the number of transactions that were started, committed, rolled back, and failed.By default, the line chart provides the historical data for the period of last 4 hours. Youcan change this time period by using the Time Selector widget.

The following KPIs for the widget are derived from the attributes as described:v Committed: A counter for the transactions that were committed since the server

startup. For a storage engine other than WiredTiger or In-Memory, the value is N/A(not applicable). This data is derived from the Committed Transactions attribute in theKKJ WIREDTIGER DETAILS data set.


v Transaction Begins: A counter for the transactions that were started since the serverstartup. For a storage engine other than WiredTiger or In-Memory, the value is N/A(not applicable). This data is derived from the Transaction Begins attribute in the KKJWIREDTIGER DETAILS data set.


Additional group widgetsThese pop-up group widgets are displayed after you click a group widget for more details. Somegroup widgets have links to more granular information in a popup widget, described here.


Response Times - Top 5The Response Times - Top 5 group widget displays the top 5 largest average operationresponse times.

The following KPIs for the widget are derived from the attributes as described:v Avg Response Time In MS: The average response time (in milliseconds) for this

command type. This data is derived from the Avg Response Time In MS attribute inthe KKJ RT COPY FOR APMUI data set.

v Cat Op Names: Concatenation of operation, database name, and collection name. Thisdata is derived from the Cat Op Names attribute in the KKJ RT COPY FOR APMUIdata set.

v Cat Op Names: Concatenation of operation, database name, and collection name. Thisdata is derived from the Cat Op Names attribute in the KKJ RESPONSE TIMES dataset.

v Max Response Time In MS: The longest time (in milliseconds) that a command of thistype requires to complete. This data is derived from the Max Response Time In MSattribute in the KKJ RESPONSE TIMES data set.

Custom viewsAfter you select an application that includes a MongoDB managed resource, the Custom Views tab isavailable for displaying and building custom dashboard pages with attribute values from the MongoDBAgent. You can quickly build monitoring pages for an application and save them for viewing.

Only a subset of MongoDB Agent attributes, which are the most useful for reporting, are available forcustom views. These attributes are shown in italic in Chapter 4, “Attributes,” on page 27.



Chapter 3. Thresholds

Thresholds test for certain conditions on your managed resources, such as memory usage over 95%, andraise an event when the conditions have been met.

The agent comes with predefined thresholds that you can use to monitor your MongoDB environment.You can create additional thresholds for the areas of interest.

After you click

System Configuration > Threshold Manager, select MongoDB as the data sourcetype to see all the available thresholds.

Predefined thresholdsThe thresholds are organized in the Cloud APM console Threshold Manager by the data set for whichthey were written. The MongoDB Agent has the following predefined thresholds:

KKJ_MongoDB_Coll_Nearly_FullMongoDB collection is critically full.

The default configuration has the following SQL syntax:

*IF *VALUE KKJ_COLLECTION_STORAGE.Percentage_Size *GE 90 *AND *VALUEKKJ_COLLECTION_STORAGE.Is_Capped *EQ 1

This threshold is evaluated every 5 minutes.

The severity of this threshold is Critical.

The threshold is evaluated for each distinct value of the Database_Name attribute.

This threshold uses the following attributes:Collection_Storage.Percentage_Size[COLLECT.PERCENTAGE],Collection_Storage.Is_Capped[COLLECT.IS_CAPPED],Collection_Storage.Database_Name[COLLECT.DATABASE_N].

KKJ_MongoDB_Coll_Usage_HighMongoDB collection is gradually increasing.


*IF *VALUE KKJ_COLLECTION_STORAGE.Percentage_Size *GE 75 *AND *VALUEKKJ_COLLECTION_STORAGE.Percentage_Size *LT 90 *AND *VALUEKKJ_COLLECTION_STORAGE.Is_Capped *EQ 1


The severity of this threshold is Warning.

The threshold is evaluated for each distinct value of the Database_Name attribute.

This threshold uses the following attributes:Collection_Storage.Percentage_Size[COLLECT.PERCENTAGE],Collection_Storage.Is_Capped[COLLECT.IS_CAPPED],Collection_Storage.Database_Name[COLLECT.DATABASE_N].

KKJ_MongoDB_Connections_HighNumber of connections is critically high.


*IF *VALUE KKJ_MONGO_INSTANCE_INFORMATION.Percentage_of_Connecitons *GE 90




The threshold is evaluated for each distinct value of the Host_Name attribute.

This threshold uses the following attributes:Mongo_Instance_Information.Percentage_of_Connecitons[MONGOIN.PERCENTAGE],Mongo_Instance_Information.Host_Name[MONGOIN.HOST_NAME].

KKJ_MongoDB_Connections_High_WarnNumber of connections is high.


*IF *VALUE KKJ_MONGO_INSTANCE_INFORMATION.Percentage_of_Connecitons *GE 70 *AND *VALUEKKJ_MONGO_INSTANCE_INFORMATION.Percentage_of_Connecitons *LT 90



The threshold is evaluated for each distinct value of the Host_Name attribute.

This threshold uses the following attributes:Mongo_Instance_Information.Percentage_of_Connecitons[MONGOIN.PERCENTAGE],Mongo_Instance_Information.Host_Name[MONGOIN.HOST_NAME].

KKJ_MongoDB_DownThere is no running process, system is down.


*IF *VALUE KKJ_GLOBAL_STATUS.Status *EQ 0



The threshold is evaluated for each distinct value of the Status attribute.

This threshold uses the following attributes: Global_Status.Status[GLOBALS.STATUS].

KKJ_MongoDB_Members_DownReplication set does not have enough voting members.


*IF *VALUE KKJ_GLOBAL_STATUS.Status *EQ 1



The threshold is evaluated for each distinct value of the Status attribute.

This threshold uses the following attributes: Global_Status.Status[GLOBALS.STATUS].

KKJ_Replication_Lag_CriticalMongoDB replication lag value is critical.


*IF *VALUE KKJ_MONGOD_LISTING.Replication_Lag *GE 4



The threshold is evaluated for each distinct value of the Host attribute.


This threshold uses the following attributes:Mongod_Listing.Replication_Lag[MONGODL.REPLLAG],Mongod_Listing.Host[MONGODL.HOST0].

KKJ_Replication_Lag_WarningMongoDB replication lag value is gradually increasing.


*IF *VALUE KKJ_MONGOD_LISTING.Replication_Lag *GE 1 *AND *VALUEKKJ_MONGOD_LISTING.Replication_Lag *LT 4



The threshold is evaluated for each distinct value of the Host attribute.

This threshold uses the following attributes:Mongod_Listing.Replication_Lag[MONGODL.REPLLAG],Mongod_Listing.Host[MONGODL.HOST0].

Customized thresholdsYou can use the predefined thresholds as a starting point for event monitoring, and create your ownthresholds as conditions arise that you want to monitor.

The MongoDB Agent has many data sets that you can use to create thresholds to monitor for specificconditions. For descriptions of the data sets, see Chapter 4, “Attributes,” on page 27.

Tip: The hover help for the Threshold Editor Data set field has a Learn more link to the attributedescriptions for the selected data set.

Chapter 3. Thresholds 25


Chapter 4. Attributes

Attributes are the application properties that are being measured and reported by the Monitoring Agentfor MongoDB. Attributes make up the key performance indicators (KPIs) that are reported, and you canuse them to create thresholds for conditions that you want to monitor.

About attributes

Attributes are organized into data sets (also referred to as attribute groups). The values can be selectivelydisplayed in dashboards or used to define a threshold.

The most recent data sample of the attributes in the data set are used after you open a dashboard or starta threshold.

DashboardsOnly a subset of MongoDB Agent attributes is displayed in the dashboards. Queries to thedashboard data provider specify which attribute values to request from the managed resource.These attributes are shown in italic in this chapter. You can use these attributes to create thecharts and tables in custom dashboard pages.

ThresholdsYou can define thresholds that monitor the state of your operating system, database, orapplication and open an event when the threshold is exceeded. You use attributes to definethresholds that describe a condition that you want to test. After the threshold is started, theattribute values that are specified in the threshold are compared with the values collected by theMongoDB Agent. After the condition is met, an event is registered and you are alerted byindicators in the Application Performance Dashboard navigator, All My Applications summaryboxes, and the Events tab.

The MongoDB Agent comes with predefined thresholds that are enabled and started with the agentor data collector. If you edit a predefined threshold, such as to change the condition or severity, itis no longer treated as a predefined threshold but considered a custom threshold.

All MongoDB Agent attributes, unless otherwise noted, can be used to create custom thresholds.The Events tab has a table of open events with information, including threshold name, severity,source, and display item. You can expand an event row to see the formula and drill down to thedashboard for the managed resource.

Some attributes names display differently in the Threshold Editor, as shown in parentheses afterthe name, such as “Object Count (OBJECT_COUNT)”.

Historical data configurationsThe MongoDB Agent collects historical data for key data sets that are shown in the dashboards.A dashboard page that includes historical views from the managed resource instance has a timeselector tool for adjusting the time range. With line charts, you can also compare the values witha previous day, up to the number of days that have been saved.

Additional information about attributes

Note the following conditions:v When no data can be collected for a data set, an empty result is returned (no rows of data)v When a specific attribute cannot be collected, the value 0 or “” is returned unless otherwise specified in

a particular attribute (for example, “N/A”)v Any numeric attribute value that is greater than the largest (positive or negative) number that can be

represented by that type returns the corresponding maximum or minimum value (for example, the


maximum value for a 32-bit number is 2,147,483,647). These values are displayed as text values that aredefined by the data set, such as “Value Exceeds Maximum” or “Value Exceeds Minimum”.

Numeric attributes have characteristics that are indicated in parentheses after the data type, such as“(32-bit numeric property)”. A numeric attribute value can be 32-bit or 64-bit or some other size. Thevalue type can be gauge, which means it varies, like a speedometer; counter, which counts and alwaysincreases; or numeric property, such as disk size.

For a list of the data sets, a list of the attributes in each data set, and descriptions of the attributes in theMongoDB Agent, see “Data sets for the monitoring agent” and “Attribute descriptions” on page 29.

Data sets for the monitoring agentThe MongoDB Agent contains the following data sets.v Data set name: Collection Storage

– Table name: KKJCOLLECT– Historical table name: KKJ_COLLECTION_STORAGE or KKJCOLLECT

v Data set name: Database Names– Table name: KKJDATABAS– Historical table name: KKJ_DATABASE_NAMES or KKJDATABAS

v Data set name: General Shard Information– Table name: KKJGENERAL– Historical table name: KKJ_GENERAL_SHARD_INFORMATION or KKJGENERAL

v Data set name: Global Status– Table name: KKJGLOBALS– Historical table name: KKJ_GLOBAL_STATUS or KKJGLOBALS

v Data set name: Locks– Table name: KKJLOCK– Historical table name: KKJ_LOCKS or KKJLOCK

v Data set name: MII Copy for APM UI One– Table name: KKJMIICOPY– Historical table name: KKJ_MII_COPY_FOR_APMUI_ONE or KKJMIICOPY

v Data set name: MII Copy for APM UI Two– Table name: KKJMIICOP0– Historical table name: KKJ_MII_COPY_FOR_APMUI_TWO or KKJMIICOP0

v Data set name: MMAPv1 Details– Table name: KKJSTORAGM– Historical table name: KKJ_MMAPV1_DETAILS or KKJSTORAGM

v Data set name: Mongo Inst DB Lock– Table name: KKJMONGOI0– Historical table name: KKJ_MONGO_INST_DB_LOCK or KKJMONGOI0

v Data set name: Mongo Inst IO Info– Table name: KKJMONGOIO– Historical table name: KKJ_MONGO_INST_IO_INFO or KKJMONGOIO

v Data set name: Mongo Instance Information– Table name: KKJMONGOIN– Historical table name: KKJ_MONGO_INSTANCE_INFORMATION or KKJMONGOIN


v Data set name: Mongod Listing– Table name: KKJMONGODL– Historical table name: KKJ_MONGOD_LISTING or KKJMONGODL

v Data set name: MongoDB Locks– Table name: KKJDBLOCKN– Historical table name: KKJ_MONGODB_LOCKS or KKJDBLOCKN

v Data set name: Performance Object Status– Table name: KKJPOBJST– Historical table name: KKJ_PERFORMANCE_OBJECT_STATUS or KKJPOBJST

v Data set name: Response Times– Table name: KKJRESPONS– Historical table name: KKJ_RESPONSE_TIMES or KKJRESPONS

v Data set name: Router Location– Table name: KKJROUTERL– Historical table name: KKJ_ROUTER_LOCATION or KKJROUTERL

v Data set name: RT Copy for APM UI– Table name: KKJRTCOPYF– Historical table name: KKJ_RT_COPY_FOR_APMUI or KKJRTCOPYF

v Data set name: Take Action Status– Table name: KKJTACTST– Historical table name: KKJ_TAKE_ACTION_STATUS or KKJTACTST

v Data set name: Thread Pool Status– Table name: KKJTHPLST– Historical table name: KKJ_THREAD_POOL_STATUS or KKJTHPLST

v Data set name: WiredTiger Details– Table name: KKJSTORAGW– Historical table name: KKJ_WIREDTIGER_DETAILS or KKJSTORAGW

Attribute descriptionsAttributes in each MongoDB Agent data set collect data that the agent uses for monitoring.

The descriptions of the data sets contain information such as description, type, and names for eachattribute in the data set. Some attributes are designated as key attributes, which are identifier attributesfor the data set. An attribute in italic indicates that it is available for display in the ApplicationPerformance Dashboard pages.

Collection Storage data setAmount of data contained in a collection and its preallocated space. Thresholds for this data set areassociated with the MongoDB component. This data set is displayed as KKJ COLLECTION_STORAGE inthe threshold editor. A data sample is sent to the server every 5 minutes and is maintained for 8 days bydefault. The default data sample consists of the first 15 rows sorted by Percentage_Size. The attributesshown in italic are visible in the UI. All attributes are available for thresholds.

This data set contains the following attributes:

Collection NameThe name of the collection. This attribute is a key attribute. The type is string.

Chapter 4. Attributes 29

The following names are defined for this attribute: COLLECTION_NAME or COLLECTIO0(historical name), Collection Name (caption), Collection_Name (attribute name), and COLLECTIO0(column name).

Collection SizeThe data size (in MB) of the collection. The type is real number (32-bit gauge) with four decimalplaces of precision.

The following names are defined for this attribute: COLLECTION_SIZE or SIZE_CO (historicalname), Collection Size (caption), Collection_Size (attribute name), and SIZE_CO (column name).

Collection Storage SizeThe total amount of preallocated storage space (in MB) within the collection. The value N/Ameans that the data is not applicable. The type is real number (32-bit gauge) with four decimalplaces of precision with enumerated values. The following values are defined: N/A (-1). Anyvalue that does not have a definition here is displayed in the User Interface.

The following names are defined for this attribute: COLLECTION_STORAGE_SIZE orSTORAGE_CO (historical name), Collection Storage Size (caption), Collection_Storage_Size(attribute name), and STORAGE_CO (column name).

Database NameThe name of the database. This attribute is a key attribute. The type is string.

The following names are defined for this attribute: DATABASE_NAME or DATABASE_N(historical name), Database Name (caption), Database_Name (attribute name), and DATABASE_N(column name).

Is CappedIndicates whether the collection is capped. The type is integer (32-bit gauge) with enumeratedvalues. The following values are defined: True (1), False (0). Any value that does not have adefinition here is displayed in the User Interface.

The following names are defined for this attribute: IS_CAPPED (historical name), Is Capped(caption), Is_Capped (attribute name), and IS_CAPPED (column name).

Node The managed system name of the agent. This attribute is a key attribute. The type is string.

The following names are defined for this attribute: NODE (historical name), Node (caption),ORIGINNODE (attribute name), and ORIGINNODE (column name).

Percentage SizeThe percentage of data space that is being used. The value N/A means that the data is notapplicable. The type is real number (32-bit gauge) with two decimal places of precision withenumerated values. The following values are defined: N/A (-1). Any value that does not have adefinition here is displayed in the User Interface.

The following names are defined for this attribute: PERCENTAGE_SIZE or PERCENTAGE(historical name), Percentage Size (caption), Percentage_Size (attribute name), and PERCENTAGE(column name).

TimestampThe local time at the agent when the data was collected. The type is string.

The following names are defined for this attribute: TIMESTAMP (historical name), Timestamp(caption), Timestamp (attribute name), and TIMESTAMP (column name).

Avg SizeThe average element size (in MB). The type is integer (32-bit counter).

The following names are defined for this attribute: AVG_SIZE (historical name), Avg Size(caption), Avg_Size (attribute name), and AVG_SIZE (column name).


Cat NamesConcatenation of the database and collection names. The type is string.

The following names are defined for this attribute: CAT_NAMES (historical name), Cat Names(caption), Cat_Names (attribute name), and CAT_NAMES (column name).

Max DocumentsThe maximum number of documents that can be included in a collection. The type is string.

The following names are defined for this attribute: MAX_DOCUMENTS or MAX_DOCUME(historical name), Max Documents (caption), Max_Documents (attribute name), andMAX_DOCUME (column name).

Object CountThe number of json data objects in the collection. The type is integer (64-bit counter).

The following names are defined for this attribute: OBJECT_COUNT or OBJECT_CO0 (historicalname), Object Count (caption), Object_Count (attribute name), and OBJECT_CO0 (column name).

Size The data size (in MB) of the collection. The type is integer (64-bit counter).

The following names are defined for this attribute: SIZE (historical name), Size (caption), Size(attribute name), and SIZE (column name).

Storage SizeThe total amount of preallocated storage space (in MB) within the collection. The value N/Ameans that the data is not applicable. The type is integer (64-bit counter) with enumerated values.The following values are defined: N/A (-1). Any value that does not have a definition here isdisplayed in the User Interface.

The following names are defined for this attribute: STORAGE_SIZE or STORAGE_S0 (historicalname), Storage Size (caption), Storage_Size (attribute name), and STORAGE_S0 (column name).

Database Names data setA list of active database names associated with this mongod or mongos instance.




Is EmptyIndicates if the database contains data. The type is string.

The following names are defined for this attribute: IS_EMPTY (historical name), Is Empty(caption), Is_Empty (attribute name), and IS_EMPTY (column name).



Size BytesTotal size (in bytes) of the database. The type is integer (64-bit gauge).

The following names are defined for this attribute: SIZE_BYTES (historical name), Size Bytes(caption), Size_Bytes (attribute name), and SIZE_BYTES (column name).




General Shard Information data setInformation about mongod ownership among the shards, along with the number of contained collections,objects, and the maximum storage size of the shard.


Available Storage SizeThe storage size that is available in the database. The type is integer (32-bit gauge).

The following names are defined for this attribute: AVAIALBE_STORAGE_SIZE or AVAIALBE_S(historical name), Available Storage Size (caption), Avaialbe_Storage_Size (attribute name), andAVAIALBE_S (column name).

Avg Object SizeAverage size of all the KEY:VALUE objects contained within the shard. The type is integer (32-bitgauge).

The following names are defined for this attribute: AVG_OBJECT_SIZE or AVG_OBJECT(historical name), Avg Object Size (caption), Avg_Object_Size (attribute name), and AVG_OBJECT(column name).

Cat NameConcatenation of the shard and the database names. The type is string.

The following names are defined for this attribute: CAT_NAME (historical name), Cat Name(caption), Cat_Name (attribute name), and CAT_NAME (column name).

Database NameThe name of the database that belongs to this shard. This attribute is a key attribute. The type isstring.


Index SizeThe total size of all indexes in the database. The type is integer (64-bit counter).

The following names are defined for this attribute: INDEX_SIZE (historical name), Index Size(caption), Index_Size (attribute name), and INDEX_SIZE (column name).

Mongod InstancesA comma delimited list of the host name or IP:PORT addresses of the MongoDB instances thatare members of the shard. The type is string.

The following names are defined for this attribute: MONGOD_INSTANCES or MONGOD_INS(historical name), Mongod Instances (caption), Mongod_Instances (attribute name), andMONGOD_INS (column name).



Num of CollectionsThe number of collections that are associated with the shard. The type is integer (32-bit counter).

The following names are defined for this attribute: NUM_OF_COLLECTIONS or NUM_OF_COL(historical name), Num of Collections (caption), Num_of_Collections (attribute name), andNUM_OF_COL (column name).


Num of ExtentsThe number of extents in the database across all collections. The type is integer (32-bit counter).

The following names are defined for this attribute: NUM_OF_EXTENTS or NUM_OF_EXT(historical name), Num of Extents (caption), Num_of_Extents (attribute name), andNUM_OF_EXT (column name).

Num of IndexesThe total number of indexes in the database. The type is integer (32-bit counter).

The following names are defined for this attribute: NUM_OF_INDEXES or NUM_OF_IND(historical name), Num of Indexes (caption), Num_of_Indexes (attribute name), andNUM_OF_IND (column name).

Num of Objects RecordedThe number of KEY:VALUE objects contained within the shard. The type is integer (64-bitcounter).

The following names are defined for this attribute: NUM_OF_OBJECTS_RECORDED orNUM_OF_OBJ (historical name), Num of Objects Recorded (caption), Num_of_Objects_Recorded(attribute name), and NUM_OF_OBJ (column name).

Percentage SizeThe percentage of data within the collection when compared to the total size for each shard. Thetype is integer (32-bit gauge).

The following names are defined for this attribute: PERCENTAGE_SIZE or PERCENTAGE(historical name), Percentage Size (caption), Percentage_Size (attribute name), and PERCENTAGE(column name).

Shard NameThe user-defined name of a shard. This attribute is a key attribute. The type is string.

The following names are defined for this attribute: SHARD_NAME (historical name), ShardName (caption), Shard_Name (attribute name), and SHARD_NAME (column name).

Size of DataThe amount of data (in bytes) in the shard. The type is integer (64-bit counter).

The following names are defined for this attribute: SIZE_OF_DATA or SIZE_OF_DA (historicalname), Size of Data (caption), Size_of_Data (attribute name), and SIZE_OF_DA (column name).

Size of Data ScaledThe size of the data scaled in KB. The type is integer (64-bit counter).

The following names are defined for this attribute: SIZE_OF_DATA_SCALED or SIZE_OF_D0(historical name), Size of Data Scaled (caption), Size_of_Data_Scaled (attribute name), andSIZE_OF_D0 (column name).

Storage SizeThe disk space that is currently preallocated for the shard. The type is integer (64-bit counter).

The following names are defined for this attribute: STORAGE_SIZE or STORAGE_SI (historicalname), Storage Size (caption), Storage_Size (attribute name), and STORAGE_SI (column name).



Total Size of DatabaseThe total size of all the files that hold the database contents; does not include namespace files.The type is integer (64-bit counter).


The following names are defined for this attribute: TOTAL_SIZE_OF_DATABASE or TOTAL_SIZE(historical name), Total Size of Database (caption), Total_Size_of_Database (attribute name), andTOTAL_SIZE (column name).

Total Size of NamespaceThe total size of namespace files in the database. The files cannot be modified after thenamespace has been created. The type is integer (32-bit counter).

The following names are defined for this attribute: TOTAL_SIZE_OF_NAMESPACE orTOTAL_SIZ0 (historical name), Total Size of Namespace (caption), Total_Size_of_Namespace(attribute name), and TOTAL_SIZ0 (column name).

Global Status data setThe global status of the system such as, critical, warning, and running. Thresholds for this data set areassociated with the MongoDB component. This data set is displayed as KKJ GLOBAL_STATUS in thethreshold editor. A data sample is sent to the server every minute and is maintained for 8 days bydefault. The attributes shown in italic are visible in the UI. All attributes are available for thresholds.




Status The value of the global status. The type is integer (32-bit gauge) with enumerated values. Thefollowing values are defined: Value Exceeds Maximum (2147483647), Value Exceeds Minimum(-2147483648), Down (0), Warning (1), Running (2). Any value that does not have a definition hereis displayed in the User Interface.

The following names are defined for this attribute: STATUS (historical name), Status (caption),Status (attribute name), and STATUS (column name).



Locks data setThe lock summary for all mongod instances. This data set is configured for historical collection.Thresholds for this data set are associated with the MongoDB component. This data set is displayed asKKJ LOCKS in the threshold editor. A data sample is sent to the server every minute and is maintainedfor 8 days by default. The attributes shown in italic are visible in the UI. All attributes are available forthresholds.


Acquiring Count TotalA counter for the total number of times that the lock was acquired in all lock type modes sincethe last data collection. The value -1 means that the data is not applicable. The type isDEFAULT(2).

The following names are defined for this attribute: ACQUIRING_COUNT_TOTAL or ACOUNTN(historical name), Acquiring Count Total (caption), Acquiring_Count_Total (attribute name), andACOUNTN (column name).

Host NameThe name of the host on which the mongod or mongos process is running. This attribute is a keyattribute. The type is string.


The following names are defined for this attribute: HOST_NAME or HOST (historical name), HostName (caption), Host_Name (attribute name), and HOST (column name).



Target PageThe name of the target page for the Cloud APM console, which differs for MongoDB version 2.xand MongoDB version 3.x, or later. This attribute is a key attribute. The type is string.

The following names are defined for this attribute: TARGET_PAGE or PAGE (historical name),Target Page (caption), Target_Page (attribute name), and PAGE (column name).

Time Acquiring TotalThe total time (in milliseconds) that all databases need to acquire a lock since the last datacollection. The value -1 means that the data is not applicable. The type is DEFAULT(2).

The following names are defined for this attribute: TIME_ACQUIRING_TOTAL orTOTALACQUN (historical name), Time Acquiring Total (caption), Time_Acquiring_Total (attributename), and TOTALACQUN (column name).

Time Locked TotalThe time (in milliseconds) that is spent on holding the locks on all databases since the last datacollection. The value -1 means that the data is not applicable. The type is DEFAULT(2).

The following names are defined for this attribute: TIME_LOCKED_TOTAL or TIMELOCKN(historical name), Time Locked Total (caption), Time_Locked_Total (attribute name), andTIMELOCKN (column name).



MII Copy for APM UI One data setFiltered data rows from the Mongo Instance Information data set. Thresholds for this data set areassociated with the MongoDB component. This data set is displayed as KKJMII_COPY_FOR_APMUI_ONE in the threshold editor. A data sample is sent to the server every minuteand is maintained for 8 days by default. The default data sample consists of the first 1 rows sorted byRAM_Approx_MB. The attributes shown in italic are visible in the UI. All attributes are available forthresholds.


Host NameThe host name of the system. The MongoDB instance for the port, which you are checking, runson this system. This attribute is a key attribute. The type is string.

The following names are defined for this attribute: HOST_NAME (historical name), Host Name(caption), Host_Name (attribute name), and HOST_NAME (column name).



RAM Approx MBThe value of the resident memory (in MB). This value is approximately equivalent to the amountof RAM that is currently being used by the database process. The type is integer (32-bit gauge).


The following names are defined for this attribute: RAM_APPROX_MB or RAM_APPROX(historical name), RAM Approx MB (caption), RAM_Approx_MB (attribute name), andRAM_APPROX (column name).



Available ConnectionsA counter for the number of available connections to the database. The type is integer (64-bitcounter).

The following names are defined for this attribute: AVAILABLE_CONNECTIONS orAVAILABLE_ (historical name), Available Connections (caption), Available_Connections (attributename), and AVAILABLE_ (column name).

Bits The architecture of the target system. The type is integer (32-bit counter).

The following names are defined for this attribute: BITS (historical name), Bits (caption), Bits(attribute name), and BITS (column name).

BytesINA counter for the network traffic (in bytes) that is received by the database. The type is integer(64-bit gauge).

The following names are defined for this attribute: BYTESIN (historical name), BytesIN (caption),BytesIN (attribute name), and BYTESIN (column name).

BytesOUTA counter for the network traffic (in bytes) that is sent from the database. The type is integer(64-bit gauge).

The following names are defined for this attribute: BYTESOUT (historical name), BytesOUT(caption), BytesOUT (attribute name), and BYTESOUT (column name).

CommandsA counter for the number of commands that are issued to the database since the mongod instancewas last started. The type is DEFAULT(2).

The following names are defined for this attribute: COMMANDS (historical name), Commands(caption), Commands (attribute name), and COMMANDS (column name).

Current ConnectionsA counter for the number of connections to the database server from clients. The type is integer(32-bit counter).

The following names are defined for this attribute: CURRENT_CONNECTIONS orCURRENT_CO (historical name), Current Connections (caption), Current_Connections (attributename), and CURRENT_CO (column name).

DeletesA counter for the number of delete operations that are received since the mongod instance waslast started. The type is real number (rate of change between successive values) with two decimalplaces of precision.

The following names are defined for this attribute: DELETES (historical name), Deletes (caption),Deletes (attribute name), and DELETES (column name).

GetmoreA counter for the number of getmore operations that are received since the mongod instance waslast started. The type is real number (rate of change between successive values) with two decimalplaces of precision.


The following names are defined for this attribute: GETMORE (historical name), Getmore(caption), Getmore (attribute name), and GETMORE (column name).

InsertsA counter for the number of insert operations that are received since the mongod instance waslast started. The type is real number (rate of change between successive values) with two decimalplaces of precision.

The following names are defined for this attribute: INSERTS (historical name), Inserts (caption),Inserts (attribute name), and INSERTS (column name).

MessagesA counter for the number of messages that were generated since the server process started. Thetype is integer (32-bit counter).

The following names are defined for this attribute: MESSAGES (historical name), Messages(caption), Messages (attribute name), and MESSAGES (column name).

Mongo VersionThe version of the MongoDB instance that is currently running. The type is string.

The following names are defined for this attribute: MONGO_VERSION or MONGO_VERS(historical name), Mongo Version (caption), Mongo_Version (attribute name), and MONGO_VERS(column name).

Num RequestsA counter for the number of requests that are received by the database server. The type is integer(32-bit counter).

The following names are defined for this attribute: NUM_REQUESTS or NUM_REQUES(historical name), Num Requests (caption), Num_Requests (attribute name), and NUM_REQUES(column name).

Op TotalThe total rate of operations on the mongod instance. The type is real number (32-bit gauge) withtwo decimal places of precision.

The following names are defined for this attribute: OP_TOTAL (historical name), Op Total(caption), Op_Total (attribute name), and OP_TOTAL (column name).

Page FaultsA counter for the number of page faults that require disk operations. The type is integer (32-bitgauge).

The following names are defined for this attribute: PAGE_FAULTS or PAGE_FAULT (historicalname), Page Faults (caption), Page_Faults (attribute name), and PAGE_FAULT (column name).

Percentage of ConnectionsThe percentage of connections that are made from the available connections. The type is integer(32-bit gauge).

The following names are defined for this attribute: PERCENTAGE_OF_CONNECITONS orPERCENTAGE (historical name), Percentage of Connections (caption), Percentage_of_Connecitons(attribute name), and PERCENTAGE (column name).

PID The process identification (PID) number on which the MongoDB instance is currently running.The type is integer (32-bit gauge).

The following names are defined for this attribute: PID (historical name), PID (caption), PID(attribute name), and PID (column name).


QueriesA counter for the number of queries that are received since the mongod instance was last started.The type is real number (rate of change between successive values) with two decimal places ofprecision.

The following names are defined for this attribute: QUERIES (historical name), Queries (caption),Queries (attribute name), and QUERIES (column name).

Total Connections CreatedA counter for the total number of connections that were created, including the connections thatare now closed. The type is integer (64-bit counter).

The following names are defined for this attribute: TOTAL_CONNECTIONS_CREATED orTOTAL_CONN (historical name), Total Connections Created (caption), Total_Connections_Created(attribute name), and TOTAL_CONN (column name).

UpdatesA counter for the number of update operations that are received since the mongod instance waslast started. The type is real number (rate of change between successive values) with two decimalplaces of precision.

The following names are defined for this attribute: UPDATES (historical name), Updates(caption), Updates (attribute name), and UPDATES (column name).

UpTimeThe time (in seconds) for which the mongos or mongod process has been active. The type isinteger (32-bit counter).

The following names are defined for this attribute: UPTIME (historical name), UpTime (caption),UpTime (attribute name), and UPTIME (column name).

Virtual Mem MBThe amount of virtual memory (in MB) that is used by the mongod process. The type is integer(32-bit gauge).

The following names are defined for this attribute: VIRTUAL_MEM_MB or VIRTUAL_ME(historical name), Virtual Mem MB (caption), Virtual_Mem_MB (attribute name), andVIRTUAL_ME (column name).

WarningsA counter for the number of warnings that were generated since the server process had started.The type is integer (32-bit counter).

The following names are defined for this attribute: WARNINGS (historical name), Warnings(caption), Warnings (attribute name), and WARNINGS (column name).

MII Copy for APM UI Two data setFiltered data rows from the Mongo Instance Information data set. Thresholds for this data set areassociated with the MongoDB component. This data set is displayed as KKJMII_COPY_FOR_APMUI_TWO in the threshold editor. A data sample is sent to the server every minuteand is maintained for 8 days by default. The default data sample consists of the first 1 rows sorted byVirtual_Mem_MB. The attributes shown in italic are visible in the UI. All attributes are available forthresholds.


Host NameThe host name of the system. The MongoDB instance for the port, which you are checking, runson this system. This attribute is a key attribute. The type is string.



















Current ConnectionsA counter for the number of connections to the database server from clients. The type is integer(32-bit counter).









MessagesA counter for the number of messages that were generated since the server process had started.The type is integer (32-bit counter).


Mongo VersionThe version of the MongoDB instance that is currently running. The type is string.








Percentage of ConnectionsThe percentage of connections that are made out of the available connections. The type is integer(32-bit gauge).















WarningsA counter for the number of warnings that were generated since the server process had started.The type is integer (32-bit counter).


MMAPv1 Details data setFunctional information about the MongoDB MMAPv1 storage engine. Thresholds for this data set areassociated with the MongoDB component. This data set is displayed as KKJ MMAPV1_DETAILS in thethreshold editor. A data sample is sent to the server every 5 minutes and is maintained for 8 days bydefault. The attributes shown in italic are visible in the UI. All attributes are available for thresholds.


Average Time(ms)The average time (in milliseconds) that the mongod processes spend in writing or flushing data


to the disk. For a storage engine other than MMAPv1, the value is N/A (not applicable). The typeis integer (64-bit gauge) with enumerated values. The following values are defined: Value ExceedsMaximum (2147483647), Value Exceeds Minimum (-2147483648), N/A (-1). Any value that doesnot have a definition here is displayed in the User Interface.

The following names are defined for this attribute: TIME_AVG_MS or AVGMS (historical name),Average Time(ms) (caption), Time_Avg_MS (attribute name), and AVGMS (column name).

CommitsThe number of transactions that are written to the journal during the last journal group commitinterval. For a storage engine other than MMAPv1, the value is N/A (not applicable). The type isinteger (64-bit gauge) with enumerated values. The following values are defined: Value ExceedsMaximum (2147483647), Value Exceeds Minimum (-2147483648), N/A (-1). Any value that doesnot have a definition here is displayed in the User Interface.

The following names are defined for this attribute: COMMITS (historical name), Commits(caption), Commits (attribute name), and COMMITS (column name).

FlushesA counter for the number of times that the database flushes all the write operations to the disk.For a storage engine other than MMAPv1, the value -1 means that the data is not applicable. Thetype is integer (difference between successive values).

The following names are defined for this attribute: FLUSHES (historical name), Flushes (caption),Flushes (attribute name), and FLUSHES (column name).

Host NameThe host name of the system on which this mongod process is running. This attribute is a keyattribute. The type is string.

The following names are defined for this attribute: HOST_NAME or HOSTNAME (historicalname), Host Name (caption), Host_Name (attribute name), and HOSTNAME (column name).

Journaled MBThe data (in MB) that is written to the journal during the last journal group commit interval. Fora storage engine other than MMAPv1, the value is N/A (not applicable). The type is integer(64-bit gauge) with enumerated values. The following values are defined: Value ExceedsMaximum (2147483647), Value Exceeds Minimum (-2147483648), N/A (-1). Any value that doesnot have a definition here is displayed in the User Interface.

The following names are defined for this attribute: JOURNALED_MB or JOURNALMB (historicalname), Journaled MB (caption), Journaled_MB (attribute name), and JOURNALMB (column name).

Last Flush Time(ms)The time (in milliseconds) that the last flush operation took to complete. For a storage engineother than MMAPv1, the value is N/A (not applicable). The type is integer (64-bit gauge) withenumerated values. The following values are defined: Value Exceeds Maximum (2147483647),Value Exceeds Minimum (-2147483648), N/A (-1). Any value that does not have a definition hereis displayed in the User Interface.

The following names are defined for this attribute: TIME_LAST_MS or LASTMS (historical name),Last Flush Time(ms) (caption), Time_Last_MS (attribute name), and LASTMS (column name).



Time PrepLogBufferThe time (in milliseconds) that is spent in preparing to write to the journal. For a storage engineother than MMAPv1, the value is N/A (not applicable). The type is integer (64-bit gauge) with


enumerated values. The following values are defined: Value Exceeds Maximum (2147483647),Value Exceeds Minimum (-2147483648), N/A (-1). Any value that does not have a definition hereis displayed in the User Interface.

The following names are defined for this attribute: TIME_PREPLOGBUFFER or PBUFFER(historical name), Time PrepLogBuffer (caption), Time_PrepLogBuffer (attribute name), andPBUFFER (column name).

Time RemapPrivateViewThe time (in milliseconds) that is spent in remapping the copy-on-write memory mapped views.For a storage engine other than MMAPv1, the value is N/A (not applicable). The type is integer(64-bit gauge) with enumerated values. The following values are defined: Value ExceedsMaximum (2147483647), Value Exceeds Minimum (-2147483648), N/A (-1). Any value that doesnot have a definition here is displayed in the User Interface.

The following names are defined for this attribute: TIME_REMAPPRIVATEVIEW orREMAPVIEW (historical name), Time RemapPrivateView (caption), Time_RemapPrivateView(attribute name), and REMAPVIEW (column name).

Time WriteToDataFilesThe time (in milliseconds) that is spent in writing to the data files after journaling. For a storageengine other than MMAPv1, the value is N/A (not applicable). The type is integer (64-bit gauge)with enumerated values. The following values are defined: Value Exceeds Maximum(2147483647), Value Exceeds Minimum (-2147483648), N/A (-1). Any value that does not have adefinition here is displayed in the User Interface.

The following names are defined for this attribute: TIME_WRITETODATAFILES or PERWRITE(historical name), Time WriteToDataFiles (caption), Time_WriteToDataFiles (attribute name), andPERWRITE (column name).

Time WriteToJournalThe time (in milliseconds) that is spent in actually writing to the journal. For a storage engineother than MMAPv1, the value is N/A (not applicable). The type is integer (64-bit gauge) withenumerated values. The following values are defined: Value Exceeds Maximum (2147483647),Value Exceeds Minimum (-2147483648), N/A (-1). Any value that does not have a definition hereis displayed in the User Interface.

The following names are defined for this attribute: TIME_WRITETOJOURNAL or WJOURNAL(historical name), Time WriteToJournal (caption), Time_WriteToJournal (attribute name), andWJOURNAL (column name).



Total Time(ms)The time (in milliseconds) that the mongod processes spend in writing or flushing data to thedisk. For a storage engine other than MMAPv1, the value -1 means that the data is notapplicable. The type is integer (difference between successive values).

The following names are defined for this attribute: TIME_TOTAL_MS or TOTALMS (historicalname), Total Time(ms) (caption), Time_Total_MS (attribute name), and TOTALMS (column name).

WriteToDataFilesMBThe data (in MB) that is written from the journal to the data files during the last journal groupcommit interval. For a storage engine other than MMAPv1, the value is N/A (not applicable).The type is integer (64-bit gauge) with enumerated values. The following values are defined:Value Exceeds Maximum (2147483647), Value Exceeds Minimum (-2147483648), N/A (-1). Anyvalue that does not have a definition here is displayed in the User Interface.


The following names are defined for this attribute: WRITETODATAFILESMB or DFILESMB(historical name), WriteToDataFilesMB (caption), WriteToDataFilesMB (attribute name), andDFILESMB (column name).

Mongo Inst DB Lock data setThe data that is gathered by running the agent.sh script with the lockInfo parameter (agent.sh lockInfo).This data set is configured for historical collection. Thresholds for this data set are associated with theMongoDB component. This data set is displayed as KKJ MONGO_INST_DB_LOCK in the thresholdeditor. A data sample is sent to the server every minute and is maintained for 8 days by default. Theattributes shown in italic are visible in the UI. All attributes are available for thresholds.


Database NameThe name of the database for which the lock information is available. This attribute is a keyattribute. The type is string.


Host NameThe host name of the system. The MongoDB process for the port, which you check for the lockinformation, runs on this system. This attribute is a key attribute. The type is string.




Time Acquiring Millis Read v3The time (in milliseconds) that is spent in waiting to acquire the read lock on the database. ForMongoDB version 3.x, or later, the value is N/A (not applicable). The type is integer (32-bitgauge) with enumerated values. The following values are defined: Value Exceeds Maximum(2147483647), Value Exceeds Minimum (-2147483648), N/A (-1). Any value that does not have adefinition here is displayed in the User Interface.

The following names are defined for this attribute: TIME_ACQUIRING_MICROS_READ_V3 orTIMEACQRE (historical name), Time Acquiring Millis Read v3 (caption),Time_Acquiring_Micros_Read_v3 (attribute name), and TIMEACQRE (column name).

Time Acquiring Millis ReadThe time (in milliseconds) that is spent in waiting to acquire the read lock on the database sincethe last data collection. The type is DEFAULT(2).

The following names are defined for this attribute: TIME_ACQUIRING_MICROS_READ orTIME_ACQRE (historical name), Time Acquiring Millis Read (caption),Time_Acquiring_Micros_Read (attribute name), and TIME_ACQRE (column name).

Time Acquiring Millis Write v3The time (in milliseconds) that is spent in waiting to acquire the write lock on the database. ForMongoDB version 3.x, or later, the value is N/A (not applicable). The type is integer (32-bitgauge) with enumerated values. The following values are defined: Value Exceeds Maximum(2147483647), Value Exceeds Minimum (-2147483648), N/A (-1). Any value that does not have adefinition here is displayed in the User Interface.


The following names are defined for this attribute: TIME_ACQUIRING_MICROS_WRITE_V3 orTIMEACQWR (historical name), Time Acquiring Millis Write v3 (caption),Time_Acquiring_Micros_Write_v3 (attribute name), and TIMEACQWR (column name).

Time Acquiring Millis WriteThe time (in milliseconds) that is spent in waiting to acquire the write lock on the database sincethe last data collection. The type is DEFAULT(2).

The following names are defined for this attribute: TIME_ACQUIRING_MICROS_WRITE orTIME_ACQWR (historical name), Time Acquiring Millis Write (caption),Time_Acquiring_Micros_Write (attribute name), and TIME_ACQWR (column name).

Time Locked Millis ReadThe time (in milliseconds) that is spent in holding the read lock on the database since the lastdata collection. The type is DEFAULT(2).

The following names are defined for this attribute: TIME_LOCKED_MICROS_READ orTIME_LOCKR (historical name), Time Locked Millis Read (caption), Time_Locked_Micros_Read(attribute name), and TIME_LOCKR (column name).

Time Locked Millis WriteThe time (in milliseconds) that is spent in holding the write lock on the database since the lastdata collection. The type is DEFAULT(2).

The following names are defined for this attribute: TIME_LOCKED_MICROS_WRITE orTIME_LOCKW (historical name), Time Locked Millis Write (caption), Time_Locked_Micros_Write(attribute name), and TIME_LOCKW (column name).



Total Time AcquiringThe total time (in milliseconds) that the database needs to acquire a lock since the last datacollection. For MongoDB version 3.x, or later, the value is N/A (not applicable). The type isDEFAULT(2).

The following names are defined for this attribute: TOTAL_TIME_ACQUIRING orTOTAL_ACQU (historical name), Total Time Acquiring (caption), Total_Time_Acquiring (attributename), and TOTAL_ACQU (column name).

Total Time LockedThe total time (in milliseconds) for which the database is locked since the last data collection. ForMongoDB version 3.x, or later, the value is N/A (not applicable). The type is DEFAULT(2).

The following names are defined for this attribute: TOTAL_TIME_LOCKED or TOTAL_LOCK(historical name), Total Time Locked (caption), Total_Time_Locked (attribute name), andTOTAL_LOCK (column name).

Time Locked Millis Read v3The time (in milliseconds) that is spent in holding the read lock on the database. For MongoDBversion 3.x, or later, the value is N/A (not applicable). The type is integer (32-bit gauge) withenumerated values. The following values are defined: Value Exceeds Maximum (2147483647),Value Exceeds Minimum (-2147483648), N/A (-1). Any value that does not have a definition hereis displayed in the User Interface.

The following names are defined for this attribute: TIME_LOCKED_MICROS_READ_V3 orTIMELOCKR (historical name), Time Locked Millis Read v3 (caption),Time_Locked_Micros_Read_v3 (attribute name), and TIMELOCKR (column name).


Time Locked Millis Write v3The time (in milliseconds) that is spent in holding the write lock the on database. For MongoDBversion 3.x, or later, the value is N/A (not applicable). The type is integer (32-bit gauge) withenumerated values. The following values are defined: Value Exceeds Maximum (2147483647),Value Exceeds Minimum (-2147483648), N/A (-1). Any value that does not have a definition hereis displayed in the User Interface.

The following names are defined for this attribute: TIME_LOCKED_MICROS_WRITE_V3 orTIMELOCKW (historical name), Time Locked Millis Write v3 (caption),Time_Locked_Micros_Write_v3 (attribute name), and TIMELOCKW (column name).

Mongo Inst IO Info data setInput and output information for mongod or mongos processes down to a database lock level. This dataset is configured for historical collection. Thresholds for this data set are associated with the MongoDBcomponent. This data set is displayed as KKJ MONGO_INST_IO_INFO in the threshold editor. A datasample is sent to the server every minute and is maintained for 8 days by default. The attributes shownin italic are visible in the UI. All attributes are available for thresholds.


BytesINA counter for the network traffic (in KB) that is received by the database since the last datacollection. The type is DEFAULT(2).


BytesOUTA counter for the network traffic (in KB) that is sent from the database since the last datacollection. The type is DEFAULT(2).


Hit RatioThe ratio of the number of hits to the number of accesses. For a router and MongoDB version 3.x,or later, the value N/A means that the data is not applicable. The type is integer (32-bit gauge)with enumerated values. The following values are defined: Value Exceeds Maximum(2147483647), Value Exceeds Minimum (-2147483648), N/A (-1). Any value that does not have adefinition here is displayed in the User Interface.

The following names are defined for this attribute: HIT_RATIO (historical name), Hit Ratio(caption), Hit_Ratio (attribute name), and HIT_RATIO (column name).

Host NameThe host name of the system. The MongoDB instance for the port, which you are checking forinput and output information, runs on this system. This attribute is a key attribute. The type isstring.


MultiTarget CursorThe total number of cursors that only target more than one shard. For MongoDB Single Instance(Type=3), the value -1 means that the data is not applicable. The type is integer (differencebetween successive values).

The following names are defined for this attribute: MULTITARGET_CURSOR or MCURSOR(historical name), MultiTarget Cursor (caption), MultiTarget_Cursor (attribute name), andMCURSOR (column name).


No Timeout CursorThe number of open cursors with the noTimeout option set to prevent timeout after a period ofinactivity. For MongoDB Single Instance (Type=3), the value N/A means that the data is notapplicable. The type is integer (32-bit gauge) with enumerated values. The following values aredefined: N/A (-1). Any value that does not have a definition here is displayed in the UserInterface.

The following names are defined for this attribute: NO_TIMEOUT_CURSOR or NCURSOR(historical name), No Timeout Cursor (caption), No_Timeout_Cursor (attribute name), andNCURSOR (column name).



Num RequestsA counter for the number of requests that are received by the database server since the last datacollection. The type is DEFAULT(2).


Number of Hits v3The number of times that the mongod process accessed the index and returned the index valuefrom memory. For MongoDB version 3.x, or later, the value N/A means that the data is notapplicable. The type is integer (32-bit gauge) with enumerated values. The following values aredefined: Value Exceeds Maximum (2147483647), Value Exceeds Minimum (-2147483648), N/A (-1).Any value that does not have a definition here is displayed in the User Interface.

The following names are defined for this attribute: NUMBER_OF_HITS_V3 or NUMHITSN(historical name), Number of Hits v3 (caption), Number_of_Hits_v3 (attribute name), andNUMHITSN (column name).

Number of HitsThe number of times that the mongod process accessed the index and returned the index valuefrom memory since the last data collection. For a router, the value -1 means that the data is notapplicable. The type is integer (difference between successive values).

The following names are defined for this attribute: NUMBER_OF_HITS or NUM_HITS (historicalname), Number of Hits (caption), Number_of_Hits (attribute name), and NUM_HITS (columnname).

Number of Misses v3The number of times that an operation attempted to access an index that was not in memory. ForMongoDB version 3.x, or later, the value N/A means that the data is not applicable. The type isinteger (32-bit gauge) with enumerated values. The following values are defined: Value ExceedsMaximum (2147483647), Value Exceeds Minimum (-2147483648), N/A (-1). Any value that doesnot have a definition here is displayed in the User Interface.

The following names are defined for this attribute: NUMBER_OF_MISSES_V3 or NUMMISSN(historical name), Number of Misses v3 (caption), Number_of_Misses_v3 (attribute name), andNUMMISSN (column name).

Number of MissesThe number of times that an operation attempted to access an index that was not in memorysince the last data collection. For a router, the value -1 means that the data is not applicable. Thetype is integer (difference between successive values).


The following names are defined for this attribute: NUMBER_OF_MISSES or NUM_MISSES(historical name), Number of Misses (caption), Number_of_Misses (attribute name), andNUM_MISSES (column name).

Number of Resets v3The number of times that the index counters were reset since the database was last restarted. ForMongoDB version 3.x, or later, the value N/A means that the data is not applicable. The type isinteger (32-bit gauge) with enumerated values. The following values are defined: Value ExceedsMaximum (2147483647), Value Exceeds Minimum (-2147483648), N/A (-1). Any value that doesnot have a definition here is displayed in the User Interface.

The following names are defined for this attribute: NUMBER_OF_RESETS_V3 or NUMRESETN(historical name), Number of Resets v3 (caption), Number_of_Resets_v3 (attribute name), andNUMRESETN (column name).

Number of ResetsThe number of times that the index counters were reset since the last data collection. The type isinteger (difference between successive values).

The following names are defined for this attribute: NUMBER_OF_RESETS or NUM_RESETS(historical name), Number of Resets (caption), Number_of_Resets (attribute name), andNUM_RESETS (column name).

Op CountThe total number of current operations in the oplog buffer. For a router, the value -1 means thatthe data is not applicable. This attribute is a key attribute. The type is integer (32-bit gauge).

The following names are defined for this attribute: OP_COUNT (historical name), Op Count(caption), Op_Count (attribute name), and OP_COUNT (column name).

Page FaultsA counter for the number of page faults since the last data collection that require disk operations.For a router, the value N/A means that the data is not applicable. The type is integer (differencebetween successive values).


Pinned The number of pinned open cursors. For MongoDB Single Instance (Type=3), the value N/Ameans that the data is not applicable. The type is integer (32-bit gauge) with enumerated values.The following values are defined: N/A (-1). Any value that does not have a definition here isdisplayed in the User Interface.

The following names are defined for this attribute: PINNED (historical name), Pinned (caption),Pinned (attribute name), and PINNED (column name).

Single TargetThe total number of cursors that only target a single shard. For MongoDB Single Instance(Type=3), the value -1 means that the data is not applicable. The type is integer (differencebetween successive values).

The following names are defined for this attribute: SINGLE_TARGET or SCURSOR (historicalname), Single Target (caption), Single_Target (attribute name), and SCURSOR (column name).

Storage EngineThe name of the storage engine that is used for a particular node. For a router, the value -1means that the data is not applicable. This attribute is a key attribute. The type is string.

The following names are defined for this attribute: STORAGE_ENGINE or STORAGENG(historical name), Storage Engine (caption), Storage_Engine (attribute name), and STORAGENG(column name).


Timeout CursorThe total number of cursors that have timed out since the server process started. For MongoDBSingle Instance (Type=3), the value -1 means that the data is not applicable. The type is integer(difference between successive values).

The following names are defined for this attribute: TIMEOUT_CURSOR or CURSOR (historicalname), Timeout Cursor (caption), Timeout_Cursor (attribute name), and CURSOR (column name).



Total Active ConnectionsThe total number of active client connections to the database. For a router, the value N/A meansthat the data is not applicable. The type is integer (32-bit gauge) with enumerated values. Thefollowing values are defined: Value Exceeds Maximum (2147483647), Value Exceeds Minimum(-2147483648), N/A (-1). Any value that does not have a definition here is displayed in the UserInterface.

The following names are defined for this attribute: TOTAL_ACTIVE_CONNECTIONS orTOT_ACT_QU (historical name), Total Active Connections (caption), Total_Active_Connections(attribute name), and TOT_ACT_QU (column name).

Total Active ReadersThe total number of active client connections that perform read operations. For a router, the valueN/A means that the data is not applicable. The type is integer (32-bit gauge) with enumeratedvalues. The following values are defined: Value Exceeds Maximum (2147483647), Value ExceedsMinimum (-2147483648), N/A (-1). Any value that does not have a definition here is displayed inthe User Interface.

The following names are defined for this attribute: TOTAL_ACTIVE_READERS or TOT_ACT_RE(historical name), Total Active Readers (caption), Total_Active_Readers (attribute name), andTOT_ACT_RE (column name).

Total Active WritersThe total number of active client connections that perform write operations. For a router, thevalue N/A means that the data is not applicable. The type is integer (32-bit gauge) withenumerated values. The following values are defined: Value Exceeds Maximum (2147483647),Value Exceeds Minimum (-2147483648), N/A (-1). Any value that does not have a definition hereis displayed in the User Interface.

The following names are defined for this attribute: TOTAL_ACTIVE_WRITERS or TOT_ACT_WR(historical name), Total Active Writers (caption), Total_Active_Writers (attribute name), andTOT_ACT_WR (column name).

Total Current QueueThe total number of queued operations that are waiting for a lock. For a router, the value N/Ameans that the data is not applicable. The type is integer (64-bit gauge) with enumerated values.The following values are defined: Value Exceeds Maximum (2147483647), Value ExceedsMinimum (-2147483648), N/A (-1). Any value that does not have a definition here is displayed inthe User Interface.

The following names are defined for this attribute: TOTAL_CURRENT_QUEUE or TOTAL_CURR(historical name), Total Current Queue (caption), Total_Current_Queue (attribute name), andTOTAL_CURR (column name).

Total Current ReadersThe total number of operations that are waiting for the read lock. For a router, the value N/Ameans that the data is not applicable. The type is integer (64-bit gauge) with enumerated values.


The following values are defined: Value Exceeds Maximum (2147483647), Value ExceedsMinimum (-2147483648), N/A (-1). Any value that does not have a definition here is displayed inthe User Interface.

The following names are defined for this attribute: TOTAL_CURRENT_READERS orTOT_CUR_RE (historical name), Total Current Readers (caption), Total_Current_Readers (attributename), and TOT_CUR_RE (column name).

Total Current WritersThe total number of operations that are waiting for the write lock. For a router, the value N/Ameans that the data is not applicable. The type is integer (32-bit gauge) with enumerated values.The following values are defined: Value Exceeds Maximum (2147483647), Value ExceedsMinimum (-2147483648), N/A (-1). Any value that does not have a definition here is displayed inthe User Interface.

The following names are defined for this attribute: TOTAL_CURRENT_WRITERS orTOT_CUR_WR (historical name), Total Current Writers (caption), Total_Current_Writers (attributename), and TOT_CUR_WR (column name).

Total Open CursorThe number of cursors that MongoDB maintains for clients. For MongoDB Single Instance(Type=3), the value N/A means that the data is not applicable. The type is integer (32-bit gauge)with enumerated values. The following values are defined: N/A (-1). Any value that does nothave a definition here is displayed in the User Interface.

The following names are defined for this attribute: TOTAL_OPEN_CURSOR or OCURSOR(historical name), Total Open Cursor (caption), Total_Open_Cursor (attribute name), andOCURSOR (column name).

Average MS of FlushThe average time (in milliseconds) that is required to flush the data to the disk. The value N/Ameans that the data is not applicable. The type is integer (32-bit gauge) with enumerated values.The following values are defined: Value Exceeds Maximum (2147483647), Value ExceedsMinimum (-2147483648), N/A (0). Any value that does not have a definition here is displayed inthe User Interface.

The following names are defined for this attribute: AVERAGE_MS_OF_FLUSH or AVERAGE_MS(historical name), Average MS of Flush (caption), Average_MS_of_Flush (attribute name), andAVERAGE_MS (column name).

Background FlushesThe number of times that the database flushed all writes to the disk since the last data collection.For a router, the value -1 means that the data is not applicable. The type is integer (differencebetween successive values).

The following names are defined for this attribute: BACKGROUND_FLUSHES orBACKGROUND (historical name), Background Flushes (caption), Background_Flushes (attributename), and BACKGROUND (column name).

Background Flushes v3The number of times that the database flushed all writes to the disk. For a storage engine otherthan MMAPv1, the value N/A means that the data is not applicable. The type is integer (32-bitgauge) with enumerated values. The following values are defined: Value Exceeds Maximum(2147483647), Value Exceeds Minimum (-2147483648), N/A (-1). Any value that does not have adefinition here is displayed in the User Interface.

The following names are defined for this attribute: BACKGROUND_FLUSHES_V3 or BACKN(historical name), Background Flushes v3 (caption), Background_Flushes_v3 (attribute name), andBACKN (column name).


Batches NumThe total number of batches across all databases. For a router, the value -1 means that the data isnot applicable. The type is integer (32-bit gauge).

The following names are defined for this attribute: BATCHES_NUM or BATCHES_NU (historicalname), Batches Num (caption), Batches_Num (attribute name), and BATCHES_NU (columnname).

Batches Total MSThe time (in milliseconds) that is spent to apply operations to the oplog. For a router, the value -1means that the data is not applicable. The type is integer (32-bit gauge).

The following names are defined for this attribute: BATCHES_TOTAL_MS or BATCHES_TO(historical name), Batches Total MS (caption), Batches_Total_MS (attribute name), andBATCHES_TO (column name).







Global Lock TimeThe time (in microseconds) for which the database held the global lock since the last datacollection. For a router, the value -1 means that the data is not applicable. For a single mongodprocess, the value zero (0) means that the data is not available. The type is DEFAULT(2).

The following names are defined for this attribute: GLOBAL_LOCK_TIME or GLOBAL_LOC(historical name), Global Lock Time (caption), Global_Lock_Time (attribute name), andGLOBAL_LOC (column name).

Global Lock Time MSThe time (in milliseconds) that is required to transfer the global lock. The type is integer (64-bitgauge).

The following names are defined for this attribute: GLOBAL_LOCK_TIME_MS or GLOBAL_LO0(historical name), Global Lock Time MS (caption), Global_Lock_Time_MS (attribute name), andGLOBAL_LO0 (column name).




Is MasterIndicates whether the mongod is a secondary. For a router, the value -1 means that the data is notapplicable. The type is string.

The following names are defined for this attribute: IS_MASTER (historical name), Is Master(caption), Is_Master (attribute name), and IS_MASTER (column name).

Last Flush FinishedThe date and time when the last flush operation was completed. For a router, the value -1 meansthat the data is not applicable. The value should be in date format. The type is string.

The following names are defined for this attribute: LAST_FLUSH_FINISHED or LAST_FLUSH(historical name), Last Flush Finished (caption), Last_Flush_Finished (attribute name), andLAST_FLUSH (column name).

Last MS FlushThe time (in milliseconds) that was required for the last flush operation. For a router, the value -1means that the data is not applicable. The type is integer (32-bit gauge).

The following names are defined for this attribute: LAST_MS_FLUSH or LAST_MS_FL (historicalname), Last MS Flush (caption), Last_MS_Flush (attribute name), and LAST_MS_FL (columnname).

Miss RatioThe ratio of hits to misses. For a router, the value N/A means that the data is not applicable. Thetype is integer (32-bit gauge) with enumerated values. The following values are defined: ValueExceeds Maximum (2147483647), Value Exceeds Minimum (-2147483648), N/A (-1). Any valuethat does not have a definition here is displayed in the User Interface.

The following names are defined for this attribute: MISS_RATIO (historical name), Miss Ratio(caption), Miss_Ratio (attribute name), and MISS_RATIO (column name).

Number of AccessesThe number of times that the operations accessed the indexes since the last data collection. For arouter, the value -1 means that the data is not applicable. The type is integer (difference betweensuccessive values).

The following names are defined for this attribute: NUMBER_OF_ACCESSES or NUM_ACCESS(historical name), Number of Accesses (caption), Number_of_Accesses (attribute name), andNUM_ACCESS (column name).








SecondaryIndicates whether the mongod is a master, or a primary. For a router, the value -1 means that thedata is not applicable. The type is string.

The following names are defined for this attribute: SECONDARY (historical name), Secondary(caption), Secondary (attribute name), and SECONDARY (column name).

Set NameThe name of the set to which the server belongs. For a router or a single instance, the value -1means that the data is not applicable. The type is string.

The following names are defined for this attribute: SET_NAME (historical name), Set Name(caption), Set_Name (attribute name), and SET_NAME (column name).

Total MS of FlushesThe time (in milliseconds) that the mongod processes spent in writing or flushing the data to thedisk since the last data collection. For a router, the value -1 means that the data is not applicable.The type is integer (difference between successive values).

The following names are defined for this attribute: TOTAL_MS_OF_FLUSHES or TOTAL_MS_O(historical name), Total MS of Flushes (caption), Total_MS_of_Flushes (attribute name), andTOTAL_MS_O (column name).

Total Number of OperationsThe total number of items that are inserted into the oplog since the last data collection. For arouter, the value -1 means that the data is not applicable. The type is integer (difference betweensuccessive values).

The following names are defined for this attribute: TOTAL_NUMBER_OF_OPERATIONS orTOTAL_NUMB (historical name), Total Number of Operations (caption),Total_Number_of_Operations (attribute name), and TOTAL_NUMB (column name).





Mongo Instance Information data setFunctional information for a mongod or mongos instance. Provides port connection, page fault (Linuxonly), command numbers, and memory usage by the process. Thresholds for this data set are associatedwith the MongoDB component. This data set is displayed as KKJ MONGO_INSTANCE_INFORMATIONin the threshold editor. A data sample is sent to the server every minute and is maintained for 8 days bydefault. The attributes shown in italic are visible in the UI. All attributes are available for thresholds.





CommandsA counter for the number of commands that are issued to the mongod instance since the instancewas last started. The type is DEFAULT(2).


Current ConnectionsA counter for the number of connections to the database server from the clients. The type isinteger (32-bit counter).


Deletes A counter for the number of delete operations on the mongod instance since the instance was laststarted. The type is real number (rate of change between successive values) with two decimalplaces of precision.


GetmoreA counter for the number of getmore operations on the mongod instance since the instance waslast started. The type is real number (rate of change between successive values) with two decimalplaces of precision.


Host NameThe host name of the system. The MongoDB process for the port, which you are checking, runson this system. This attribute is a key attribute. The type is string.


Inserts A counter for the number of insert operations on the mongod instance since the instance was laststarted. The type is real number (rate of change between successive values) with two decimalplaces of precision.


Mongo VersionVersion of the MongoDB instance that is currently running. The type is string.







Percentage of ConnectionsThe percentage of connections that are made out of the available connections. The type is integer(32-bit gauge).




QueriesA counter for the number of queries on the mongod instance since the instance was last started.The type is real number (rate of change between successive values) with two decimal places ofprecision.






UpdatesA counter for the number of update operations on the mongod instance since the instance waslast started. The type is real number (rate of change between successive values) with two decimalplaces of precision.

The following names are defined for this attribute: UPDATES (historical name), Updates (caption),Updates (attribute name), and UPDATES (column name).






WarningsA counter for the number of warnings that were generated since the server process started. Thetype is integer (32-bit counter).








MessagesA counter for the number of messages that were generated since the server process started. Thetype is integer (32-bit counter).








Mongod Listing data setList of all mongod instances that are connected to the router through their respective replica sets, a singlereplication set, or a single instance. This list includes the instances with online status (true or false),designation (primary or secondary), ping in milliseconds, and operational information about the replicaset. Thresholds for this data set are associated with the MongoDB component. This data set is displayed


as KKJ MONGOD_LISTING in the threshold editor. A data sample is sent to the server every minute andis maintained for 8 days by default. The attributes shown in italic are visible in the UI. All attributes areavailable for thresholds.


Error msgDisplays an error message if there are no entries in the oplog. For MongoDB Single Instance(Type=3), the value is N/A (not applicable). The type is integer (32-bit gauge) with enumeratedvalues. The following values are defined: Value Exceeds Maximum (2147483647), Value ExceedsMinimum (-2147483648), N/A (-1). Any value that does not have a definition here is displayed inthe User Interface.

The following names are defined for this attribute: ERROR_MSG or ERRMSG (historical name),Error msg (caption), Error_msg (attribute name), and ERRMSG (column name).

Host and PortThe host name and port number as a single value. The type is string.

The following names are defined for this attribute: HOSTANDPORT or HOSTPORT (historicalname), Host and Port (caption), HostAndPort (attribute name), and HOSTPORT (column name).

Host The host name or IP address of the system on which the MongoDB process is running. Thisattribute is a key attribute. The type is string.

The following names are defined for this attribute: HOST or HOST0 (historical name), Host(caption), Host (attribute name), and HOST0 (column name).

Last OperationDisplays the time stamp for the last (that is the latest) operation in the oplog. For MongoDBSingle Instance (Type=3), the value is N/A (not applicable). The type is string with enumeratedvalues. The following values are defined: N/A (-1). Any value that does not have a definitionhere is displayed in the User Interface.

The following names are defined for this attribute: LAST_OPERATION or LASTOP (historicalname), Last Operation (caption), Last_Operation (attribute name), and LASTOP (column name).

Name The name of the replication set, process type, or single instance. The type is string.

The following names are defined for this attribute: NAME (historical name), Name (caption),Name (attribute name), and NAME (column name).



Oplog WindowThe time interval (in seconds) between the oldest and the latest entries in the oplog. This valueusually corresponds to the approximate amount of time that is available in the replication oplogof the primary. For MongoDB Single Instance (Type=3), the value is N/A (not applicable). Thetype is integer (32-bit gauge) with enumerated values. The following values are defined: ValueExceeds Maximum (2147483647), Value Exceeds Minimum (-2147483648), N/A (-1). Any valuethat does not have a definition here is displayed in the User Interface.

The following names are defined for this attribute: OPLOG_WINDOW or OPLOG (historicalname), Oplog Window (caption), Oplog_Window (attribute name), and OPLOG (column name).

Percentage UsedThe total percentage of space that is used by the oplog.This value may exceed beyond 100 percentif the space used for oplog is greater than the space allocated, in which case specify an opLogsize sufficient for the required operation in oplog. For MongoDB Single Instance (Type=3), thevalue is N/A (not applicable). The type is integer (32-bit gauge) with enumerated values. The


following values are defined: Value Exceeds Maximum (2147483647), Value Exceeds Minimum(-2147483648), N/A (-1). Any value that does not have a definition here is displayed in the UserInterface.

The following names are defined for this attribute: PERCENTAGE_USED or PERSIZE (historicalname), Percentage Used (caption), Percentage_Used (attribute name), and PERSIZE (column name).

Port The port number of the listed mongod process. This attribute is a key attribute. The type isinteger (32-bit gauge).

The following names are defined for this attribute: PORT (historical name), Port (caption), Port(attribute name), and PORT (column name).

Replication LagThe timestamp (in minutes) for the last (that is the latest) operation in the oplog. For MongoDBSingle Instance (Type=3), the value is N/A (not applicable). The type is integer (32-bit gauge)with enumerated values. The following values are defined: Value Exceeds Maximum(2147483647), Value Exceeds Minimum (-2147483648), N/A (-1). Any value that does not have adefinition here is displayed in the User Interface.

The following names are defined for this attribute: REPLICATION_LAG or REPLLAG (historicalname), Replication Lag (caption), Replication_Lag (attribute name), and REPLLAG (column name).

Role The role of the shard member, such as primary, secondary, or an arbiter. The type is integer(32-bit gauge) with enumerated values. The following values are defined: Value ExceedsMaximum (2147483647), Value Exceeds Minimum (-2147483648), Startup (0), Primary (1),Secondary (2), Recovering (3), Fatal (4), Startup2 (5), Unknown (6), Arbiter (7), Down (8), Rollback(9), Shunned (10). Any value that does not have a definition here is displayed in the UserInterface.

The following names are defined for this attribute: ROLE (historical name), Role (caption), Role(attribute name), and ROLE (column name).

Status StringIndicates whether the mongod process is online or offline. The type is string with enumeratedvalues. The following values are defined: Online (1), Offline (0). Any value that does not have adefinition here is displayed in the User Interface.

The following names are defined for this attribute: STATUSSTRING or STATUSSTRI (historicalname), Status String (caption), StatusString (attribute name), and STATUSSTRI (column name).

Status Indicates the online or offline status of the shards with a numeric back end. The type is integer(32-bit gauge) with enumerated values. The following values are defined: Value ExceedsMaximum (2147483647), Value Exceeds Minimum (-2147483648), Online (1), Offline (0), Unknown(-1). Any value that does not have a definition here is displayed in the User Interface.

The following names are defined for this attribute: STATUS (historical name), Status (caption),Status (attribute name), and STATUS (column name).

Target pageIndicates whether the setup is a replica setup. For MongoDB Single Instance (Type=3), the valueis N/A (not applicable). The type is string with enumerated values. The following values aredefined: page notReplicaSet (-1). Any value that does not have a definition here is displayed inthe User Interface.

The following names are defined for this attribute: TARGET_PAGE or TARGET (historical name),Target page (caption), Target_page (attribute name), and TARGET (column name).




Total SizeThe total size (in MB) of the oplog. For MongoDB Single Instance (Type=3), the value is N/A (notapplicable). The type is integer (32-bit gauge) with enumerated values. The following values aredefined: Value Exceeds Maximum (2147483647), Value Exceeds Minimum (-2147483648), N/A (-1).Any value that does not have a definition here is displayed in the User Interface.

The following names are defined for this attribute: TOTAL_SIZE or TSIZE (historical name), TotalSize (caption), Total_Size (attribute name), and TSIZE (column name).

Used sizeThe total amount of space (in MB) that is used by the oplog. For MongoDB Single Instance(Type=3), the value is N/A (not applicable). The type is integer (32-bit gauge) with enumeratedvalues. The following values are defined: Value Exceeds Maximum (2147483647), Value ExceedsMinimum (-2147483648), N/A (-1). Any value that does not have a definition here is displayed inthe User Interface.

The following names are defined for this attribute: USED_SIZE or USIZE (historical name), Usedsize (caption), Used_size (attribute name), and USIZE (column name).

IP AddressThe IP address where the component is running. The type is string.

The following names are defined for this attribute: IP_ADDRESS or IPADDR (historical name), IPAddress (caption), IP_Address (attribute name), and IPADDR (column name).

UptimeThe time (in seconds) for which the replica member was online. The type is string.

The following names are defined for this attribute: UPTIME (historical name), Uptime (caption),Uptime (attribute name), and UPTIME (column name).

MongoDB Locks data setThe lock summary for all mongod instances of MongoDB version 3 and later. This data set is configuredfor historical collection. Thresholds for this data set are associated with the MongoDB component. Thisdata set is displayed as KKJ MONGODB_LOCKS in the threshold editor. A data sample is sent to theserver every minute and is maintained for 8 days by default. The attributes shown in italic are visible inthe UI. All attributes are available for thresholds.


Acquiring CountA counter for the total number of times that the lock was acquired in all the lock type modessince the last data collection. For MongoDB version 2.x, the value -1 means that the data is notapplicable. The type is DEFAULT(2).

The following names are defined for this attribute: ACQUIRING_COUNT or ACOUNT (historicalname), Acquiring Count (caption), Acquiring_Count (attribute name), and ACOUNT (columnname).

Acquiring Deadlock CountA counter for the total number of times that the lock acquisitions encountered deadlocks since thelast data collection. For MongoDB version 2.x, the value -1 means that the data is not applicable.The type is DEFAULT(2).

The following names are defined for this attribute: ACQUIRING_DEADLOCK_COUNT orADCOUNT (historical name), Acquiring Deadlock Count (caption), Acquiring_Deadlock_Count(attribute name), and ADCOUNT (column name).


Acquiring Shared CountA counter for the number of times the Shared (S) lock mode was acquired for a particular locktype. For MongoDB version 2.x, the value -1 means that the data is not applicable. The type isDEFAULT(2).

The following names are defined for this attribute: ACQUIRING_SHARED_COUNT orACOUNTS (historical name), Acquiring Shared Count (caption), Acquiring_Shared_Count (attributename), and ACOUNTS (column name).

Acquiring Wait CountA counter for the total number of times that the lock acquisitions encountered waits because thelocks were held in a conflicting mode since the last data collection. For MongoDB version 2.x, thevalue -1 means that the data is not applicable. The type is DEFAULT(2).

The following names are defined for this attribute: ACQUIRING_WAIT_COUNT or AWCOUNT(historical name), Acquiring Wait Count (caption), Acquiring_Wait_Count (attribute name), andAWCOUNT (column name).

Host NameThe name of host on which the mongod or mongos process runs. This attribute is a key attribute.The type is string.

The following names are defined for this attribute: HOST_NAME or HOST (historical name), HostName (caption), Host_Name (attribute name), and HOST (column name).

Lock typeThe type of the lock. The value N/A means data is not applicable. This attribute is a keyattribute. The type is string with enumerated values. The following values are defined: N/A (-1).Any value that does not have a definition here is displayed in the User Interface.

The following names are defined for this attribute: LOCK_TYPE or LOCKTYPE (historical name),Lock type (caption), Lock_type (attribute name), and LOCKTYPE (column name).



Time AcquiringMicrosThe total cumulative wait time (in microseconds) for the lock acquisitions since the last datacollection. For MongoDB version 2.x, the value -1 means that the data is not applicable. The typeis DEFAULT(2).

The following names are defined for this attribute: TIME_ACQUIRINGMICROS or AWTIME(historical name), Time AcquiringMicros (caption), Time_AcquiringMicros (attribute name), andAWTIME (column name).



Acquiring Exclusive CountA counter for the number of times that the Exclusive (X) lock mode was acquired for a particularlock type. For MongoDB version 2.x, the value -1 means that the data is not applicable. The typeis DEFAULT(2).

The following names are defined for this attribute: ACQUIRING_EXCLUSIVE_COUNT orACOUNTE (historical name), Acquiring Exclusive Count (caption), Acquiring_Exclusive_Count(attribute name), and ACOUNTE (column name).


Acquiring IS CountA counter for the number of times that the Intent Shared (IS) lock mode was acquired for aparticular lock type. For MongoDB version 2.x, the value -1 means that the data is not applicable.The type is DEFAULT(2).

The following names are defined for this attribute: ACQUIRING_IS_COUNT or ACOUNTIS(historical name), Acquiring IS Count (caption), Acquiring_IS_Count (attribute name), andACOUNTIS (column name).

Acquiring IX CountA counter for the number of times that the Intent Exclusive (IX) lock mode was acquired for aparticular lock type. For MongoDB version 2.x, the value -1 means that the data is not applicable.The type is DEFAULT(2).

The following names are defined for this attribute: ACQUIRING_IX_COUNT or ACOUNTIX(historical name), Acquiring IX Count (caption), Acquiring_IX_Count (attribute name), andACOUNTIX (column name).

Acquiring Wait Count ISA counter for the number of times that the Intent Shared (IS) lock mode acquisition encounteredwaits for a particular lock type. For MongoDB version 2.x, the value -1 means that the data is notapplicable. The type is DEFAULT(2).

The following names are defined for this attribute: ACQUIRING_WAIT_COUNT_IS or AWCNTIS(historical name), Acquiring Wait Count IS (caption), Acquiring_Wait_Count_IS (attribute name),and AWCNTIS (column name).

Acquiring Wait Count IXA counter for the number of times that the Intent Exclusive (IX) lock acquisition encounteredwaits for a particular lock type. For MongoDB version 2.x, the value -1 means that the data is notapplicable. The type is DEFAULT(2).

The following names are defined for this attribute: ACQUIRING_WAIT_COUNT_IX or AWCNTIX(historical name), Acquiring Wait Count IX (caption), Acquiring_Wait_Count_IX (attribute name),and AWCNTIX (column name).

Acquiring Wait Count SA counter for the number of times that the Shared (S) lock mode acquisition encountered waitsfor a particular lock type. For MongoDB version 2.x, the value -1 means that the data is notapplicable. The type is DEFAULT(2).

The following names are defined for this attribute: ACQUIRING_WAIT_COUNT_S or AWCNTS(historical name), Acquiring Wait Count S (caption), Acquiring_Wait_Count_S (attribute name),and AWCNTS (column name).

Acquiring Wait Count XA counter for the number of times that the Exclusive (X) lock mode acquisition encountered waitsfor a particular lock type. For MongoDB version 2.x, the value -1 means that the data is notapplicable. The type is DEFAULT(2).

The following names are defined for this attribute: ACQUIRING_WAIT_COUNT_X or AWCNTX(historical name), Acquiring Wait Count X (caption), Acquiring_Wait_Count_X (attribute name),and AWCNTX (column name).

Time AcquiringMicros ISThe cumulative wait time (in microseconds) for the lock acquisitions in the Intent Shared (IS)mode. For MongoDB version 2.x, the value -1 means that the data is not applicable. The type isDEFAULT(2).

The following names are defined for this attribute: TIME_ACQUIRINGMICROS_IS or ATIMEIS(historical name), Time AcquiringMicros IS (caption), Time_AcquiringMicros_IS (attribute name),and ATIMEIS (column name).


Time AcquiringMicros IXThe cumulative wait time (in microseconds) for the lock acquisitions in the Intent Exclusive (IX)mode. For MongoDB version 2.x, the value -1 means that the data is not applicable. The type isDEFAULT(2).

The following names are defined for this attribute: TIME_ACQUIRINGMICROS_IX or ATIMEIX(historical name), Time AcquiringMicros IX (caption), Time_AcquiringMicros_IX (attribute name),and ATIMEIX (column name).

Time AcquiringMicros SThe cumulative wait time (in microseconds) for the lock acquisitions in the Shared (S) lock mode.For MongoDB version 2.x, the value -1 means that the data is not applicable. The type isDEFAULT(2).

The following names are defined for this attribute: TIME_ACQUIRINGMICROS_S or ATIMES(historical name), Time AcquiringMicros S (caption), Time_AcquiringMicros_S (attribute name),and ATIMES (column name).

Time AcquiringMicros XThe cumulative wait time (in microseconds) for the lock acquisitions in the Exclusive (X) lockmode. For MongoDB version 2.x, the value -1 means that the data is not applicable. The type isDEFAULT(2).

The following names are defined for this attribute: TIME_ACQUIRINGMICROS_X or ATIMEX(historical name), Time AcquiringMicros X (caption), Time_AcquiringMicros_X (attribute name),and ATIMEX (column name).

Performance Object Status data setThe Performance Object Status data set contains information that reflects the status of other data sets soyou can see the status of all performance objects that make up this application all at once. Each of theseother performance data sets is represented by a row in this table (or other type of view). The status for adata set reflects the result of the last attempt to collect data for that data set, so you can see whether theagent is collecting data correctly. Unlike other data sets, the Performance Object Status data set does notreflect the state of the monitored application. This data set is most often used to determine why data isnot available for one of the performance data sets.


Average Collection DurationThe average duration of all data collections of this group in seconds. The type is real number(32-bit counter) with two decimal places of precision with enumerated values. The followingvalues are defined: NO DATA (-100). Any value that does not have a definition here is displayedin the User Interface.

The following names are defined for this attribute: AVERAGE_COLLECTION_DURATION orCOLAVGD (historical name), Average Collection Duration (caption), Average_Collection_Duration(attribute name), and COLAVGD (column name).

Cache Hit PercentThe percentage of external data requests for this group that were satisfied from the cache. Thetype is real number (32-bit counter) with two decimal places of precision.

The following names are defined for this attribute: CACHE_HIT_PERCENT or CACHPCT(historical name), Cache Hit Percent (caption), Cache_Hit_Percent (attribute name), andCACHPCT (column name).

Cache HitsThe number of times an external data request for this group was satisfied from the cache. Thetype is integer (32-bit counter).


The following names are defined for this attribute: CACHE_HITS or CACHEHT (historicalname), Cache Hits (caption), Cache_Hits (attribute name), and CACHEHT (column name).

Cache MissesThe number of times an external data request for this group was not available in the cache. Thetype is integer (32-bit counter).

The following names are defined for this attribute: CACHE_MISSES or CACHEMS (historicalname), Cache Misses (caption), Cache_Misses (attribute name), and CACHEMS (column name).

Error CodeThe error code associated with the query. The type is integer with enumerated values. Thefollowing values are defined: NO ERROR (0), GENERAL ERROR (1), OBJECT NOT FOUND (2),COUNTER NOT FOUND (3), NAMESPACE ERROR (4), OBJECT CURRENTLY UNAVAILABLE(5), COM LIBRARY INIT FAILURE (6), SECURITY INIT FAILURE (7), PROXY SECURITYFAILURE (9), NO INSTANCES RETURNED (10), ASSOCIATOR QUERY FAILED (11),REFERENCE QUERY FAILED (12), NO RESPONSE RECEIVED (13), CANNOT FIND JOINEDQUERY (14), CANNOT FIND JOIN ATTRIBUTE IN QUERY 1 RESULTS (15), CANNOT FINDJOIN ATTRIBUTE IN QUERY 2 RESULTS (16), QUERY 1 NOT A SINGLETON (17), QUERY 2NOT A SINGLETON (18), NO INSTANCES RETURNED IN QUERY 1 (19), NO INSTANCESRETURNED IN QUERY 2 (20), CANNOT FIND ROLLUP QUERY (21), CANNOT FIND ROLLUPATTRIBUTE (22), FILE OFFLINE (23), NO HOSTNAME (24), MISSING LIBRARY (25),ATTRIBUTE COUNT MISMATCH (26), ATTRIBUTE NAME MISMATCH (27), COMMON DATAPROVIDER NOT STARTED (28), CALLBACK REGISTRATION ERROR (29), MDL LOAD ERROR(30), AUTHENTICATION FAILED (31), CANNOT RESOLVE HOST NAME (32), SUBNODEUNAVAILABLE (33), SUBNODE NOT FOUND IN CONFIG (34), ATTRIBUTE ERROR (35),CLASSPATH ERROR (36), CONNECTION FAILURE (37), FILTER SYNTAX ERROR (38), FILENAME MISSING (39), SQL QUERY ERROR (40), SQL FILTER QUERY ERROR (41), SQL DBQUERY ERROR (42), SQL DB FILTER QUERY ERROR (43), PORT OPEN FAILED (44), ACCESSDENIED (45), TIMEOUT (46), NOT IMPLEMENTED (47), REQUESTED A BAD VALUE (48),RESPONSE TOO BIG (49), GENERAL RESPONSE ERROR (50), SCRIPT NONZERO RETURN(51), SCRIPT NOT FOUND (52), SCRIPT LAUNCH ERROR (53), CONF FILE DOES NOT EXIST(54), CONF FILE ACCESS DENIED (55), INVALID CONF FILE (56), EIF INITIALIZATIONFAILED (57), CANNOT OPEN FORMAT FILE (58), FORMAT FILE SYNTAX ERROR (59),REMOTE HOST UNAVAILABLE (60), EVENT LOG DOES NOT EXIST (61), PING FILE DOESNOT EXIST (62), NO PING DEVICE FILES (63), PING DEVICE LIST FILE MISSING (64), SNMPMISSING PASSWORD (65), DISABLED (66), URLS FILE NOT FOUND (67), XML PARSE ERROR(68), NOT INITIALIZED (69), ICMP SOCKETS FAILED (70), DUPLICATE CONF FILE (71),DELETED CONFIGURATION (72). Any value that does not have a definition here is displayed inthe User Interface.

The following names are defined for this attribute: ERROR_CODE or ERRCODE (historicalname), Error Code (caption), Error_Code (attribute name), and ERRCODE (column name).

Intervals SkippedThe number of times a background data collection for this group was skipped because theprevious collection was still running when the next one was due to start. The type is integer(32-bit counter).

The following names are defined for this attribute: INTERVALS_SKIPPED or INTSKIP (historicalname), Intervals Skipped (caption), Intervals_Skipped (attribute name), and INTSKIP (columnname).

Last Collection DurationThe duration of the most recently completed data collection of this group in seconds. The type isreal number (32-bit counter) with two decimal places of precision.

The following names are defined for this attribute: LAST_COLLECTION_DURATION orCOLDURA (historical name), Last Collection Duration (caption), Last_Collection_Duration(attribute name), and COLDURA (column name).


Last Collection FinishedThe most recent time a data collection of this group finished. The type is timestamp withenumerated values. The following values are defined: NOT COLLECTED (0691231190000000),NOT COLLECTED (0000000000000001). Any value that does not have a definition here isdisplayed in the User Interface.

The following names are defined for this attribute: LAST_COLLECTION_FINISHED or COLFINI(historical name), Last Collection Finished (caption), Last_Collection_Finished (attribute name),and COLFINI (column name).

Last Collection StartThe most recent time a data collection of this group started. The type is timestamp withenumerated values. The following values are defined: NOT COLLECTED (0691231190000000),NOT COLLECTED (0000000000000001). Any value that does not have a definition here isdisplayed in the User Interface.

The following names are defined for this attribute: LAST_COLLECTION_START or COLSTRT(historical name), Last Collection Start (caption), Last_Collection_Start (attribute name), andCOLSTRT (column name).



Number of CollectionsThe number of data collections for this group since the agent started. The type is integer (32-bitcounter).

The following names are defined for this attribute: NUMBER_OF_COLLECTIONS or NUMCOLL(historical name), Number of Collections (caption), Number_of_Collections (attribute name), andNUMCOLL (column name).

Object NameThe name of the performance object. The type is string.

The following names are defined for this attribute: OBJECT_NAME or OBJNAME (historicalname), Object Name (caption), Object_Name (attribute name), and OBJNAME (column name).

Object StatusThe status of the performance object. The type is integer with enumerated values. The followingvalues are defined: ACTIVE (0), INACTIVE (1). Any value that does not have a definition here isdisplayed in the User Interface.

The following names are defined for this attribute: OBJECT_STATUS or OBJSTTS (historicalname), Object Status (caption), Object_Status (attribute name), and OBJSTTS (column name).

Object TypeThe type of the performance object. The type is integer with enumerated values. The followingvalues are defined: WMI (0), PERFMON (1), WMI ASSOCIATION GROUP (2), JMX (3), SNMP(4), SHELL COMMAND (5), JOINED GROUPS (6), CIMOM (7), CUSTOM (8), ROLLUP DATA (9),WMI REMOTE DATA (10), LOG FILE (11), JDBC (12), CONFIG DISCOVERY (13), NT EVENTLOG (14), FILTER (15), SNMP EVENT (16), PING (17), DIRECTOR DATA (18), DIRECTOREVENT (19), SSH REMOTE SHELL COMMAND (20). Any value that does not have a definitionhere is displayed in the User Interface.

The following names are defined for this attribute: OBJECT_TYPE or OBJTYPE (historical name),Object Type (caption), Object_Type (attribute name), and OBJTYPE (column name).

Query NameThe name of the attribute group. This attribute is a key attribute. The type is string.


The following names are defined for this attribute: QUERY_NAME or ATTRGRP (historicalname), Query Name (caption), Query_Name (attribute name), and ATTRGRP (column name).

Refresh IntervalThe interval at which this group is refreshed in seconds. The type is integer (32-bit counter).

The following names are defined for this attribute: REFRESH_INTERVAL or REFRINT (historicalname), Refresh Interval (caption), Refresh_Interval (attribute name), and REFRINT (columnname).



Response Times data setMaximum and average response times for different command types, such as queries and updates. It isrequired that profiling levels 1 or 2 be active for all mongod instances in the replica set (shard).Thresholds for this data set are associated with the MongoDB component. This data set is displayed asKKJ RESPONSE_TIMES in the threshold editor. A data sample is sent to the server every minute and ismaintained for 8 days by default. The default data sample consists of the first 6 rows sorted byMax_Response_Time_In_MS. The attributes shown in italic are visible in the UI. All attributes areavailable for thresholds.


Cat Op NamesConcatenation of operation, database name, and collection name. The type is string.

The following names are defined for this attribute: CAT_OP_NAMES or CAT_OP_NAM(historical name), Cat Op Names (caption), Cat_Op_Names (attribute name), and CAT_OP_NAM(column name).

Collection NameThe collection name is provided for the given database and command data. This attribute is a keyattribute. The type is string.

The following names are defined for this attribute: COLLECTION_NAME or COLLECTION(historical name), Collection Name (caption), Collection_Name (attribute name), and COLLECTION(column name).

Database NameThe name of the database to which the values in the row are correlated. This attribute is a keyattribute. The type is string.


Max Response Time In MSThe longest time (in milliseconds) that a command of this type requires to complete. The type isreal number (32-bit gauge) with two decimal places of precision.

The following names are defined for this attribute: MAX_RESPONSE_TIME_IN_MS orMAX_RESPON (historical name), Max Response Time In MS (caption), Max_Response_Time_In_MS(attribute name), and MAX_RESPON (column name).




Operation TypeThe type of operation that was run. This attribute is a key attribute. The type is string.

The following names are defined for this attribute: OPERATION_TYPE or OPERATION_(historical name), Operation Type (caption), Operation_Type (attribute name), and OPERATION_(column name).



Avg Response Time In MSThe average response time (in milliseconds) for this command type. The type is real number(32-bit gauge) with two decimal places of precision.

The following names are defined for this attribute: AVG_RESPONSE_TIME_IN_MS orAVG_RESPON (historical name), Avg Response Time In MS (caption),Avg_Response_Time_In_MS (attribute name), and AVG_RESPON (column name).

Recent HistoryThe count of the most recent type of each operation that is used to compute the maximum andaverage response times. By default, this history is 1 MB in size, and can be expanded if the userincreases the history capacity in the "system.profile" namespace. The type is integer (32-bitcounter).

The following names are defined for this attribute: RECENT_HISTORY or RECENT_HIS(historical name), Recent History (caption), Recent_History (attribute name), and RECENT_HIS(column name).

Router Location data setThe host name and port information for the MongoDB router.


Host The host name or IP Address where the MongoDB router runs. The type is string.

The following names are defined for this attribute: HOST (historical name), Host (caption), Host(attribute name), and HOST (column name).

Instance NameThe instance name of the agent that represents this MongoDB. The type is string.

The following names are defined for this attribute: INSTANCE_NAME or INST (historical name),Instance Name (caption), Instance_Name (attribute name), and INST (column name).

IP AddressThe IP address where the component runs. The type is string.

The following names are defined for this attribute: IP_ADDRESS or IPADDR (historical name), IPAddress (caption), IP_Address (attribute name), and IPADDR (column name).



Port The port number where the MongoDB router runs. The type is integer (32-bit gauge).

The following names are defined for this attribute: PORT (historical name), Port (caption), Port(attribute name), and PORT (column name).




RT Copy for APM UI data setFiltered data rows from the Response Times data set. Thresholds for this data set are associated with theMongoDB component. This data set is displayed as KKJ RT_COPY_FOR_APMUI in the threshold editor.A data sample is sent to the server every minute and is maintained for 8 days by default. The defaultdata sample consists of the first 6 rows sorted by Avg_Response_Time_In_MS. The attributes shown initalic are visible in the UI. All attributes are available for thresholds.


Avg Response Time In MSThe average response time (in milliseconds) for this command type. The type is real number(32-bit gauge) with two decimal places of precision.

The following names are defined for this attribute: AVG_RESPONSE_TIME_IN_MS orAVG_RESPON (historical name), Avg Response Time In MS (caption), Avg_Response_Time_In_MS(attribute name), and AVG_RESPON (column name).

Cat Op NamesConcatenation of operation, database name, and collection name. The type is string.

The following names are defined for this attribute: CAT_OP_NAMES or CAT_OP_NAM(historical name), Cat Op Names (caption), Cat_Op_Names (attribute name), and CAT_OP_NAM(column name).

Collection NameThe name of the collection. This attribute is a key attribute. The type is string.

The following names are defined for this attribute: COLLECTION_NAME or COLLECTION(historical name), Collection Name (caption), Collection_Name (attribute name), and COLLECTION(column name).





Operation TypeThe type of operation that was run. This attribute is a key attribute. The type is string.

The following names are defined for this attribute: OPERATION_TYPE or OPERATION_(historical name), Operation Type (caption), Operation_Type (attribute name), and OPERATION_(column name).




Max Response Time In MSThe longest time (in milliseconds) that a command of this type requires to complete. The type isreal number (32-bit gauge) with two decimal places of precision.

The following names are defined for this attribute: MAX_RESPONSE_TIME_IN_MS orMAX_RESPON (historical name), Max Response Time In MS (caption),Max_Response_Time_In_MS (attribute name), and MAX_RESPON (column name).

Recent HistoryThe count of the most recent type of each operation that is used to compute the maximum andaverage response times. By default, the history is 1 MB in size, and can be expanded if the userincreases the history capacity in the "system.profile" namespace. The type is integer (32-bitcounter).

The following names are defined for this attribute: RECENT_HISTORY or RECENT_HIS(historical name), Recent History (caption), Recent_History (attribute name), and RECENT_HIS(column name).

Take Action Status data setThe Take Action Status data set contains information about the results of actions this agent ran.


Action App Return CodeThe application return code of the action is the actual return code of the command run. The typeis integer (32-bit numeric property).

The following names are defined for this attribute: ACTION_APP_RETURN_CODE or TSKAPRC(historical name), Action App Return Code (caption), Action_App_Return_Code (attribute name),and TSKAPRC (column name).

Action CommandThe command that was run by the action. The type is string.

The following names are defined for this attribute: ACTION_COMMAND or TSKCMND(historical name), Action Command (caption), Action_Command (attribute name), andTSKCMND (column name).

Action IDThe id of the action. The type is integer (32-bit numeric property).

The following names are defined for this attribute: ACTION_ID or TSKID (historical name),Action ID (caption), Action_ID (attribute name), and TSKID (column name).

Action InstanceThe instance that is associated with the output produced by running the action. The type isstring.

The following names are defined for this attribute: ACTION_INSTANCE or TSKINST (historicalname), Action Instance (caption), Action_Instance (attribute name), and TSKINST (column name).

Action MessageThe message that is associated with the return code of the action. The type is string.

The following names are defined for this attribute: ACTION_MESSAGE or TSKMSGE (historicalname), Action Message (caption), Action_Message (attribute name), and TSKMSGE (columnname).

Action NameThe name of the action that was run. The type is string.

The following names are defined for this attribute: ACTION_NAME or TSKNAME (historicalname), Action Name (caption), Action_Name (attribute name), and TSKNAME (column name).


Action NodeThe node where the action ran. The type is string.

The following names are defined for this attribute: ACTION_NODE or TSKORGN (historicalname), Action Node (caption), Action_Node (attribute name), and TSKORGN (column name).

Action OwnerThe name of the situation or user that initiated the action. The type is string.

The following names are defined for this attribute: ACTION_OWNER or TSKOWNR (historicalname), Action Owner (caption), Action_Owner (attribute name), and TSKOWNR (column name).

Action ResultsThe output that is produced by running the action. The type is string.

The following names are defined for this attribute: ACTION_RESULTS or TSKOUTP (historicalname), Action Results (caption), Action_Results (attribute name), and TSKOUTP (column name).

Action StatusThe return code from the Action Status dialog, which is the return code category that is definedfor the application return code. The type is integer (32-bit numeric property).

The following names are defined for this attribute: ACTION_STATUS or TSKSTAT (historicalname), Action Status (caption), Action_Status (attribute name), and TSKSTAT (column name).

Action SubnodeThe subnode where the action ran. The type is string.

The following names are defined for this attribute: ACTION_SUBNODE or TSKSBND (historicalname), Action Subnode (caption), Action_Subnode (attribute name), and TSKSBND (columnname).

Action TypeThe type of the action. The type is integer (32-bit numeric property) with enumerated values. Thefollowing values are defined: UNKNOWN (0), AUTOMATION (1). Any value that does not havea definition here is displayed in the User Interface.

The following names are defined for this attribute: ACTION_TYPE or TSKTYPE (historical name),Action Type (caption), Action_Type (attribute name), and TSKTYPE (column name).



TimestampThe time the event was generated. The type is string.


Thread Pool Status data setThe Thread Pool Status data set contains information that reflects the status of the internal thread poolused to collect data asynchronously.




Thread Pool Active ThreadsThe number of threads in the thread pool currently active doing work. The type is integer (32-bit


gauge) with enumerated values. The following values are defined: NO DATA (-1), NO DATA(-100). Any value that does not have a definition here is displayed in the User Interface.

The following names are defined for this attribute: THREAD_POOL_ACTIVE_THREADS orTPACTTH (historical name), Thread Pool Active Threads (caption), Thread_Pool_Active_Threads(attribute name), and TPACTTH (column name).

Thread Pool Avg Active ThreadsThe average number of threads in the thread pool simultaneously active doing work. The type isreal number (32-bit gauge) with two decimal places of precision with enumerated values. Thefollowing values are defined: NO DATA (-1), NO DATA (-100). Any value that does not have adefinition here is displayed in the User Interface.

The following names are defined for this attribute: THREAD_POOL_AVG_ACTIVE_THREADS orTPAVGAT (historical name), Thread Pool Avg Active Threads (caption),Thread_Pool_Avg_Active_Threads (attribute name), and TPAVGAT (column name).

Thread Pool Avg Job WaitThe average time a job spends waiting on the thread pool queue in seconds. The type is realnumber (32-bit gauge) with two decimal places of precision with enumerated values. Thefollowing values are defined: NO DATA (-1), NO DATA (-100). Any value that does not have adefinition here is displayed in the User Interface.

The following names are defined for this attribute: THREAD_POOL_AVG_JOB_WAIT orTPAVJBW (historical name), Thread Pool Avg Job Wait (caption), Thread_Pool_Avg_Job_Wait(attribute name), and TPAVJBW (column name).

Thread Pool Avg Queue LengthThe average length of the thread pool queue during this run. The type is real number (32-bitgauge) with two decimal places of precision with enumerated values. The following values aredefined: NO DATA (-1), NO DATA (-100). Any value that does not have a definition here isdisplayed in the User Interface.

The following names are defined for this attribute: THREAD_POOL_AVG_QUEUE_LENGTH orTPAVGQL (historical name), Thread Pool Avg Queue Length (caption),Thread_Pool_Avg_Queue_Length (attribute name), and TPAVGQL (column name).

Thread Pool Max Active ThreadsThe peak number of threads in the thread pool that were simultaneously active doing work. Thetype is integer (32-bit counter) with enumerated values. The following values are defined: NODATA (-1), NO DATA (-100). Any value that does not have a definition here is displayed in theUser Interface.

The following names are defined for this attribute: THREAD_POOL_MAX_ACTIVE_THREADSor TPMAXAT (historical name), Thread Pool Max Active Threads (caption),Thread_Pool_Max_Active_Threads (attribute name), and TPMAXAT (column name).

Thread Pool Max Queue LengthThe peak length the thread pool queue reached. The type is integer (32-bit counter) withenumerated values. The following values are defined: NO DATA (-1), NO DATA (-100). Anyvalue that does not have a definition here is displayed in the User Interface.

The following names are defined for this attribute: THREAD_POOL_MAX_QUEUE_LENGTH orTPMAXQL (historical name), Thread Pool Max Queue Length (caption),Thread_Pool_Max_Queue_Length (attribute name), and TPMAXQL (column name).

Thread Pool Max SizeThe maximum number of threads that are allowed to exist in the thread pool. The type is integer(32-bit numeric property) with enumerated values. The following values are defined: NO DATA(-1), NO DATA (-100). Any value that does not have a definition here is displayed in the UserInterface.


The following names are defined for this attribute: THREAD_POOL_MAX_SIZE or TPMAXSZ(historical name), Thread Pool Max Size (caption), Thread_Pool_Max_Size (attribute name), andTPMAXSZ (column name).

Thread Pool Min Active ThreadsThe smallest number of threads in the thread pool that were simultaneously active doing work.The type is integer (32-bit counter) with enumerated values. The following values are defined:NO DATA (-1), NO DATA (-100). Any value that does not have a definition here is displayed inthe User Interface.

The following names are defined for this attribute: THREAD_POOL_MIN_ACTIVE_THREADS orTPMINAT (historical name), Thread Pool Min Active Threads (caption),Thread_Pool_Min_Active_Threads (attribute name), and TPMINAT (column name).

Thread Pool Min Queue LengthThe minimum length the thread pool queue reached. The type is integer (32-bit counter) withenumerated values. The following values are defined: NO DATA (-1), NO DATA (-100). Anyvalue that does not have a definition here is displayed in the User Interface.

The following names are defined for this attribute: THREAD_POOL_MIN_QUEUE_LENGTH orTPMINQL (historical name), Thread Pool Min Queue Length (caption),Thread_Pool_Min_Queue_Length (attribute name), and TPMINQL (column name).

Thread Pool Queue LengthThe number of jobs currently waiting in the thread pool queue. The type is integer (32-bit gauge)with enumerated values. The following values are defined: NO DATA (-1), NO DATA (-100). Anyvalue that does not have a definition here is displayed in the User Interface.

The following names are defined for this attribute: THREAD_POOL_QUEUE_LENGTH orTPQLGTH (historical name), Thread Pool Queue Length (caption), Thread_Pool_Queue_Length(attribute name), and TPQLGTH (column name).

Thread Pool SizeThe number of threads currently existing in the thread pool. The type is integer (32-bit gauge)with enumerated values. The following values are defined: NO DATA (-1), NO DATA (-100). Anyvalue that does not have a definition here is displayed in the User Interface.

The following names are defined for this attribute: THREAD_POOL_SIZE or THPSIZE (historicalname), Thread Pool Size (caption), Thread_Pool_Size (attribute name), and THPSIZE (columnname).

Thread Pool Total JobsThe number of jobs that are completed by all threads in the pool since agent start. The type isinteger (32-bit counter) with enumerated values. The following values are defined: NO DATA (-1),NO DATA (-100). Any value that does not have a definition here is displayed in the UserInterface.

The following names are defined for this attribute: THREAD_POOL_TOTAL_JOBS or TPTJOBS(historical name), Thread Pool Total Jobs (caption), Thread_Pool_Total_Jobs (attribute name), andTPTJOBS (column name).



WiredTiger Details data setFunctional information about the MongoDB WiredTiger storage engine. Thresholds for this data set areassociated with the MongoDB component. This data set is displayed as KKJ WIREDTIGER_DETAILS in


the threshold editor. A data sample is sent to the server every 5 minutes and is maintained for 8 days bydefault. The attributes shown in italic are visible in the UI. All attributes are available for thresholds.


Bytes in CacheThe size (in MB) of the data that is currently in the cache (in MB). For a storage engine other thanWiredTiger or In-Memory, the value is N/A (not applicable). The type is integer (64-bit gauge)with enumerated values. The following values are defined: Value Exceeds Maximum(2147483647), Value Exceeds Minimum (-2147483648), N/A (-1). Any value that does not have adefinition here is displayed in the User Interface.

The following names are defined for this attribute: BYTES_IN_CACHE or BYTESCACHE(historical name), Bytes in Cache (caption), Bytes_in_Cache (attribute name), and BYTESCACHE(column name).

Committed TransactionsA counter for the transactions that were committed since the server startup. For a storage engineother than WiredTiger or In-Memory, the value is N/A (not applicable). The type is integer (rateof change between successive values).

The following names are defined for this attribute: COMMITTED_TRANSACTIONS orCOMMITED (historical name), Committed Transactions (caption), Committed_Transactions(attribute name), and COMMITED (column name).

Dirty BytesThe number of dirty data bytes in the cache (in MB). For a storage engine other than WiredTigeror In-Memory, the value is N/A (not applicable). The type is integer (64-bit gauge) withenumerated values. The following values are defined: Value Exceeds Maximum (2147483647),Value Exceeds Minimum (-2147483648), N/A (-1). Any value that does not have a definition hereis displayed in the User Interface.

The following names are defined for this attribute: DIRTY_BYTES or DIRTYBYTES (historicalname), Dirty Bytes (caption), Dirty_Bytes (attribute name), and DIRTYBYTES (column name).

Host NameThe host name of the system on which this mongod process runs. This attribute is a key attribute.The type is string.

The following names are defined for this attribute: HOST_NAME or HOSTNAME (historicalname), Host Name (caption), Host_Name (attribute name), and HOSTNAME (column name).

Max Bytes ConfiguredThe maximum size (in MB) of the cache. For a storage engine other than WiredTiger orIn-Memory, the value is N/A (not applicable). The type is integer (64-bit gauge) with enumeratedvalues. The following values are defined: Value Exceeds Maximum (2147483647), Value ExceedsMinimum (-2147483648), N/A (-1). Any value that does not have a definition here is displayed inthe User Interface.

The following names are defined for this attribute: MAX_BYTES_CONFIGURED or MAXBYTES(historical name), Max Bytes Configured (caption), Max_Bytes_Configured (attribute name), andMAXBYTES (column name).



Open CursorThe number of open cursors. For a storage engine other than WiredTiger or In-Memory, the valueis N/A (not applicable). The type is integer (64-bit gauge) with enumerated values. The following


values are defined: Value Exceeds Maximum (2147483647), Value Exceeds Minimum(-2147483648), N/A (-1). Any value that does not have a definition here is displayed in the UserInterface.

The following names are defined for this attribute: OPEN_CURSOR or CURSORCNT (historicalname), Open Cursor (caption), Open_Cursor (attribute name), and CURSORCNT (column name).

Open SessionThe number of open sessions. For a storage engine other than WiredTiger or In-Memory, thevalue is N/A (not applicable). The type is integer (64-bit gauge) with enumerated values. Thefollowing values are defined: Value Exceeds Maximum (2147483647), Value Exceeds Minimum(-2147483648), N/A (-1). Any value that does not have a definition here is displayed in the UserInterface.

The following names are defined for this attribute: OPEN_SESSION or SESSIONCNT (historicalname), Open Session (caption), Open_Session (attribute name), and SESSIONCNT (column name).

Percentage ReadThe percentage of the concurrent read operation tickets that are available. For a storage engineother than WiredTiger or In-Memory, the value is N/A (not applicable). The type is integer (64-bitgauge) with enumerated values. The following values are defined: Value Exceeds Maximum(2147483647), Value Exceeds Minimum (-2147483648), N/A (-1). Any value that does not have adefinition here is displayed in the User Interface.

The following names are defined for this attribute: PERCENTAGE_READ or PERREAD (historicalname), Percentage Read (caption), Percentage_Read (attribute name), and PERREAD (columnname).

Percentage WriteThe percentage of the concurrent write operation tickets that are available. For a storage engineother than WiredTiger or In-Memory, the value is N/A (not applicable). The type is integer (64-bitgauge) with enumerated values. The following values are defined: Value Exceeds Maximum(2147483647), Value Exceeds Minimum (-2147483648), N/A (-1). Any value that does not have adefinition here is displayed in the User Interface.

The following names are defined for this attribute: PERCENTAGE_WRITE or PERWRITE(historical name), Percentage Write (caption), Percentage_Write (attribute name), and PERWRITE(column name).

Read BytesThe number of bytes that are read from the cache (in MB). For a storage engine other thanWiredTiger or In-Memory, the value is N/A (not applicable). The type is integer (64-bit gauge)with enumerated values. The following values are defined: Value Exceeds Maximum(2147483647), Value Exceeds Minimum (-2147483648), N/A (-1). Any value that does not have adefinition here is displayed in the User Interface.

The following names are defined for this attribute: READ_BYTES or READBYTES (historicalname), Read Bytes (caption), Read_Bytes (attribute name), and READBYTES (column name).



Transaction BeginsA counter for the transactions that were started since the server startup. For a storage engineother than WiredTiger or In-Memory, the value is N/A (not applicable). The type is integer (rateof change between successive values).


The following names are defined for this attribute: TRANSACTION_BEGINS or TRANSBEGIN(historical name), Transaction Begins (caption), Transaction_Begins (attribute name), andTRANSBEGIN (column name).

Transaction FailedA counter for the transactions that failed due to the cache overflow. For a storage engine otherthan WiredTiger or In-Memory, the value is N/A (not applicable). The type is integer (rate ofchange between successive values).

The following names are defined for this attribute: TRANSACTION_FAILED or TRANFAILED(historical name), Transaction Failed (caption), Transaction_Failed (attribute name), andTRANFAILED (column name).

Transaction Rolled BackA counter for the transactions that were rolled back. For a storage engine other than WiredTigeror In-Memory, the value is N/A (not applicable). The type is integer (rate of change betweensuccessive values).

The following names are defined for this attribute: TRANSACTION_ROLLED_BACK orROLLEDBACK (historical name), Transaction Rolled Back (caption), Transaction_Rolled_Back(attribute name), and ROLLEDBACK (column name).

Write BytesThe number of bytes that are written into the cache (in MB). For a storage engine other thanWiredTiger or In-Memory, the value is N/A (not applicable). The type is integer (64-bit gauge)with enumerated values. The following values are defined: Value Exceeds Maximum(2147483647), Value Exceeds Minimum (-2147483648), N/A (-1). Any value that does not have adefinition here is displayed in the User Interface.

The following names are defined for this attribute: WRITE_BYTES or WRITEBYTES (historicalname), Write Bytes (caption), Write_Bytes (attribute name), and WRITEBYTES (column name).


Accessibility features

Accessibility features assist users who have a disability, such as restricted mobility or limited vision, touse information technology content successfully.

Accessibility features

The web-based interface of IBM® Cloud Application Performance Management is the Cloud APMconsole. The console includes the following major accessibility features:v Enables users to use assistive technologies, such as screen-reader software and digital speech

synthesizer, to hear what is displayed on the screen.1 Consult the product documentation of theassistive technology for details on using those technologies with this product.

v Enables users to operate specific or equivalent features using only the keyboard.v Communicates all information independently of color.2

The Cloud APM console uses the latest W3C Standard, WAI-ARIA 1.0, US Section 508, and Web ContentAccessibility Guidelines (WCAG) 2.0. To take advantage of accessibility features, use the latest release ofyour screen reader in combination with the latest web browser that is supported by this product.

The Cloud APM console online product documentation in IBM Knowledge Center is enabled foraccessibility. The accessibility features of IBM Knowledge Center are described at IBM Knowledge Centerrelease notes.

Keyboard navigation

This product uses standard navigation keys.

Interface information

The Cloud APM console web user interface does not rely on cascading style sheets to render contentproperly and to provide a usable experience. However, the product documentation does rely oncascading style sheets. IBM Knowledge Center provides an equivalent way for low-vision users to usetheir custom display settings, including high-contrast mode. You can control font size by using the deviceor browser settings.

The Cloud APM console web user interface includes WAI-ARIA navigational landmarks that you can useto quickly navigate to functional areas in the application.

The Cloud APM console user interface does not have content that flashes 2 - 55 times per second.

Related accessibility information

In addition to standard IBM help desk and support websites, IBM has established a TTY telephoneservice for use by deaf or hard of hearing customers to access sales and support services:

TTY service 800-IBM-3383 (800-426-3383) (within North America)

1. Exceptions include some of the Agent Configuration pages and historical line charts in the Cloud APM console.

2. Exceptions include some Agent Configuration pages of the Cloud APM console.


http://www.w3.org/TR/wai-aria/

http://www.access-board.gov/guidelines-and-standards/communications-and-it/about-the-section-508-standards/section-508-standards

http://www.w3.org/TR/WCAG20/

http://www.w3.org/TR/WCAG20/

http://www.ibm.com/support/knowledgecenter/en/about/releasenotes.html?view=kc#accessibility

http://www.ibm.com/support/knowledgecenter/en/about/releasenotes.html?view=kc#accessibility

IBM and accessibility

For more information about the commitment that IBM has to accessibility, see IBM Accessibility .


http://www.ibm.com/able

Notices

This information was developed for products and services offered in the US. This material might beavailable from IBM in other languages. However, you may be required to own a copy of the product orproduct version in that language in order to access it.

IBM may not offer the products, services, or features discussed in this document in other countries.Consult your local IBM representative for information on the products and services currently available inyour area. Any reference to an IBM product, program, or service is not intended to state or imply thatonly that IBM product, program, or service may be used. Any functionally equivalent product, program,or service that does not infringe any IBM intellectual property right may be used instead. However, it isthe user's responsibility to evaluate and verify the operation of any non-IBM product, program, orservice.

IBM may have patents or pending patent applications covering subject matter described in thisdocument. The furnishing of this document does not grant you any license to these patents. You can sendlicense inquiries, in writing, to:

IBM Director of LicensingIBM CorporationNorth Castle Drive, MD-NC119Armonk, NY 10504-1785US

For license inquiries regarding double-byte character set (DBCS) information, contact the IBM IntellectualProperty Department in your country or send inquiries, in writing, to:

Intellectual Property LicensingLegal and Intellectual Property LawIBM Japan Ltd.19-21, Nihonbashi-Hakozakicho, Chuo-kuTokyo 103-8510, Japan

INTERNATIONAL BUSINESS MACHINES CORPORATION PROVIDES THIS PUBLICATION "AS IS"WITHOUT WARRANTY OF ANY KIND, EITHER EXPRESS OR IMPLIED, INCLUDING, BUT NOTLIMITED TO, THE IMPLIED WARRANTIES OF NON-INFRINGEMENT, MERCHANTABILITY ORFITNESS FOR A PARTICULAR PURPOSE. Some jurisdictions do not allow disclaimer of express orimplied warranties in certain transactions, therefore, this statement may not apply to you.

This information could include technical inaccuracies or typographical errors. Changes are periodicallymade to the information herein; these changes will be incorporated in new editions of the publication.IBM may make improvements and/or changes in the product(s) and/or the program(s) described in thispublication at any time without notice.

Any references in this information to non-IBM websites are provided for convenience only and do not inany manner serve as an endorsement of those websites. The materials at those websites are not part ofthe materials for this IBM product and use of those websites is at your own risk.

IBM may use or distribute any of the information you provide in any way it believes appropriate withoutincurring any obligation to you.


Licensees of this program who wish to have information about it for the purpose of enabling: (i) theexchange of information between independently created programs and other programs (including thisone) and (ii) the mutual use of the information which has been exchanged, should contact:

IBM Director of LicensingIBM CorporationNorth Castle Drive, MD-NC119Armonk, NY 10504-1785US

Such information may be available, subject to appropriate terms and conditions, including in some cases,payment of a fee.

The licensed program described in this document and all licensed material available for it are providedby IBM under terms of the IBM Customer Agreement, IBM International Program License Agreement orany equivalent agreement between us.

The performance data discussed herein is presented as derived under specific operating conditions.Actual results may vary.

Information concerning non-IBM products was obtained from the suppliers of those products, theirpublished announcements or other publicly available sources. IBM has not tested those products andcannot confirm the accuracy of performance, compatibility or any other claims related tonon-IBMproducts. Questions on the capabilities of non-IBM products should be addressed to thesuppliers of those products.

Statements regarding IBM's future direction or intent are subject to change or withdrawal without notice,and represent goals and objectives only.

This information is for planning purposes only. The information herein is subject to change before theproducts described become available.

This information contains examples of data and reports used in daily business operations. To illustratethem as completely as possible, the examples include the names of individuals, companies, brands, andproducts. All of these names are fictitious and any similarity to actual people or business enterprises isentirely coincidental.

COPYRIGHT LICENSE:

This information contains sample application programs in source language, which illustrate programmingtechniques on various operating platforms. You may copy, modify, and distribute these sample programsin any form without payment to IBM, for the purposes of developing, using, marketing or distributingapplication programs conforming to the application programming interface for the operating platform forwhich the sample programs are written. These examples have not been thoroughly tested under allconditions. IBM, therefore, cannot guarantee or imply reliability, serviceability, or function of theseprograms. The sample programs are provided "AS IS", without warranty of any kind. IBM shall not beliable for any damages arising out of your use of the sample programs.

Each copy or any portion of these sample programs or any derivative workmust include a copyrightnotice as follows:© (your company name) (year).Portions of this code are derived from IBM Corp. Sample Programs.© Copyright IBM Corp. 2014, 2015.


TrademarksIBM, the IBM logo, and ibm.com are trademarks or registered trademarks of International BusinessMachines Corp., registered in many jurisdictions worldwide. Other product and service names might betrademarks of IBM or other companies. A current list of IBM trademarks is available on the web at"Copyright and trademark information" at www.ibm.com/legal/copytrade.shtml.

Linux is a trademark of Linus Torvalds in the United States, other countries, or both.

Microsoft, Windows, Windows NT, and the Windows logo are trademarks of Microsoft Corporation in theUnited States, other countries, or both.

UNIX is a registered trademark of The Open Group in the United States and other countries.

Java™ and all Java-based trademarks and logos are trademarks or registered trademarks of Oracle and/orits affiliates.

Terms and conditions for product documentationPermissions for the use of these publications are granted subject to the following terms and conditions.

Applicability

These terms and conditions are in addition to any terms of use for the IBM website.

Personal use

You may reproduce these publications for your personal, noncommercial use provided that allproprietary notices are preserved. You may not distribute, display or make derivative work of thesepublications, or any portion thereof, without the express consent of IBM.

Commercial use

You may reproduce, distribute and display these publications solely within your enterprise provided thatall proprietary notices are preserved. You may not make derivative works of these publications, orreproduce, distribute or display these publications or any portion thereof outside your enterprise, withoutthe express consent of IBM.

Rights

Except as expressly granted in this permission, no other permissions, licenses or rights are granted, eitherexpress or implied, to the publications or any information, data, software or other intellectual propertycontained therein.

IBM reserves the right to withdraw the permissions granted herein whenever, in its discretion, the use ofthe publications is detrimental to its interest or, as determined by IBM, the above instructions are notbeing properly followed.

You may not download, export or re-export this information except in full compliance with all applicablelaws and regulations, including all United States export laws and regulations.

Notices 79

http://www.ibm.com/legal/us/en/copytrade.shtml

IBM MAKES NO GUARANTEE ABOUT THE CONTENT OF THESE PUBLICATIONS. THEPUBLICATIONS ARE PROVIDED "AS-IS" AND WITHOUT WARRANTY OF ANY KIND, EITHEREXPRESSED OR IMPLIED, INCLUDING BUT NOT LIMITED TO IMPLIED WARRANTIES OFMERCHANTABILITY, NON-INFRINGEMENT, AND FITNESS FOR A PARTICULAR PURPOSE.

IBM Online Privacy StatementIBM Software products, including software as a service solutions, (“Software Offerings”) may use cookiesor other technologies to collect product usage information, to help improve the end user experience, totailor interactions with the end user or for other purposes. In many cases no personally identifiableinformation is collected by the Software Offerings. Some of our Software Offerings can help enable you tocollect personally identifiable information. If this Software Offering uses cookies to collect personallyidentifiable information, specific information about this offering's use of cookies is set forth in thefollowing paragraphs.

Depending upon the configurations deployed, this Software Offering may use session cookies that collecteach user's user name for purposes of session management, authentication, and single sign-onconfiguration. These cookies can be disabled, but disabling them will also likely eliminate thefunctionality they enable.

If the configurations deployed for this Software Offering provide you as customer the ability to collectpersonally identifiable information from end users via cookies and other technologies, you should seekyour own legal advice about any laws applicable to such data collection, including any requirements fornotice and consent.

For more information about the use of various technologies, including cookies, for these purposes, SeeIBM's Privacy Policy at http://www.ibm.com/privacy and IBM's Online Privacy Statement athttp://www.ibm.com/privacy/details the section entitled “Cookies, Web Beacons and OtherTechnologies” and the “IBM Software Products and Software-as-a-Service Privacy Statement” athttp://www.ibm.com/software/info/product-privacy.


http://www.ibm.com/privacy

http://www.ibm.com/privacy/details

http://www.ibm.com/software/info/product-privacy

Index

Aaccessibility features 75Acquiring Count attribute 59Acquiring Count Total attribute 34Acquiring Deadlock Count attribute 59Acquiring Exclusive Count attribute 60Acquiring IS Count attribute 61Acquiring IX Count attribute 61Acquiring Shared Count attribute 60Acquiring Wait Count attribute 60Acquiring Wait Count IS attribute 61Acquiring Wait Count IX attribute 61Acquiring Wait Count S attribute 61Acquiring Wait Count X attribute 61Action App Return Code attribute 68Action Command attribute 68Action ID attribute 68Action Instance attribute 68Action Message attribute 68Action Name attribute 68Action Node attribute 69Action Owner attribute 69Action Results attribute 69Action Status attribute 69Action Subnode attribute 69Action Type attribute 69additional information

attributes 27attributes

Acquiring Count 59Acquiring Count Total 34Acquiring Deadlock Count 59Acquiring Exclusive Count 60Acquiring IS Count 61Acquiring IX Count 61Acquiring Shared Count 60Acquiring Wait Count 60Acquiring Wait Count IS 61Acquiring Wait Count IX 61Acquiring Wait Count S 61Acquiring Wait Count X 61Action App Return Code 68Action Command 68Action ID 68Action Instance 68Action Message 68Action Name 68Action Node 69Action Owner 69Action Results 69Action Status 69Action Subnode 69Action Type 69Available Connections 36, 39, 53Available Storage Size 32Average Collection Duration 62Average MS of Flush 50Average Time(ms) 41Avg Object Size 32Avg Response Time In MS 66, 67Avg Size 30

attributes (continued)Background Flushes 50Background Flushes v3 50Batches Num 51Batches Total MS 51Bits 36, 39, 56Bytes in Cache 72BytesIN 36, 39, 46, 56BytesOUT 36, 39, 46, 56Cache Hit Percent 62Cache Hits 62Cache Misses 63Cat Name 32Cat Names 31Cat Op Names 65, 67Collection Name 29, 65, 67Collection Size 30Collection Storage 29Collection Storage Size 30Commands 36, 39, 51, 54Commits 42Committed Transactions 72Current Connections 36, 39, 54Database Name 30, 31, 32, 44, 65, 67Database Names 31Deletes 36, 39, 51, 54Dirty Bytes 72Error Code 63Error msg 57Flushes 42General Shard Information 32Getmore 36, 40, 51, 54Global Lock Time 51Global Lock Time MS 51Global Status 34Hit Ratio 46Host 57, 66Host and Port 57Host Name 34, 35, 38, 42, 44, 46, 54, 60, 72Index Size 32Inserts 37, 40, 51, 54Instance Name 66Intervals Skipped 63IP Address 59, 66Is Capped 30Is Empty 31Is Master 52Journaled MB 42Last Collection Duration 63Last Collection Finished 64Last Collection Start 64Last Flush Finished 52Last Flush Time(ms) 42Last MS Flush 52Last Operation 57Lock type 60Locks 34Max Bytes Configured 72Max Documents 31Max Response Time In MS 65, 68Messages 37, 40, 56


attributes (continued)MII Copy for APM UI One 35MII Copy for APM UI Two 38Miss Ratio 52MMAPv1 Details 41Mongo Inst DB Lock 44Mongo Inst IO Info 46Mongo Instance Information 53Mongo Version 37, 40, 54Mongod Instances 32Mongod Listing 57MongoDB Locks 59MultiTarget Cursor 46Name 57No Timeout Cursor 47Node 30, 31, 32, 34, 35, 39, 42, 44, 47, 54, 57, 60, 64, 65, 66,

67, 69, 72Num of Collections 32Num of Extents 33Num of Indexes 33Num of Objects Recorded 33Num Requests 37, 40, 47, 56Number of Accesses 52Number of Collections 64Number of Hits 47Number of Hits v3 47Number of Misses 47Number of Misses v3 47Number of Resets 48Number of Resets v3 48Object Count 31Object Name 64Object Status 64Object Type 64Op Count 48Op Total 37, 40, 52, 54Open Cursor 72Open Session 73Operation Type 66, 67Oplog Window 57overview 27Page Faults 37, 40, 48, 56Percentage of Connections 37, 40, 55Percentage Read 73Percentage Size 30, 33Percentage Used 57Percentage Write 73Performance Object Status 62PID 37, 41, 55Pinned 48Port 58, 66Queries 38, 41, 52, 55Query Name 64RAM Approx MB 35, 41, 52, 55Read Bytes 73Recent History 66, 68Refresh Interval 65Replication Lag 58Response Times 65Role 58Router Location 66RT Copy for APM UI 67Secondary 53Set Name 53Shard Name 33Single Target 48Size 31

attributes (continued)Size Bytes 31Size of Data 33Size of Data Scaled 33Status 34, 58Status String 58Storage Engine 48Storage Size 31, 33Take Action Status 68Target page 58Target Page 35Thread Pool Active Threads 69Thread Pool Avg Active Threads 70Thread Pool Avg Job Wait 70Thread Pool Avg Queue Length 70Thread Pool Max Active Threads 70Thread Pool Max Queue Length 70Thread Pool Max Size 70Thread Pool Min Active Threads 71Thread Pool Min Queue Length 71Thread Pool Queue Length 71Thread Pool Size 71Thread Pool Status 69Thread Pool Total Jobs 71Time Acquiring Millis Read 44Time Acquiring Millis Read v3 44Time Acquiring Millis Write 45Time Acquiring Millis Write v3 44Time Acquiring Total 35Time AcquiringMicros 60Time AcquiringMicros IS 61Time AcquiringMicros IX 62Time AcquiringMicros S 62Time AcquiringMicros X 62Time Locked Millis Read 45Time Locked Millis Read v3 45Time Locked Millis Write 45Time Locked Millis Write v3 46Time Locked Total 35Time PrepLogBuffer 42Time RemapPrivateView 43Time WriteToDataFiles 43Time WriteToJournal 43Timeout Cursor 49Timestamp 30, 31, 33, 34, 35, 36, 39, 43, 45, 49, 55, 58, 60,

65, 66, 67, 69, 71, 73Total Active Connections 49Total Active Readers 49Total Active Writers 49Total Connections Created 38, 41, 56Total Current Queue 49Total Current Readers 49Total Current Writers 50Total MS of Flushes 53Total Number of Operations 53Total Open Cursor 50Total Size 59Total Size of Database 33Total Size of Namespace 34Total Time Acquiring 45Total Time Locked 45Total Time(ms) 43Transaction Begins 73Transaction Failed 74Transaction Rolled Back 74Updates 38, 41, 53, 55Uptime 59


attributes (continued)UpTime 38, 41, 55Used size 59Virtual Mem MB 38, 39, 53, 55Warnings 38, 41, 56WiredTiger Details 72Write Bytes 74WriteToDataFilesMB 43

Available Connections attribute 36, 39, 53Available Storage Size attribute 32Average Collection Duration attribute 62Average MS of Flush attribute 50Average Time(ms) attribute 41Avg Object Size attribute 32Avg Response Time In MS attribute 66, 67Avg Size attribute 30

BBackground Flushes attribute 50Background Flushes v3 attribute 50Batches Num attribute 51Batches Total MS attribute 51Bits attribute 36, 39, 56Bytes in Cache attribute 72BytesIN attribute 36, 39, 46, 56BytesOUT attribute 36, 39, 46, 56

CCache Hit Percent attribute 62Cache Hits attribute 62Cache Misses attribute 63Cat Name attribute 32Cat Names attribute 31Cat Op Names attribute 65, 67Collection Name attribute 29, 65, 67Collection Size attribute 30Collection Storage data set 29Collection Storage Size attribute 30Commands attribute 36, 39, 51, 54Commits attribute 42Committed Transactions attribute 72Current Connections attribute 36, 39, 54

Ddashboards 3data set

attributes 29data sets

Collection Storage 29Database Names 31General Shard Information 32Global Status 34list of all 28Locks 34MII Copy for APM UI One 35MII Copy for APM UI Two 38MMAPv1 Details 41Mongo Inst DB Lock 44Mongo Inst IO Info 46Mongo Instance Information 53Mongod Listing 57MongoDB Locks 59overview 27

data sets (continued)Performance Object Status 62Response Times 65Router Location 66RT Copy for APM UI 67Take Action Status 68Thread Pool Status 69WiredTiger Details 72

Database Name attribute 30, 31, 32, 44, 65, 67Database Names data set 31Deletes attribute 36, 39, 51, 54Dirty Bytes attribute 72

EError Code attribute 63Error msg attribute 57

FFlushes attribute 42

GGeneral Shard Information data set 32Getmore attribute 36, 40, 51, 54Global Lock Time attribute 51Global Lock Time MS attribute 51Global Status data set 34

HHit Ratio attribute 46Host and Port attribute 57Host attribute 57, 66Host Name attribute 34, 35, 38, 42, 44, 46, 54, 60, 72

IIndex Size attribute 32Inserts attribute 37, 40, 51, 54Instance Name attribute 66Intervals Skipped attribute 63Introduction 1IP Address attribute 59, 66Is Capped attribute 30Is Empty attribute 31Is Master attribute 52

JJournaled MB attribute 42

KKPIs 3

LLast Collection Duration attribute 63Last Collection Finished attribute 64Last Collection Start attribute 64Last Flush Finished attribute 52

Index 83

Last Flush Time(ms) attribute 42Last MS Flush attribute 52Last Operation attribute 57Lock type attribute 60Locks data set 34

MMax Bytes Configured attribute 72Max Documents attribute 31Max Response Time In MS attribute 65, 68Messages attribute 37, 40, 56MII Copy for APM UI One data set 35MII Copy for APM UI Two data set 38Miss Ratio attribute 52MMAPv1 Details data set 41Mongo Inst DB Lock data set 44Mongo Inst IO Info data set 46Mongo Instance Information data set 53Mongo Version attribute 37, 40, 54Mongod Instances attribute 32Mongod Listing data set 57MongoDB Locks data set 59MultiTarget Cursor attribute 46

NName attribute 57No Timeout Cursor attribute 47Node attribute 30, 31, 32, 34, 35, 39, 42, 44, 47, 54, 57, 60, 64,

65, 66, 67, 69, 72Num of Collections attribute 32Num of Extents attribute 33Num of Indexes attribute 33Num of Objects Recorded attribute 33Num Requests attribute 37, 40, 47, 56Number of Accesses attribute 52Number of Collections attribute 64Number of Hits attribute 47Number of Hits v3 attribute 47Number of Misses attribute 47Number of Misses v3 attribute 47Number of Resets attribute 48Number of Resets v3 attribute 48

OObject Count attribute 31Object Name attribute 64Object Status attribute 64Object Type attribute 64Op Count attribute 48Op Total attribute 37, 40, 52, 54Open Cursor attribute 72Open Session attribute 73Operation Type attribute 66, 67Oplog Window attribute 57

PPage Faults attribute 37, 40, 48, 56Percentage of Connections attribute 37, 40, 55Percentage Read attribute 73Percentage Size attribute 30, 33Percentage Used attribute 57

Percentage Write attribute 73Performance Object Status data set 62PID attribute 37, 41, 55Pinned attribute 48Port attribute 58, 66

QQueries attribute 38, 41, 52, 55Query Name attribute 64

RRAM Approx MB attribute 35, 41, 52, 55Read Bytes attribute 73Recent History attribute 66, 68Refresh Interval attribute 65Replication Lag attribute 58Response Times data set 65Role attribute 58Router Location data set 66RT Copy for APM UI data set 67

SSecondary attribute 53Set Name attribute 53Shard Name attribute 33Single Target attribute 48Size attribute 31Size Bytes attribute 31Size of Data attribute 33Size of Data Scaled attribute 33Status attribute 34, 58Status String attribute 58Storage Engine attribute 48Storage Size attribute 31, 33

TTake Action Status data set 68Target page attribute 58Target Page attribute 35Thread Pool Active Threads attribute 69Thread Pool Avg Active Threads attribute 70Thread Pool Avg Job Wait attribute 70Thread Pool Avg Queue Length attribute 70Thread Pool Max Active Threads attribute 70Thread Pool Max Queue Length attribute 70Thread Pool Max Size attribute 70Thread Pool Min Active Threads attribute 71Thread Pool Min Queue Length attribute 71Thread Pool Queue Length attribute 71Thread Pool Size attribute 71Thread Pool Status data set 69Thread Pool Total Jobs attribute 71thresholds 23thresholds, using attributes 27Time Acquiring Millis Read attribute 44Time Acquiring Millis Read v3 attribute 44Time Acquiring Millis Write attribute 45Time Acquiring Millis Write v3 attribute 44Time Acquiring Total attribute 35Time AcquiringMicros attribute 60Time AcquiringMicros IS attribute 61


Time AcquiringMicros IX attribute 62Time AcquiringMicros S attribute 62Time AcquiringMicros X attribute 62Time Locked Millis Read attribute 45Time Locked Millis Read v3 attribute 45Time Locked Millis Write attribute 45Time Locked Millis Write v3 attribute 46Time Locked Total attribute 35Time PrepLogBuffer attribute 42Time RemapPrivateView attribute 43Time WriteToDataFiles attribute 43Time WriteToJournal attribute 43Timeout Cursor attribute 49Timestamp attribute 30, 31, 33, 34, 35, 36, 39, 43, 45, 49, 55,

58, 60, 65, 66, 67, 69, 71, 73Total Active Connections attribute 49Total Active Readers attribute 49Total Active Writers attribute 49Total Connections Created attribute 38, 41, 56Total Current Queue attribute 49Total Current Readers attribute 49Total Current Writers attribute 50Total MS of Flushes attribute 53Total Number of Operations attribute 53Total Open Cursor attribute 50Total Size attribute 59Total Size of Database attribute 33Total Size of Namespace attribute 34Total Time Acquiring attribute 45Total Time Locked attribute 45Total Time(ms) attribute 43Transaction Begins attribute 73Transaction Failed attribute 74Transaction Rolled Back attribute 74

UUpdates attribute 38, 41, 53, 55Uptime attribute 59UpTime attribute 38, 41, 55Used size attribute 59

VVirtual Mem MB attribute 38, 39, 53, 55

WWarnings attribute 38, 41, 56widgets 3WiredTiger Details data set 72Write Bytes attribute 74WriteToDataFilesMB attribute 43

Index 85


IBM®

Printed in USA