Yandex Cloud
Search
Contact UsTry it for free
  • Customer Stories
  • Documentation
  • Blog
  • All Services
  • System Status
  • Marketplace
    • Featured
    • Infrastructure & Network
    • Data Platform
    • AI for business
    • Security
    • DevOps tools
    • Serverless
    • Monitoring & Resources
  • All Solutions
    • By industry
    • By use case
    • Economics and Pricing
    • Security
    • Technical Support
    • Start testing with double trial credits
    • Cloud credits to scale your IT product
    • Gateway to Russia
    • Cloud for Startups
    • Center for Technologies and Society
    • Yandex Cloud Partner program
    • Price calculator
    • Pricing plans
  • Customer Stories
  • Documentation
  • Blog
© 2026 Direct Cursus Technology L.L.C.
Yandex StoreDoc
  • Getting started
    • All guides
      • Viewing cluster logs
      • Performance diagnostics
      • Performance analysis tools
      • Cluster and host state monitoring
  • Access management
  • Pricing policy
  • Terraform reference
  • Monitoring metrics
  • Audit Trails events
  • Public materials
  • Release notes

In this article:

  • Built-in diagnostic tools
  • Profiler
  • Currently running queries
  • Logs
  1. Step-by-step guides
  2. Logs and monitoring
  3. Performance analysis tools

Performance analysis tools

Written by
Yandex Cloud
Updated at February 6, 2026
  • Built-in diagnostic tools
    • Profiler
    • Currently running queries
  • Logs

Built-in diagnostic toolsBuilt-in diagnostic tools

Yandex StoreDoc provides tools for collecting performance metrics:

  • mongostat: Collects CPU and memory usage statistics for Yandex StoreDoc processes.
  • mongotop: Collects read/write statistics for each collection.

To run these tools, use a connection string containing credentials of a user with the mdbMonitor role. For example:

mongostat 5 --uri="mongodb://{<name_of_user_with_mdbMonitor_role>}:{<password>}@{<host>}:27018/?authSource=admin"
mongotop 5 --uri="mongodb://{<name_of_user_with_mdbMonitor_role>}:{<password>}@{<host>}:27018/?authSource=admin"

In this example, both utilities continuously output performance metrics, polling the system every 5 seconds.

ProfilerProfiler

Yandex StoreDoc Includes a built-in profiler. That collects query data and uses it to generate a query optimization strategy. The profiler’s operation is controlled by the Yandex StoreDoc settings, which you can configure when creating a cluster or updating the DBMS settings:

  • operationProfiling.mode.
  • operationProfiling.slowOpThreshold.

Warning

Setting operationProfiling.mode to all and operationProfiling.slowOpThreshold to a value near 0 will severely degrade cluster performance.

To view the data collected by the profiler, refer to the system.profile collection in each database. To read profiler collections, a user must have the mdbMonitor role. By default, this data is duplicated in the logs.

Currently running queriesCurrently running queries

To view queries executed by other users, run db.currentOp under the mdbMonitor role:

db.currentOp()

To view the current user's queries, run db.currentOp() with ownOps set to true:

db.currentOp({ "$ownOps": true })

LogsLogs

The logs contain the most detailed information about Yandex StoreDoc operation.

Management console
CLI
REST API
gRPC API
  1. Open the folder dashboard.
  2. Navigate to the Yandex StoreDoc service.
  3. Click the name of your cluster and select the Logs tab.

If you do not have the Yandex Cloud CLI installed yet, install and initialize it.

By default, the CLI uses the folder specified when creating the profile. To change the default folder, use the yc config set folder-id <folder_ID> command. You can also set a different folder for any specific command using the --folder-name or --folder-id parameter.

To view Yandex StoreDoc logs:

  1. See the description of the CLI command for viewing logs:

    yc managed-mongodb cluster list-logs --help
    
  2. To retrieve all cluster logs, run this command:

    yc managed-mongodb cluster list-logs --id <cluster_ID>
    

    You can get the cluster ID from the list of clusters in your folder.

  1. Get an IAM token for API authentication and place it in an environment variable:

    export IAM_TOKEN="<IAM_token>"
    
  2. Call the Cluster.ListLogs method, e.g., via the following cURL request:

    curl \
        --request GET \
        --header "Authorization: Bearer $IAM_TOKEN" \
        --url 'https://mdb.api.cloud.yandex.net/managed-mongodb/v1/clusters/<cluster_ID>:logs' \
        --url-query serviceType=<service_type> \
        --url-query columnFilter=<column_list> \
        --url-query fromTime=<time_range_start> \
        --url-query toTime=<time_range_end>
    

    Where:

    • serviceType: Target service type for log retrieval:

      • MONGOD: Yandex StoreDoc operations log.
      • AUDIT: Audit log.
    • columnFilter: List of output columns:

      • hostname: Host name.
      • component: Type of component to log, Example: HTTP-Session.
      • message: Message output by the component.
      • query_id: Request ID.
      • severity: Logging level, e.g., Debug.
      • thread: ID of the thread involved in query handling.

      You can specify only one column in the columnFilter parameter. If you want to filter logs by more than one column, provide a list of the columns in several parameters.

      • fromTime: Left boundary of a time range in RFC-3339 format, Example: 2006-01-02T15:04:05Z.
      • toTime: End of the time range in the same format as fromTime.

    You can get the cluster ID from the list of clusters in your folder.

  3. Check the server response to make sure your request was successful.

  1. Get an IAM token for API authentication and place it in an environment variable:

    export IAM_TOKEN="<IAM_token>"
    
  2. Clone the cloudapi repository:

    cd ~/ && git clone --depth=1 https://github.com/yandex-cloud/cloudapi
    

    Below, we assume that the repository contents reside in the ~/cloudapi/ directory.

  3. Call the ClusterService.ListLogs method, e.g., via the following gRPCurl request:

    grpcurl \
      -format json \
      -import-path ~/cloudapi/ \
      -import-path ~/cloudapi/third_party/googleapis/ \
      -proto ~/cloudapi/yandex/cloud/mdb/mongodb/v1/cluster_service.proto \
      -rpc-header "Authorization: Bearer $IAM_TOKEN" \
      -d '{
            "cluster_id": "<cluster_ID>",
            "service_type": "<service_type>",
            "column_filter": [
              "<column_1>", "<column_2>", ..., "<column_N>"
            ],
            "from_time": "<time_range_start>",
            "to_time": "<time_range_end>"
          }' \
      mdb.api.cloud.yandex.net:443 \
      yandex.cloud.mdb.mongodb.v1.ClusterService.ListLogs
    

    Where:

    • service_type: Target service type for log retrieval:

      • MONGOD: Yandex StoreDoc operations log.
      • AUDIT: Audit log.
    • column_filter: List of output columns:

      • hostname: Host name.
      • component: Type of component to log, Example: HTTP-Session.
      • message: Message output by the component.
      • query_id: Request ID.
      • severity: Logging level, e.g., Debug.
      • thread: ID of the thread involved in query handling.

      You can specify more than one column in the column_filter parameter if you want to filter logs by multiple columns.

      • from_time: Left boundary of a time range in RFC-3339 format, Example: 2006-01-02T15:04:05Z.
      • to_time: End of the time range in the same format as from_time.

    You can get the cluster ID from the list of clusters in your folder.

  4. Check the server response to make sure your request was successful.

Was the article helpful?

Previous
Performance diagnostics
Next
Cluster and host state monitoring
© 2026 Direct Cursus Technology L.L.C.