# Metrics for Valkey and Redis OSS The `Amazon ElastiCache` namespace includes the following Valkey and Redis OSS metrics. These metrics are the same when using the Valkey engine. With the exception of `ReplicationLag`, `EngineCPUUtilization`, `SuccessfulWriteRequestLatency`, and `SuccessfulReadRequestLatency`, these metrics are derived from the **info** command. Each metric is calculated at the cache node level. For complete documentation of the **info** command, see [http://valkey.io/commands/info](https://valkey.io/commands/info). **See Also** + [Host-Level Metrics](CacheMetrics.HostLevel.md) [\[See the AWS documentation website for more details\]](http://docs.aws.amazon.com/AmazonElastiCache/latest/dg/CacheMetrics.Redis.html) The following are aggregations of certain kinds of commands, derived from **info commandstats**. The commandstats section provides statistics based on the command type, including the number of calls, the total CPU time consumed by these commands, and the average CPU consumed per command execution. For each command type, the following line is added: `cmdstat_XXX: calls=XXX,usec=XXX,usec_per_call=XXX`. The latency metrics listed following are calculated using commandstats statistic from [INFO](https://valkey.io/commands/info). They are calculated in the following way: `delta(usec)/delta(calls)`. `delta` is calculated as the diff within one minute. Latency is defined as CPU time taken by ElastiCache to process the command. Note that for clusters using data tiering, the time taken to fetch items from SSD is not included in these measurements. For a full list of available commands, see [commands](https://valkey.io/commands) in the Valkey documentation. | Metric | Description | Unit | | --- | --- | --- | | ClusterBasedCmds | 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). | Count | | ClusterBasedCmdsLatency | Latency of cluster-based commands. | Microseconds | | EvalBasedCmds | The total number of commands for eval-based commands. This is derived from the commandstats statistic by summing eval, evalsha. | Count | | EvalBasedCmdsLatency | Latency of eval-based commands. | Microseconds | | GeoSpatialBasedCmds | 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. | Count | | GeoSpatialBasedCmdsLatency | Latency of geospatial-based commands. | Microseconds | | GetTypeCmds | 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.) | Count | | GetTypeCmdsLatency | Latency of read commands. | Microseconds | | HashBasedCmds | 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). | Count | | HashBasedCmdsLatency | Latency of hash-based commands. | Microseconds | | HyperLogLogBasedCmds | 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.). | Count | | HyperLogLogBasedCmdsLatency | Latency of HyperLogLog-based commands. | Microseconds | | JsonBasedCmds | 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. | Count | | JsonBasedCmdsLatency | Latency of all JSON commands, including both read and write commands. | Microseconds | | JsonBasedGetCmds | 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. | Count | | JsonBasedGetCmdsLatency | Latency of JSON read-only commands. | Microseconds | | JsonBasedSetCmds | 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. | Count | | JsonBasedSetCmdsLatency | Latency of JSON write commands. | Microseconds | | KeyBasedCmds | 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.). | Count | | KeyBasedCmdsLatency | Latency of key-based commands. | Microseconds | | ListBasedCmds | 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). | Count | | ListBasedCmdsLatency | Latency of list-based commands. | Microseconds | | NonKeyTypeCmds | 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. | Count | | NonKeyTypeCmdsLatency | Latency of non-key-based commands. | Microseconds | | PubSubBasedCmds | 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. | Count | | PubSubBasedCmdsLatency | Latency of pub/sub-based commands. | Microseconds | | SetBasedCmds | 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). | Count | | SetBasedCmdsLatency | Latency of set-based commands. | Microseconds | | SetTypeCmds | 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.) | Count | | SetTypeCmdsLatency | Latency of write commands. | Microseconds | | SortedSetBasedCmds | 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). | Count | | SortedSetBasedCmdsLatency | Latency of sorted-based commands. | Microseconds | | StringBasedCmds | 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). | Count | | StringBasedCmdsLatency | Latency of string-based commands. | Microseconds | | StreamBasedCmds | 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). | Count | | StreamBasedCmdsLatency | Latency of stream-based commands. | Microseconds | | SearchBasedCmds | The total number of Search commands, including both read and write commands. This is derived from the commandstats statistic by summing all Search commands. | Count | | SearchBasedCmdsLatency | Latency of all Search commands, including both read and write commands. | Microseconds | | SearchBasedGetCmds | The total number of Search read-only commands. This is derived from the commandstats statistic by summing all Search read commands. | Count | | SearchBasedGetCmdsLatency | Latency of Search read-only commands. | Microseconds | | SearchBasedSetCmds | The total number of Search write commands. This is derived from the commandstats statistic by summing all Search write commands. | Count | | SearchBasedSetCmdsLatency | Latency of Search write commands. | Microseconds |