{
  "id": "hotkeys",
  "title": "HOTKEYS",
  "url": "https://redis.io/docs/latest/commands/hotkeys/",
  "summary": "A container for hotkeys tracking commands.",
  "tags": [
    "docs",
    "develop",
    "stack",
    "oss",
    "rs",
    "rc",
    "oss",
    "kubernetes",
    "clients"
  ],
  "last_updated": "2026-04-09T10:29:34-04:00",
  "page_type": "content",
  "content_hash": "f9f6025f8899ccc80d6550af5054c93f153a3dc2b2f9fc6cdacc40f3eb7b828d",
  "sections": [
    {
      "id": "overview",
      "title": "Overview",
      "role": "overview",
      "text": "This is a container command for hotkeys tracking commands that provides a method for identifying hotkeys inside a Redis server during a specified tracking time period.\n\nHotkeys in this context are defined by two metrics:\n* Percentage of CPU time spent on the key from the total time during the tracking period.\n* Percentage of network bytes (input + output) used for the key from the total network bytes used by Redis during the tracking period."
    },
    {
      "id": "usage",
      "title": "Usage",
      "role": "syntax",
      "text": "The general workflow is for the user to initiate a hotkeys tracking process which should run for some time. The keys' metrics are recorded inside a probabilistic data structure, after which the user is able to fetch the top K metrics.\n\nAvailable subcommands:\n\n- [`HOTKEYS START`]() - Starts hotkeys tracking with specified metrics.\n- [`HOTKEYS STOP`]() - Stops hotkeys tracking but preserves data.\n- [`HOTKEYS GET`]() - Returns tracking results and metadata.\n- [`HOTKEYS RESET`]() - Releases resources used for tracking."
    }
  ],
  "examples": []
}