Amazon ElastiCache Valkey monitoring
Amazon ElastiCache for Valkey is a fully managed, in-memory caching service from AWS that uses Valkey, an open-source, Redis-compatible key-value datastore. It delivers high performance, low latency, and scalability for real-time applications while reducing the overhead of managing servers or clusters manually.
With Site24x7's integration with Amazon ElastiCache for Valkey, you can monitor both serverless and cluster-based Valkey caches, track performance metrics, and get alerts when issues arise.
Overview
The integration covers serverless as well as cluster-based Valkey caches, including cluster-level monitoring, shard (node-group) level monitoring if cluster mode is enabled, and node-level monitoring. Status propagation is supported, so you can be notified when any child monitor, such as shards or nodes, changes status if thresholds are configured. You can monitor host-level metrics like CPU and memory, Valkey-specific metrics such as cache hits and misses, and even command-level metrics to track command usage and manage costs. For Valkey caches with logging enabled, alerts can also be triggered for errors in slow logs or engine logs.
Site24x7's integration with Amazon Elasticache Valkey provides the following monitors:
- ElastiCache Valkey Serverless : Monitor the health and performance of serverless Valkey caches to ensure low latency and cost-efficient scaling without manual intervention.
- ElastiCache Valkey Cluster: Get a consolidated view of the entire Valkey cluster’s availability, resource usage, and performance trends for better capacity planning and uptime. The following are the child monitors of ElastiCache Valkey Cluster:
- ElastiCache Valkey Cluster Shard : Track shard-level metrics like memory usage and replication health to quickly detect issues affecting specific node groups within a cluster.
- ElastiCache Valkey Cluster Node: Monitor individual node performance to identify failures or bottlenecks at the most granular level for faster troubleshooting.
Use case
An e-commerce company uses Amazon ElastiCache for Valkey to handle real-time caching for product catalog data, shopping cart sessions, and personalized recommendations. During peak traffic events like a flash sale, the cache experiences a sudden spike in requests. With Site24x7's integration, the company can monitor cluster health to ensure all nodes are running smoothly, detect replication lag early to prevent outdated data from being served, and analyze command-level metrics to identify heavy commands slowing down the cache.
Proactive alerts notify the team when memory usage or latency crosses thresholds, so they can take corrective actions like adding nodes or clearing stale data before customers are impacted. By correlating cache metrics with application performance, the team can quickly pinpoint whether slow page loads are caused by cache issues or application code, ensuring a fast and reliable shopping experience even during traffic spikes.
Benefits of Site24x7's Amazon Elasticache Valkey integration
Integrate your Amazon Elasticache Valkey environment with Site24x7 and leverage the following benefits:
- Track health and performance: Monitor the overall health and performance of your Valkey clusters in real time.
- Identify issues early: Detect memory pressure, replication lag, or network bottlenecks before they affect application performance.
- Use resources efficiently: Spot unused or under-utilized nodes to optimize resource allocation and costs.
- Ensure reliability: Maintain high availability and consistent data delivery with proactive alerts and historical trend reports.
- Leverage status propagation: Automatically trigger alerts when child monitors such as Elasticache Valkey Cluster Shard or Elasticache Valkey Cluster Node experience downtime or performance degradation.
Setup and configuration
- Log in to your Site24x7 account.
- Go to Cloud > AWS > Integrate AWS Account and create a cross-account IAM role to enable Site24x7 to access your AWS resources.
- On the Integrate AWS Account page, select Elasticache Valkey from the Services to be discovered list based on your requirement.
Permissions
Ensure that Site24x7 receives the following permissions to monitor Amazon Elasticache Valkey:
- "elasticache:DescribeServerlessCaches",
- "elasticache:DescribeCacheSubnetGroups",
- "elasticache:ListTagsForResource",
- "elasticache:DescribeCacheClusters",
- "elasticache:DescribeReplicationGroups",
- "elasticache:DescribeServerlessCacheSnapshots",
- "elasticache:DescribeSnapshots",
- "elasticache:DescribeEvents",
- "elasticache:DescribeUpdateActions"
Polling frequency
Site24x7 queries AWS service-level APIs according to the set polling frequency (from once a minute to once a day) to collect metrics from Amazon Elasticache Valkey monitors.
Supported metrics
The supported metrics for Amazon Elasticache Valkey monitors are given below.
Elasticache Valkey Serverless
The supported metrics for Elasticache Valkey Serverless monitor are given below.
| Metric name | Description | Statistics | Unit |
|---|---|---|---|
| Bytes Used For Cache | The total number of bytes used by the data stored in your cache. | Average | Bytes |
| ElastiCache Processing Units | The total number of ElastiCacheProcessingUnits (ECPUs) consumed by the requests executed on your cache. | Sum | Count |
| Successful Read Request Latency | Latency of successful read requests. | Average | Microseconds |
| Successful Write Request Latency | Latency of successful write requests. | Average | Microseconds |
| Total Commands Count | The total count of all commands executed on your cache. | Sum | Count |
| Cache Hit Rate | Indicates the hit rate of your cache. | Average | Percentage |
| Cache Hits | The number of successful read-only key lookups in the cache. | Sum | Count |
| Current Connections | The number of client connections to your cache. | Sum | Count |
| Throttled Commands | The number of requests that were throttled by ElastiCache because the workload was scaling faster than ElastiCache can scale. | Sum | Count |
| New Connections | The total number of connections that have been accepted by the server during this period. | Sum | Count |
| Current Items | The number of items in the cache. | Sum | Count |
| Current Volatile Items | The number of items in the cache with TTL. | Sum | Count |
| Network Bytes In | Total bytes transferred in to cache. | Average | Bytes |
| Network Bytes Out | Total bytes transferred out of cache. | Average | Bytes |
| Evictions | The count of keys evicted by the cache. | Sum | Count |
| IAM Authentication Expirations | The total number of expired IAM-authenticated Valkey connections. | Sum | Count |
| IAM Authentication Throttling | The total number of throttled IAM-authenticated Valkey AUTH or HELLO requests. | Sum | Count |
| Key Authorization Failures | The total number of failed attempts by users to access keys they don’t have permission to access. We suggest setting an alarm on this to detect unauthorized access attempts. | Sum | Count |
| Authentication Failures | The total number of failed attempts to authenticate to Valkey using the AUTH command. We suggest setting an alarm on this to detect unauthorized access attempts. | Sum | Count |
| Command Authorization Failures | The total number of failed attempts by users to run commands they don’t have permission to call. We suggest setting an alarm on this to detect unauthorized access attempts. | Sum | Count |
| Eval Based Commands | The number of get commands the cache has received. | Sum | Count |
| Eval Based Commands ECPUs | The ECPUs consumed by eval-based commands. | Sum | Count |
| Geo Spatial Based Commands | The total number of commands for geospatial-based commands. It's derived by summing all of the geo type of commands: geoadd , geodist , geohash , geopos , georadius , and georadiusbymember. | Sum | Count |
| Geo Spatial Based Commands ECPUs | The ECPUs consumed by geospatial-based commands. | Sum | Count |
| Get Type Commands | The total number of read-only type commands. This is derived from the Valkey commandstats statistic by summing all of the read-only type commands (get , hget , scard, lrange, and so on). | Sum | Count |
| Get Type Commands ECPUs | The ECPUs consumed by read commands. | Sum | Count |
| Hash Based Commands | The total number of commands that are hash based. This is derived from the Valkey commandstats statistic by summing all of the commands that act upon one or more hashes (hget , hkeys , hvals , hdel , and so on). | Sum | Count |
| Hash Based Commands ECPUs | The ECPUs consumed by hash-based commands. | Sum | Count |
| HyperLog Log Based Commands | The total number of HyperLogLog-based commands. This is derived from the Valkey commandstats statistic by summing all of the pf type of commands (pfadd , pfcount , pfmerge, and so on). | Sum | Count |
| HyperLog Log Based Commands ECPUs | The ECPUs consumed by HyperLog Log-based commands. | Sum | Count |
| JSON Based Commands | The total number of JSON commands, including both read and write commands. This is derived from the Valkey commandstats statistic by summing all JSON commands that act upon JSON keys. | Sum | Count |
| JSON Based Commands ECPUs | The ECPUs consumed by all JSON commands, including both read and write commands. | Sum | Count |
| JSON Based Get Commands | The total number of JSON read-only commands. This is derived from the Valkey commandstats statistic by summing all JSON read commands that act upon JSON keys. | Sum | Count |
| JSON Based Get Commands ECPUs | The ECPUs consumed by JSON read-only commands. | Sum | Count |
| JSON Based Set Commands | The total number of JSON write commands. This is derived from the Valkey commandstats statistic by summing all JSON write commands that act upon JSON keys. | Sum | Count |
| JSON Based Set Commands ECPUs | The ECPUs consumed by JSON write commands. | Sum | Count |
| Key Based Commands | The total number of commands that are key based. This is derived from the Valkey commandstats statistic by summing all of the commands that act upon one or more keys across multiple data structures (del , expire , rename, and so on). | Sum | Count |
| Key Based Commands ECPUs | The ECPUs consumed by key-based commands. | Sum | Count |
| List Based Commands | The total number of commands that are list based. This is derived from the Valkey commandstats statistic by summing all of the commands that act upon one or more lists (lindex , lrange , lpush, ltrim, and so on). | Sum | Count |
| List Based Commands ECPUs | The ECPUs consumed by list-based commands. | Sum | Count |
| Non Key Type Commands | The total number of commands that are not key based. This is derived from the Valkey commandstats statistic by summing all of the commands that do not act upon a key, for example, acl , dbsize or info. | Sum | Count |
| Non Key Type Commands ECPUs | The ECPUs consumed by non-key-based commands. | Sum | Count |
| PubSub Based Commands | The total number of commands for pub/sub functionality. This is derived from the Valkey commandstatsstatistics by summing all of the commands used for pub/sub functionality: psubscribe , publish , pubsub, pubsubscribe, ssubscribe, sunsubscribe, spublish, subscribe, and unsubscribe. | Sum | Count |
| PubSub Based Commands ECPUs | The ECPUs consumed by pub/sub-based commands. | Sum | Count |
| Set Based Commands | The total number of commands that are set based. This is derived from the Valkey commandstats statistic by summing all of the commands that act upon one or more sets (scard , sdiff , sadd, sunion, and so on). | Sum | Count |
| Set Based Commands ECPUs | The ECPUs consumed by set-based commands. | Sum | Count |
| Set Type Commands | The total number of write types of commands. This is derived from the Valkey commandstats statistic by summing all of the mutative types of commands that operate on data (set , hset , sadd, lpop, and so on). | Sum | Count |
| Set Type Commands ECPUs | The ECPUs consumed by write commands. | Sum | Count |
| Sorted Set Based Commands | The total number of commands that are sorted set based. This is derived from the Valkey commandstats statistic by summing all of the commands that act upon one or more sorted sets (zcount , zrange , zrank, zadd, and so on). | Sum | Count |
| Sorted Set Based Commands ECPUs | The ECPUs consumed by sorted-based commands. | Sum | Count |
| String Based Commands | The total number of commands that are string based. This is derived from the Valkey commandstats statistic by summing all of the commands that act upon one or more strings (strlen , setex , setrange, and so on). | Sum | Count |
| String Based Commands ECPUs | The ECPUs consumed by string-based commands. | Sum | Count |
| Stream Based Commands | The total number of commands that are stream based. This is derived from the Valkey commandstats statistic by summing all of the commands that act upon one or more streams data types (xrange , xlen , xadd, xdel, and so on). | Sum | Count |
| Stream Based Commands ECPUs | The ECPUs consumed by stream-based commands. | Sum | Count |
Elasticache Valkey Cluster
The supported metrics for Elasticache Valkey Cluster monitor are given below.
| Metric name | Description | Statistics | Unit |
|---|---|---|---|
| Total Number of Shards | The total number of shards (node-groups) in the cluster cache. | Sum | Count |
| Total Number of Nodes | The total number of nodes in the cluster cache. | Sum | Count |
| Engine CPU Utilization | Provides CPU utilization of the Valkey engine thread. Valkey is single-threaded, so you can use this metric to analyze the load of the process itself. | Average | Percentage |
| Database Capacity Usage Counted for Evict Percentage | The percentage of total data capacity for the cluster that is in use, excluding the memory used for overhead and cache-oblivious (COB). | Average | Percentage |
| Database Memory Usage Counted For Evict Percentage | Percentage of the memory for the cluster that is in use, excluding memory used for overhead and COB. | Average | Percentage |
Elasticache Valkey Cluster Shard
The supported metrics for Elasticache Valkey Cluster Shard monitor are given below.
| Metric name | Description | Statistics | Unit |
|---|---|---|---|
|
Total number of nodes |
The total number of nodes in the shard (node-group). |
Sum |
Count |
|
Engine CPU Utilization |
Provides CPU utilization of the Valkey engine thread for the shard. |
Average |
Percentage |
|
Database Capacity Usage Counted For Evict Percentage |
The percentage of total data capacity for the shard that is in use, excluding the memory used for overhead and COB. |
Average |
Percentage |
|
Database Memory Usage Counted For Evict Percentage |
The percentage of memory for the shard that is in use, excluding memory used for overhead and COB. |
Average |
Percentage |
Elasticache Valkey Cluster Node
The supported metrics for Elasticache Valkey Cluster Node monitor are given below.
| Metric name | Description | Statistics | Unit |
|---|---|---|---|
|
CPU Utilization |
The percentage of CPU utilization for the entire node. |
Average |
Percentage |
|
CPU Credit Balance |
The number of earned CPU credits that an instance has accrued since it was launched or started. For T2 Standard, the CPUCreditBalance also includes the number of launch credits that have been accrued. |
Sum |
Credits |
|
CPU Credit Usage |
The number of CPU credits spent by the instance for CPU utilization. |
Sum |
Credits |
|
Freeable Memory |
The amount of free memory available on the host. This is derived from the RAM, buffers, and cache that the OS reports as freeable. |
Average |
Bytes |
|
Network Bytes In |
The number of bytes the host has read from the network. |
Average |
Bytes |
|
Network Bytes Out |
The number of bytes sent out on all network interfaces by the instance. |
Average |
Bytes |
|
Network Packets In |
The number of packets received on all network interfaces by the instance. This metric identifies the volume of incoming traffic in terms of the number of packets on a single instance. |
Average |
Count |
|
Network Packets Out |
The number of packets sent out on all network interfaces by the instance. This metric identifies the volume of outgoing traffic in terms of the number of packets on a single instance. |
Sum |
Count |
|
Network Bandwidth In Allowance Exceeded |
The number of packets queued or dropped because the inbound aggregate bandwidth exceeded the maximum for the instance. |
Sum |
Count |
|
Network Conntrack Allowance Exceeded |
The number of packets dropped because connection tracking exceeded the maximum for the instance and new connections could not be established. This can result in packet loss for traffic to or from the instance. |
Sum |
Count |
|
Network Bandwidth Out Allowance Exceeded |
The number of packets queued or dropped because the outbound aggregate bandwidth exceeded the maximum for the instance. |
Sum |
Count |
|
Network Packets Per Second Allowance Exceeded |
The number of packets queued or dropped because the bidirectional packets per second exceeded the maximum for the instance. |
Sum |
Count |
|
Network Max Bytes In |
The maximum per second burst of received bytes within each minute. |
Average |
Bytes |
|
Network Max Bytes Out |
The maximum per second burst of transmitted bytes within each minute. |
Average |
Bytes |
|
Network Max Packets In |
The maximum per second burst received packets within each minute. |
Sum |
Count |
|
Network Max Packets Out |
The maximum per second burst of transmitted packets within each minute. |
Sum |
Count |
|
Swap Usage |
The amount of swap used on the host. |
Average |
Bytes |
|
Active Defrag Hits |
The number of value reallocations per minute performed by the active defragmentation process. |
Sum |
Count |
|
Authentication Failures |
The total number of failed attempts to authenticate to Valkey using the AUTH command. |
Sum |
Count |
|
Bytes Used For Cache |
The total number of bytes allocated by Valkey for all purposes, including the dataset , buffers , and so on. |
Average |
Bytes |
|
Bytes Read From Disk |
The total number of bytes read from disk per minute. |
Average |
Bytes |
|
Bytes Written To Disk |
The total number of bytes written to disk per minute. |
Average |
Bytes |
|
Cache Hits |
The number of successful read-only key lookups in the main dictionary. |
Sum |
Count |
|
Cache Misses |
The number of unsuccessful read-only key lookups in the main dictionary. |
Sum |
Count |
|
Command Authorization Failures |
The total number of failed attempts by users to run commands they don’t have permission to call. |
Sum |
Count |
|
Cache Hit Rate |
Indicates the usage efficiency of the Valkey instance. If the cache ratio is lower than about 0.8, it means that a significant amount of keys are evicted, expired, or don't exist. |
Average |
Percentage |
|
Channel Authorization Failures |
The total number of failed attempts by users to access channels they do not have permission to access. |
Sum |
Count |
|
Current Connections |
The number of client connections, excluding connections from read replicas. |
Sum |
Count |
|
Current Items |
The number of items in the cache. This is derived from the keyspace statistic, summing all of the keys in the entire keyspace. |
Sum |
Count |
|
Current Volatile Items |
The total number of keys in all databases that have a time-to-live (TTL) set. This is derived from the expires statistic, summing all of the keys with a TTL set in the entire keyspace. |
Sum |
Count |
|
Database Capacity Usage Percentage |
The percentage of the total data capacity for the cluster that is in use. |
Average |
Percentage |
|
Database Memory Usage Percentage |
The percentage of the memory for the cluster that is in use. |
Average |
Percentage |
|
DB0 Average TTL |
Exposes avg_ttl of Database 0 (DB0)from the keyspace statistic of the Valkey command. |
Average |
Milliseconds |
|
Evictions |
The number of keys that have been evicted due to the maxmemory limit. |
Sum |
Count |
|
Global Datastore Replication Lag |
This is the lag between the secondary region's primary node and the primary region's primary node. For cluster mode enabled Valkey, the lag indicates the maximum delay among the shards. |
Average |
Seconds |
|
IAM Authentication Expirations |
The total number of expired IAM-authenticated Valkey connections. |
Sum |
Count |
|
IAM Authentication Throttling |
The total number of throttled IAM-authenticated Valkey AUTH or HELLO requests. |
Sum |
Count |
|
Key Authorization Failures |
The total number of failed attempts by users to access keys they don’t have permission to access. |
Sum |
Count |
|
Keys Tracked |
The number of keys being tracked by Valkey key tracking as a percentage of tracking-table-max-keys. Key tracking is used to aid client-side caching and notifies clients when keys are modified. |
Sum |
Count |
|
Memory Fragmentation Ratio |
Indicates the efficiency in the allocation of memory of the Valkey engine. Certain thresholds signify different behaviors. |
Average |
Count |
|
New Connections |
The total number of connections that have been accepted by the server during this period. |
Sum |
Count |
|
Number of Items Read From Disk |
The total number of items retrieved from disk per minute. |
Sum |
Count |
|
Number of Items Written To Disk |
The total number of items written to disk per minute. |
Sum |
Count |
|
Reclaimed |
The total number of key expiration events. |
Sum |
Count |
|
Replication Bytes |
For nodes in a replicated configuration, Replication Bytes reports the number of bytes that the primary is sending to all of its replicas. |
Average |
Bytes |
|
Replication Lag |
This metric is only applicable for a node running as a read replica. It represents how far behind, in seconds, the replica is in applying changes from the primary node. |
Average |
Seconds |
|
Successful Write Request Latency |
The latency of successful write requests. |
Average |
Microseconds |
|
Successful Read Request Latency |
The latency of successful read requests. |
Average |
Microseconds |
|
Error Count |
The total number of failed commands during the specified time period. |
Sum |
Count |
|
Cluster Based Commands |
The total number of commands that are cluster based. This is derived from the commandstats statistic by summing all of the commands that act upon a cluster (cluster slot, cluster info, and so on). |
Sum |
Count |
|
Cluster Based Commands Latency |
The latency of cluster-based commands. |
Average |
Microseconds |
|
Eval Based Commands |
The total number of commands for eval-based commands. |
Sum |
Count |
|
Eval Based Commands Latency |
The latency of eval-based commands. |
Average |
Microseconds |
|
Geo Spatial Based Commands |
The total number of commands for geospatial-based commands. This is derived from the commandstats statistic. It's derived by summing all of the geo type of commands: geoadd , geodist , geohash, geopos, georadius, and georadiusbymember. |
Sum |
Count |
|
Geo Spatial Based Commands Latency |
The latency of geospatial-based commands. |
Average |
Microseconds |
|
Get Type Commands |
The total number of read-only type commands. This is derived from the commandstats statistic by summing all of the read-only type commands (get , hget , scard, lrange, and so on). |
Sum |
Count |
|
Get Type Commands Latency |
The latency of read commands. |
Average |
Microseconds |
|
Hash Based Commands |
The total number of commands that are hash based. This is derived from the commandstats statistic by summing all of the commands that act upon one or more hashes (hget , hkeys , hvals, hdel, and so on). |
Sum |
Count |
|
Hash Based Commands Latency |
The latency of hash-based commands. |
Average |
Microseconds |
|
HyperLog Log Based Commands |
The total number of HyperLogLog-based commands. This is derived from the commandstats statistic by summing all of the pf type of commands (pfadd , pfcount , pfmerge, and so on). |
Sum |
Count |
|
HyperLog Log Based Commands Latency |
The latency of HyperLogLog-based commands. |
Average |
Microseconds |
|
JSON Based Commands |
The total number of JSON commands, including both read and write commands. This is derived from the commandstats statistic by summing all JSON commands that act upon JSON keys. |
Sum |
Count |
|
JSON Based Commands Latency |
The latency of all JSON commands, including both read and write commands. |
Average |
Microseconds |
|
JSON Based Get Commands |
The total number of JSON read-only commands. This is derived from the commandstats statistic by summing all JSON read commands that act upon JSON keys. |
Sum |
Count |
|
JSON Based Get Commands Latency |
The latency of JSON read-only commands. |
Average |
Microseconds |
|
JSON Based Set Commands |
The total number of JSON write commands. This is derived from the commandstats statistic by summing all JSON write commands that act upon JSON keys. |
Sum |
Count |
|
JSON Based Set Commands Latency |
The latency of JSON write commands. |
Average |
Microseconds |
|
Key Based Commands |
The total number of commands that are key based. This is derived from the commandstats statistic by summing all of the commands that act upon one or more keys across multiple data structures (del , expire , rename, and so on). |
Sum |
Count |
|
Key Based Commands Latency |
The latency of key-based commands. |
Average |
Microseconds |
|
List Based Commands |
The total number of commands that are list based. This is derived from the commandstats statistic by summing all of the commands that act upon one or more lists (lindex , lrange , lpush, ltrim, and so on). |
Sum |
Count |
|
List Based Commands Latency |
The latency of list-based commands. |
Average |
Microseconds |
|
Non Key Type Commands |
The total number of commands that are not key based. This is derived from the commandstats statistic by summing all of the commands that do not act upon a key, for example, acl , dbsize or info . |
Sum |
Count |
|
Non Key Type Commands Latency |
The latency of non-key-based commands. |
Average |
Microseconds |
|
PubSub Based Commands |
The total number of commands for pub/sub functionality. This is derived from the commandstatsstatistics by summing all of the commands used for pub/sub functionality: psubscribe , publish , pubsub, punsubscribe, ssubscribe, sunsubscribe, spublish, subscribe, and unsubscribe. |
Sum |
Count |
|
PubSub Based Commands Latency |
The latency of pub/sub-based commands. |
Average |
Microseconds |
|
Set Based Commands |
The total number of commands that are set based. This is derived from the commandstats statistic by summing all of the commands that act upon one or more sets (scard , sdiff , sadd, sunion, and so on). |
Sum |
Count |
|
Set Based Commands Latency |
The latency of set-based commands. |
Average |
Microseconds |
|
Set Type Commands |
The total number of write types of commands. This is derived from the commandstats statistic by summing all of the mutative types of commands that operate on data (set , hset , sadd, lpop, and so on). |
Sum |
Count |
|
Set Type Commands Latency |
The latency of write commands. |
Average |
Microseconds |
|
Sorted Set Based Commands |
The total number of commands that are sorted set based. This is derived from the commandstats statistic by summing all of the commands that act upon one or more sorted sets (zcount , zrange , zrank, zadd, and so on). |
Sum |
Count |
|
Sorted Set Based Commands Latency |
The latency of sorted-based commands. |
Average |
Microseconds |
|
String Based Commands |
The total number of commands that are string based. This is derived from the commandstats statistic by summing all of the commands that act upon one or more strings (strlen , setex , setrange, and so on). |
Sum |
Count |
|
String Based Commands Latency |
The latency of string-based commands. |
Average |
Microseconds |
|
Stream Based Commands |
The total number of commands that are stream based. This is derived from the commandstats statistic by summing all of the commands that act upon one or more streams data types (xrange , xlen , xadd, xdel, and so on). |
Sum |
Count |
|
Stream Based Commands Latency |
Latency of stream-based commands. |
Average |
Milliseconds |
Threshold configuration
To configure thresholds for a Elasticache Valkey monitors:
- Log in to your Site24x7 account and navigate to Admin > Configuration Profiles > Threshold and Availability.
- Click Add Threshold Profile.
- Select the applicable monitor type from the Monitor Type drop-down menu. The available monitor types are ElastiCache Valkey Serverless, Elasticache Valkey Cluster, Elasticache Valkey Cluster Shard, and Elasticache Valkey Cluster Node.
- Provide an appropriate name in the Display Name field.
- The supported metrics are displayed in the Threshold Configuration section. You can set threshold values for all the metrics mentioned above.
- Click Save.
Status propagation in Elasticache Valkey Cluster monitor
Site24x7's Elasticache Valkey integration includes the status propagation feature, which ensures that alerts from child monitors are propagated to the parent Elasticache Valkey Cluster monitor. By enabling the Notify for Any Child Monitor Status Changes option on the Edit Threshold Profile page, you can streamline how alerts are handled across your Elasticache Valkey Cluster resources.
Child monitors, such as Elasticache Valkey Cluster Shard, and Elasticache Valkey Cluster Node, will notify the parent Elasticache Valkey Cluster monitor of any status changes. This propagation helps you maintain a centralized view of all alerts and ensures timely responses to potential issues.
For example, if an issue occurs with a shard or node in the Valkey cluster, alerts will not be visible at the child monitor level because alerts are disabled for child monitors. The alerts will appear only at the parent ElastiCache Valkey Cluster monitor level, and only if status propagation is enabled and the required child monitor configurations are set up in the child monitor tabs.
Licensing
- Each Elasticache Valkey Serverless monitor utilizes one basic monitor license.
- Each Elasticache Valkey Cluster monitor utilizes one basic monitor license.
- Each Elasticache Valkey Cluster Shard monitor is a free monitor.
- Each Elasticache Valkey Cluster Node utilizes one basic monitor license.
Viewing Amazon Elasticache Valkey data
To monitor your Amazon Elasticache Valkey environment, log in to your Site24x7 account and navigate to Cloud > AWS > Amazon Elasticache Valkey.
Monitor data
The monitor data for each Amazon Elasticache Valkey monitor is given below.
Elasticache Valkey Serverless
The monitor data for Elasticache Valkey Serverless monitor is given below.
Summary
The Summary tab provides an overview of the events timeline and metrics in form of charts.
Command Metrics
The Command Metrics tab tracks the number of specialized or utility commands executed in the ElastiCache Valkey cluster over time. It helps you understand command usage patterns and identify unusual activity or performance issues.
Configuration
The Configuration tab displays all key configuration details of the monitored ElastiCache Valkey Serverless monitor. It helps you quickly verify setup parameters, connectivity information, and resource settings without logging into the AWS console.
Events
The Events tab shows the events associated to the Valkey serverless cache.
Backups
The Backups tab displays a list of all backups associated with the monitored ElastiCache Valkey Serverless monitor. It provides details such as the Backup Name, Type (automated or manual), Status, Cache Size, Creation Date, and Shard Information if available. This tab helps you verify backup availability, track when backups were taken, and ensure their successful completion. It also supports auditing and disaster recovery needs by giving you a clear view of all backup activities in one place.
Outages
The Outages tab provides details on an outage's start time, end time, duration, and comments, if any.
Inventory
Obtain details like Cache Name, Region, and Monitor Licensing Category from the Inventory tab. Set and view the Threshold and Availability Profile and the Notification Profile according to the user in this tab.
Log Report
This tab provides a consolidated report of the Elasticache Valkey Serverless monitor's log status, which can be downloaded as a CSV file.
Alert Logs
This tab displays a chronological list of all triggered alerts related to the Elasticache Valkey Serverless monitor. This tab helps you trace alert history and severity to assess issues and validate threshold settings.
Elasticache Valkey Cluster
The monitor data for Elasticache Valkey Cluster monitor is given below.
Summary
The Summary tab provides an overview of the events timeline and metrics in form of charts.
Shards
The Shards tab shows the list of ElastiCache Valkey Cluster Shard monitors for all node groups (shards) in the cluster, along with their status, monitor type, and available actions. You can configure thresholds for individual shard monitors by clicking the Action option (pencil icon) or apply thresholds in bulk using the Threshold Configuration button. You can also choose which child monitors to receive alerts for using these same options. To ensure alerts are triggered when a child monitor’s status changes, enable the Notify for any child monitor status changes option in the threshold profile of the Cluster monitor. Clicking on a shard monitor opens the detailed ElastiCache Valkey Cluster Shard monitor page.
Nodes
The Nodes tab lists all ElastiCache Valkey Cluster Node monitors for the nodes in the cluster, along with their status, monitor type, and available actions. You can configure thresholds for individual node monitors by clicking the Action option (pencil icon) or apply thresholds in bulk using the Threshold Configuration button. Make sure to configure alerts for the required child monitors in this tab to receive notifications.
Also, ensure the Notify for any child monitor status changes option is enabled in the threshold profile of the Cluster monitor; alerts will not be triggered unless this option is turned on. Clicking on a node monitor opens the detailed ElastiCache Valkey Cluster Node monitor page.
Configuration
View the configuration information of Elasticache Valkey Cluster monitors, such as Region, Cache Name, Cache Status, and Cluster Mode in the Configuration tab.
Backups
The Backups tab displays a list of all backups associated with the monitored ElastiCache Valkey Cluster monitor. It provides details such as the Backup Name, Type (automated or manual), Status, Cache Size, Creation Date, and Shard Information if available. This tab helps you verify backup availability, track when backups were taken, and ensure their successful completion. It also supports auditing and disaster recovery needs by giving you a clear view of all backup activities in one place.
Service Updates
View all service updates relevant to the cluster from the Service Updates tab.
Outages
The Outages tab provides details on an outage's Start Time, End Time, Duration, and Comments, if any.
Inventory
Obtain details like Cache Name, Region, and Monitor Licensing Category from the Inventory tab. Set and view the Threshold and Availability Profile and the Notification Profile according to the user in this tab.
Log Report
This tab provides a consolidated report of the Elasticache Valkey Serverless monitor's log status, which can be downloaded as a CSV file.
Alert Logs
This tab displays a chronological list of all triggered alerts related to the Elasticache Valkey Serverless monitor. This tab helps you trace alert history and severity to assess issues and validate threshold settings.
Elasticache Valkey Cluster Shard
The monitor data for Elasticache Valkey Cluster Shard monitor is given below.
Summary
The Summary tab provides an overview of the events timeline and metrics in form of charts.
Nodes
The Nodes tab lists all ElastiCache Valkey Cluster Node monitors for the nodes in the shard, along with their status, monitor type, and available actions. You can configure thresholds for individual node monitors by clicking the Action option (pencil icon) or apply thresholds in bulk using the Threshold Configuration button. Make sure to configure alerts for the required child monitors in this tab to receive notifications.
Also, ensure the Notify for any child monitor status changes option is enabled in the threshold profile of the Cluster monitor; alerts will not be triggered unless this option is turned on. Clicking on a node monitor opens the detailed ElastiCache Valkey Cluster Node monitor page.
Configuration
View the configuration information of Elasticache Valkey Cluster Shard monitors, such as Region, Cache Name, Node Group ID, and Shard Status in the Configuration tab.
Outages
The Outages tab provides details on an outage's Start Time, End Time, Duration, and Comments, if any.
Inventory
Obtain details like Cache Name, Region, and Monitor Licensing Category from the Inventory tab. Set and view the Threshold and Availability Profile and the Notification Profile according to the user in this tab.
Log Report
This tab provides a consolidated report of the Elasticache Valkey Cluster Shard monitor's log status, which can be downloaded as a CSV file.
Alert Logs
This tab displays a chronological list of all triggered alerts related to the Elasticache Valkey Cluster Shard monitor. This tab helps you trace alert history and severity to assess issues and validate threshold settings.
Elasticache Valkey Cluster Node
The monitor data for Elasticache Valkey Cluster Node monitor is given below.
Summary
The Summary tab provides an overview of the events timeline and metrics in form of charts.
Valkey Metrics
The Valkey Metrics tab provides key operational metrics for a Valkey cluster or node. It helps you monitor memory efficiency and security-related failures in real time.
Command Metrics
The Command Metrics tab tracks the number of specialized or utility commands executed in the ElastiCache Valkey cluster nodes over time. It helps you understand command usage patterns and identify unusual activity or performance issues.
Configuration
View the configuration information of Elasticache Valkey Cluster Node monitors, such as Region, Cache Name, Engine Name, and Cache Node Name in the Configuration tab.
Outages
The Outages tab provides details on an outage's Start Time, End Time, Duration, and Comments, if any.
Inventory
Obtain details like Cache Name, Region, and Monitor Licensing Category from the Inventory tab. Set and view the Threshold and Availability Profile and the Notification Profile according to the user in this tab.
Log Report
This tab provides a consolidated report of the Elasticache Valkey Cluster Node monitor's log status, which can be downloaded as a CSV file.
Alert Logs
This tab displays a chronological list of all triggered alerts related to the Elasticache Valkey Cluster Node monitor. This tab helps you trace alert history and severity to assess issues and validate threshold settings.
-
On this page
- Overview
- Use case
- Benefits of Site24x7's Amazon Elasticache Valkey integration
- Setup and configuration
- Permissions
- Polling frequency
- Supported metrics
- Threshold configuration
- Status propagation in Elasticache Valkey Cluster monitor
- Licensing
- Viewing Amazon Elasticache Valkey data
- Monitor data