[[["이해하기 쉬움","easyToUnderstand","thumb-up"],["문제가 해결됨","solvedMyProblem","thumb-up"],["기타","otherUp","thumb-up"]],[["이해하기 어려움","hardToUnderstand","thumb-down"],["잘못된 정보 또는 샘플 코드","incorrectInformationOrSampleCode","thumb-down"],["필요한 정보/샘플이 없음","missingTheInformationSamplesINeed","thumb-down"],["번역 문제","translationIssue","thumb-down"],["기타","otherDown","thumb-down"]],["최종 업데이트: 2025-09-05(UTC)"],[],[],null,["# Access Key Visualizer\n\nKey Visualizer is enabled in Spanner by default.\n\nBefore you begin\n----------------\n\nTo view Key Visualizer, you need the following [Identity and Access Management\n(IAM) permission](../iam):\n\n- `spanner.databases.read`\n\nIf you are a fine-grained access control user, you must have been granted access to:\n\n- the `spanner_sys_reader` system role or one of its member roles.\n\nFor more information, see [About fine-grained access control](../fgac-about) and\n[Fine-grained access control system roles](../fgac-system-roles).\n\nAccess the Key Visualizer interface\n-----------------------------------\n\nYou access the Key Visualizer tool from the [Google Cloud console](https://console.cloud.google.com/).\n\nTo access Key Visualizer:\n\n1. From the [Spanner page](https://console.cloud.google.com/spanner/) of the\n Google Cloud console, select an instance.\n\n2. Select a database to investigate.\n\n3. In the navigation menu, under **Observability** , select\n **Key Visualizer**.\n\nDisable Key Visualizer\n----------------------\n\nKey Visualizer is controlled by the `enable_key_visualizer`\ndatabase option. The default value is `true`.\n\nTo disable Key Visualizer, set the value of the `enable_key_visualizer`\ndatabase option to `false`. The DDL syntax to disable Key Visualizer\nis: \n\n ALTER DATABASE `\u003cvar translate=\"no\"\u003edatabase_id\u003c/var\u003e` SET OPTIONS (enable_key_visualizer=false)\n\nIf your database ID contains characters other than letters, numbers, or\nunderscores, be sure to enclose the ID with backticks (\\`\\`).\n\nThe statement can be sent using a gcloud command, or in an `UpdateDatabaseDdl`\ngRPC/REST request. For example: \n\n gcloud spanner databases ddl update \u003cvar translate=\"no\"\u003e\u003cspan class=\"devsite-syntax-n\"\u003edatabase_id\u003c/span\u003e\u003c/var\u003e --instance=\u003cvar translate=\"no\"\u003e\u003cspan class=\"devsite-syntax-n\"\u003einstance_id\u003c/span\u003e\u003c/var\u003e \\\n --ddl='ALTER DATABASE `\u003cvar translate=\"no\"\u003edatabase_id\u003c/var\u003e` SET OPTIONS ( enable_key_visualizer=false )'\n\nOnce you've explicitly set the value for `enable_key_visualizer`, you can check\nits value by clicking **SHOW EQUIVALENT DDL** in the overview page, or using the\n`ddl describe` gcloud command: \n\n gcloud spanner databases ddl describe `\u003cvar translate=\"no\"\u003edatabase_id\u003c/var\u003e` --instance=\u003cvar translate=\"no\"\u003e\u003cspan class=\"devsite-syntax-n\"\u003einstance_id\u003c/span\u003e\u003c/var\u003e\n\nRe-enable Key Visualizer\n------------------------\n\nTo re-enable Key Visualizer, follow the previous instructions, setting the\nvalue of the `enable_key_visualizer` database option to `true`.\n\nWhen first re-enabled for a database, the Key Visualizer heatmap will be empty\nfor the first few minutes while Spanner collects metrics.\n\nWhat's next\n-----------\n\n- Learn to recognize [common patterns in heatmaps](/spanner/docs/key-visualizer/patterns).\n- Find out how to [explore a heatmap in depth](/spanner/docs/key-visualizer/exploring-heatmaps).\n- Read about the [metrics you can view in a heatmap](/spanner/docs/key-visualizer/metrics)."]]
