Viewing Valkey™ cluster logs
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 log
- Go to the folder page and select Yandex Managed Service for Valkey™.
- Click the name of the cluster you need and select the
Logs tab. - Specify the time period you want the log info for: enter it manually or select in the calendar using the date input field.
- 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 command line interface yet, install and initialize it.
The folder specified in the CLI profile is used by default. You can specify a different folder using the --folder-name
or --folder-id
parameter.
-
View the description of the CLI command to view cluster logs:
yc managed-redis cluster list-logs --help
-
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 columns for data output: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
orM
(Sentinel
andMaster
, 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.
- Get an IAM token for API authentication and put it into the environment variable:
export IAM_TOKEN="<IAM_token>"
-
Use the Cluster.ListLogs method and make a 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 isREDIS
. -
columnFilter
: List of columns for data output: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
orM
(Sentinel
andMaster
, 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 forfromTime
.
You can get the cluster ID with a list of clusters in the folder.
-
-
View the server response to make sure the request was successful.
-
Get an IAM token for API authentication and put it into the environment variable:
export IAM_TOKEN="<IAM_token>"
-
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. -
Use the ClusterService.ListLogs call and make a 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 isREDIS
. -
column_filter
: List of columns for data output: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
orM
(Sentinel
andMaster
, 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 forfrom_time
.
You can get the cluster ID with a list of clusters in the folder.
-
-
View the server response to make sure the request was successful.
Getting a cluster log stream
This method allows you to get cluster logs in real time.
If you do not have the Yandex Cloud command line interface yet, install and initialize it.
The folder specified in the CLI profile is used by default. 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.
- Get an IAM token for API authentication and put it into the environment variable:
export IAM_TOKEN="<IAM_token>"
-
Use the Cluster.StreamLogs method and make a 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 isREDIS
. -
columnFilter
: List of columns for data output: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
orM
(Sentinel
andMaster
, 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 forfromTime
.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 get the cluster ID with a list of clusters in the folder.
-
-
View the server response to make sure the request was successful.
-
Get an IAM token for API authentication and put it into the environment variable:
export IAM_TOKEN="<IAM_token>"
-
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. -
Use the ClusterService.StreamLogs call and make a 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 isREDIS
. -
column_filter
: List of columns for data output: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
orM
(Sentinel
andMaster
, 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 forfrom_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 get the cluster ID with a list of clusters in the folder.
-
-
View the server response to make sure the request was successful.