Yandex Cloud
Search
Contact UsGet started
  • Blog
  • Pricing
  • Documentation
  • All Services
  • System Status
    • Featured
    • Infrastructure & Network
    • Data Platform
    • Containers
    • Developer tools
    • Serverless
    • Security
    • Monitoring & Resources
    • ML & AI
    • Business tools
  • All Solutions
    • By industry
    • By use case
    • Economics and Pricing
    • Security
    • Technical Support
    • Customer Stories
    • Start testing with double trial credits
    • Cloud credits to scale your IT product
    • Gateway to Russia
    • Cloud for Startups
    • Education and Science
    • Yandex Cloud Partner program
  • Blog
  • Pricing
  • Documentation
© 2025 Direct Cursus Technology L.L.C.
Yandex Managed Service for Valkey™
  • Getting started
    • All guides
      • Viewing cluster logs
      • Monitoring the state of clusters and hosts
  • Access management
  • Pricing policy
  • Terraform reference
  • Monitoring metrics
  • Audit Trails events
  • Public materials
  • Release notes
  • FAQ

In this article:

  • Getting a cluster log
  • Getting a cluster log stream
  1. Step-by-step guides
  2. Logs and monitoring
  3. Viewing cluster logs

Viewing Valkey™ cluster logs

Written by
Yandex Cloud
Updated at May 13, 2025
  • Getting a cluster log
  • Getting a cluster log stream

Yandex Managed Service for Valkey™ allows you to get a cluster log snippet for the selected period and view logs in real time.

Note

Cluster logs are kept for 30 days.

Getting a cluster logGetting a cluster log

Management console
CLI
REST API
gRPC API
  1. Go to the folder page and select Yandex Managed Service for Valkey™.
  2. Click the name of the cluster you need and select the Logs tab.
  3. Specify the time period you want the log info for: enter it manually or select in the calendar using the date input field.
  4. Select the hosts in the line with the date input field if needed.

A list of log entries for the selected time period will be displayed. To view detailed information about an event, click the respective entry in the list.

If there are too many entries and not all of them are displayed, click Load more at the end of the list.

If you do not have the Yandex Cloud (CLI) command line interface yet, install and initialize it.

The folder specified when creating the CLI profile is used by default. To change the default folder, use the yc config set folder-id <folder_ID> command. You can specify a different folder using the --folder-name or --folder-id parameter.

  1. View the description of the CLI command to view cluster logs:

    yc managed-redis cluster list-logs --help
    
  2. Run the following command to get cluster logs (our example does not contain a complete list of available parameters):

    yc managed-redis cluster list-logs <cluster_name_or_ID> \
       --limit <entry_number_limit> \
       --columns <list_of_columns_for_data_output> \
       --filter <entry_filtration_settings> \
       --since <time_range_left_boundary> \
       --until <time_range_right_boundary>
    

    Where:

    • --limit: limits on the number of entries to output.

    • --columns: List of data columns:
      • hostname: Host name.
      • message: Message output by the service.
      • pid: ID of the current session’s server process.
      • role: Cluster component role, e.g., X or M (Sentinel and Master, respectively).
    • --filter: record filter settings, for example, message.hostname='node1.mdb.yandexcloud.net'.

    • --since: Left boundary of a time range in RFC-3339, HH:MM:SS format or a time interval relative to the current time. Examples: 2006-01-02T15:04:05Z, 15:04:05, 2h, 3h30m ago.

    • --until: right boundary of a time range, the format is similar to that of --since.

You can request the cluster name and ID with the list of clusters in the folder.

  1. Get an IAM token for API authentication and put it into the environment variable:
export IAM_TOKEN="<IAM_token>"
  1. Use the Cluster.ListLogs method and send the following request, e.g., via cURL:

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

    Where:

    • serviceType: Type of the service to request logs for. The possible value is REDIS.

    • columnFilter: List of data columns:

      • hostname: Host name.
      • message: Message output by the service.
      • pid: ID of the current session’s server process.
      • role: Cluster component role, e.g., X or M (Sentinel and Master, respectively).

      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: Right boundary of a time range, the format is the same as for fromTime.

    You can request the cluster ID with the list of clusters in the folder.

  2. View the server response to make sure the request was successful.

  1. Get an IAM token for API authentication and put it into the 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 the repository contents are stored in the ~/cloudapi/ directory.

  3. Use the ClusterService.ListLogs call and send the following request, e.g., via gRPCurl:

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

    Where:

    • service_type: Type of the service to request logs for. The possible value is REDIS.

    • column_filter: List of data columns:

      • hostname: Host name.
      • message: Message output by the service.
      • pid: ID of the current session’s server process.
      • role: Cluster component role, e.g., X or M (Sentinel and Master, respectively).

      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: Right boundary of a time range, the format is the same as for from_time.

    You can request the cluster ID with the list of clusters in the folder.

  4. View the server response to make sure the request was successful.

Getting a cluster log streamGetting a cluster log stream

This method allows you to get cluster logs in real time.

CLI
REST API
gRPC API

If you do not have the Yandex Cloud (CLI) command line interface yet, install and initialize it.

The folder specified when creating the CLI profile is used by default. To change the default folder, use the yc config set folder-id <folder_ID> command. You can specify a different folder using the --folder-name or --folder-id parameter.

To view cluster logs as they become available, run this command:

yc managed-redis cluster list-logs <cluster_name_or_ID> --follow

You can request the cluster name and ID with the list of clusters in the folder.

  1. Get an IAM token for API authentication and put it into the environment variable:
export IAM_TOKEN="<IAM_token>"
  1. Use the Cluster.StreamLogs method and send the following request, e.g., via cURL:

    curl \
        --request GET \
        --header "Authorization: Bearer $IAM_TOKEN" \
        --url 'https://mdb.api.cloud.yandex.net/managed-redis/v1/clusters/<cluster_ID>:stream_logs' \
        --url-query serviceType=<service_type> \
        --url-query columnFilter=<column_list> \
        --url-query fromTime=<time_range_left_boundary> \
        --url-query toTime=<time_range_right_boundary> \
        --url-query filter=<log_filter>
    

    Where:

    • serviceType: Type of the service to request logs for. The possible value is REDIS.

    • columnFilter: List of data columns:

      • hostname: Host name.
      • message: Message output by the service.
      • pid: ID of the current session’s server process.
      • role: Cluster component role, e.g., X or M (Sentinel and Master, respectively).

      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: Right boundary of a time range, the format is the same as for fromTime.

      If you omit this parameter, new logs will be sent to the log stream as they arrive. Semantically, this behavior is similar to tail -f.

    • filter: Log filter, e.g., message.hostname='node1.mdb.yandexcloud.net'.

      For more information about filters and their syntax, see the API reference.

    You can request the cluster ID with the list of clusters in the folder.

  2. View the server response to make sure the request was successful.

  1. Get an IAM token for API authentication and put it into the 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 the repository contents are stored in the ~/cloudapi/ directory.

  3. Use the ClusterService.StreamLogs call and send the following request, e.g., via gRPCurl:

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

    Where:

    • service_type: Type of the service to request logs for. The possible value is REDIS.

    • column_filter: List of data columns:

      • hostname: Host name.
      • message: Message output by the service.
      • pid: ID of the current session’s server process.
      • role: Cluster component role, e.g., X or M (Sentinel and Master, respectively).

      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: Right boundary of a time range, the format is the same as for from_time.

      If you omit this parameter, new logs will be sent to the log stream as they arrive. Semantically, this behavior is similar to tail -f.

    • filter: Log filter, e.g., message.hostname='node1.mdb.yandexcloud.net'.

      For more information about filters and their syntax, see the API reference.

    You can request the cluster ID with the list of clusters in the folder.

  4. View the server response to make sure the request was successful.

Was the article helpful?

Previous
Switching the master
Next
Monitoring the state of clusters and hosts
© 2025 Direct Cursus Technology L.L.C.