tencent cloud


Monitoring Feature

Last updated: 2022-01-25 16:07:56

    The monitoring feature provided by TencentDB for MongoDB allows you to view the real-time monitoring metric data of instance resources. It collects the monitoring statistics in various forms such as visual chart, table, and dashboard. In addition, it supports setting alarms and pushing alarm notifications promptly, so that you can stay up to date with database service exceptions and adjust your business in time to guarantee stable business operations.

    Monitoring Granularity

    TencentDB for MongoDB currently doesn't support customizing the granularity of monitoring data collection. Its adaptive policy is as follows:

    Time Span Monitoring Granularity Retention Period
    0–1 day 5 seconds 1 day
    0–1 day 1 minute 15 days
    0–1 day 5 minutes 31 days
    0–7 days 1 hour 93 days
    7–30 days 1 day 186 days

    Types of Instances for Monitoring

    TencentDB for MongoDB primary, read-only, and disaster recovery instances can be monitored, and each instance is provided with a separate monitoring view for easy query.

    Monitoring Metrics

    Cloud Monitor provides the following monitoring metrics for TencentDB for MongoDB instances:

    Monitoring DimensionMonitoring MetricUnitDescription
    Cluster Write Request-Number of write requests of the current cluster
    Read Request-Number of read requests of the current cluster
    Update Request
    -Number of update requests of the current cluster
    Deletion Request-Number of deletion requests of the current cluster
    Count Request
    -Number of count requests of the current cluster
    Aggregate Request-Number of aggregate requests of the current cluster
    Cluster Connections-Total number of cluster connections, i.e., number of connections received by the current cluster proxy
    Cluster Connection Percentage%Proportion of current connections to total connections of the cluster
    Max Capacity Utilization%Proportion of currently used storage capacity to total capacity of the cluster
    QPSCounts/secOperations per second, including CRUD operations
    Submitted-Number of successful requests of the cluster
    10–50 ms-Number of requests with an execution time between 10 and 50 ms
    50–100 ms-Number of requests with an execution time between 50 and 100 ms
    100 ms-Number of requests with an execution time of more than 100 ms
    Timeout-Number of timed-out requests
    Oplog Time DifferenceHoursTime difference between the last operation and the first operation in oplog
    Primary/Secondary DelaysPrimary/Secondary delay time
    Oplog Retention PeriodHoursOplog retention period
    Cache Utilization (%)%Percentage of used cache to total cache space
    Dirty Data (%) in Cache%Percentage of the size of dirty data in the cache to total cache space
    Cache Hit Rate%Cache hit rate of the current cluster
    Node CPU Utilization%Current node CPU utilization
    Memory Utilization%Current node memory utilization
    Active Write-Number of data writes of the current node
    Active Read-Number of data reads of the current node
    Pieces of Data Deleted via TTL-Number of data entries deleted via TTL
    TTL Run Times-Number of TTL run times of the current node
    qr-Length of the client read request queue
    qw-Length of the client write request queue
    Connections-Number of connections of the current mongod node
    netinMB/sInbound traffic
    netoutMB/sOutbound traffic
    Contact Us

    Contact our sales team or business advisors to help your business.

    Technical Support

    Open a ticket if you're looking for further assistance. Our Ticket is 7x24 avaliable.

    7x24 Phone Support