GET https://recommender.googleapis.com/v1beta1/projects/PROJECT-ID/locations/LOCATION/recommenders/google.cloudsql.instance.RECOMMENDER/recommendations
다음을 바꿉니다.
PROJECT_ID: 프로젝트 ID입니다.
LOCATION: 리전(예: us-central1)
RECOMMENDER: IdleRecommender로서 추천자 ID
추천자는 감지한 유휴 인스턴스를 테이블에 나열합니다. 행마다 인스턴스 이름, 간단한 추천, 위치, 마지막 새로고침 날짜가 표시됩니다.
통계 및 자세한 권장사항 보기
Google Cloud 콘솔, gcloud 또는 Recommender API를 사용하여 유휴 인스턴스에 대한 통계와 자세한 추천을 볼 수 있습니다.
콘솔
Google Cloud 콘솔을 사용하여 유휴 인스턴스에 대한 통계를 보려면 인스턴스 목록에서 추천 버튼을 클릭합니다.
GET https://recommender.googleapis.com/v1beta1/projects/PROJECT-ID/locations/LOCATION/insightTypes/google.cloudsql.instance.INSIGHT_TYPE/insights
다음을 바꿉니다.
PROJECT_ID: 프로젝트 ID입니다.
LOCATION: 리전(예: us-central1)
INSIGHT_TYPE: ActivityInsight로서의 통계 유형 ID
유휴 인스턴스에 대한 통계를 보여주는 패널이 나타납니다. 다음 정보 카테고리는 일부 지원 차트와 함께 제공됩니다.
필드
설명 및 관련 측정항목
디스크 사용량(바이트 변동)
바이트 단위의 데이터 사용률입니다. 60초마다 샘플링됩니다. database/disk/bytes_used에 적합합니다.
최대 CPU 사용률
백분율로 표시되는 최대 CPU 사용률입니다. database/cpu/utilization에 적합합니다.
최대 메모리 사용률
백분율로 표시되는 최대 메모리 사용률입니다. database/memory/utilization에 적합합니다.
최대 디스크 읽기 작업 수
읽기 작업의 최대 개수입니다. database/disk/read_ops_count에 적합합니다.
최대 디스크 쓰기 작업 수
최대 쓰기 작업 수입니다. database/disk/write_ops_count에 적합합니다.
관찰 시작일 및 종료일
30일 관찰 기간의 시작일 및 종료일입니다.
다음 표에는 Cloud SQL 유휴 인스턴스 추천자가 비용 감소를 위해 생성할 수 있는 통계 및 권장사항이 나열되어 있습니다. 하위 유형은 gcloud 및 API 결과에 표시됩니다.
Insight
권장사항
인스턴스가 관찰 기간 동안 낮은 수준의 활동을 보여주었습니다.
하위 유형: LOW_ACTIVITY
비용 감소를 위해 인스턴스를 종료할 수 있는지 여부를 조사합니다.
하위 유형: SHUTDOWN_INSTANCE
권장사항 적용
통계 및 권장사항을 신중하게 평가하고 다음을 수행합니다.
권장사항을 검토하려면 인스턴스 보기를 클릭하세요.
페이지 상단에 권장사항이 제공된 배너가 나타납니다.
인스턴스가 의도적으로 유휴 상태에 있고 이를 종료할 필요가 없는 경우가 있을 수 있습니다. 그러나 인스턴스가 의도치 않게 유휴 상태에 있는 경우에는 이를 중지하고 삭제할 수 있습니다. 인스턴스를 중지하면 인스턴스 요금 청구가 정지됩니다. 인스턴스 데이터는 영향을 받지 않으며 스토리지 및 IP 주소에 대한 요금은 계속 적용됩니다.
인스턴스를 중지 또는 삭제할 때 주의하세요. 데이터 손실을 방지하려면 먼저 백업을 만드세요.
[[["이해하기 쉬움","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-08-13(UTC)"],[],[],null,["# Identify idle Cloud SQL instances\n\n\u003cbr /\u003e\n\n[MySQL](/sql/docs/mysql/recommender-sql-idle \"View this page for the MySQL database engine\") \\| PostgreSQL \\| [SQL Server](/sql/docs/sqlserver/recommender-sql-idle \"View this page for the SQL Server database engine\")\n\n\u003cbr /\u003e\n\nThe Cloud SQL idle instance [recommender](/recommender/docs/overview) helps\nyou detect instances that might be idle and provides you\ninsights and recommendations to help you reduce costs. This page describes how\nthis recommender works and how to use it.\n\nHow it works\n------------\n\nThe Cloud SQL idle instance recommender analyzes the usage metrics of primary\ninstances that are older than 30 days. For each instance, the recommender\nconsiders the values of certain [metrics](/monitoring/api/metrics_gcp_c#gcp-cloudsql)\nwithin an observation period spanning the last 30 days. The recommender does not\nanalyze read replicas.\n\nIf the activity level within the observation period is below a certain\nthreshold, the recommender estimates that the instance is idle. Recommendations are\ngenerated every 24 hours for shutting down such instances.\n| **Warning:** It's highly recommended that you evaluate the insights and in-context charts. Consult with the appropriate team to determine whether the flagged instance is inadvertently idle and can be deleted.\n\nPricing\n-------\n\nThe Cloud SQL idle instance recommender is in the *Standard* [Recommender pricing tier](/recommender/pricing).\n\nBefore you begin\n----------------\n\nBefore you can view recommendations and insights, do the following:\n\n- To get the permissions to view and work with insights and recommendations, ensure that you have the required [roles](/sql/docs/postgres/project-access-control#roles).\n\n For more information about roles, see [understanding roles](/iam/docs/understanding-roles) and [granting IAM permissions](/iam/docs/granting-changing-revoking-access).\n-\n\n\n Enable the Recommender API.\n\n\n [Enable the API](https://console.cloud.google.com/flows/enableapi?apiid=recommender.googleapis.com)\n\nList idle Cloud SQL instance recommendations\n--------------------------------------------\n\nYou can list idle instance recommendations by\nusing the Google Cloud console, `gcloud`, or the Recommender API. \n\n### Console\n\nTo list recommendations about idle instances by using the\nGoogle Cloud console, follow these steps:\n\n1. Go to the **Cloud SQL Instances** page.\n\n [Go to Cloud SQL Instances](https://console.cloud.google.com/sql/instances)\n2. Click **View all** on the idle instance recommendations banner.\n\nAlternatively, follow these steps:\n\n1. Go to the **Recommendation Hub**.\n\n [Go to the Recommendation Hub](https://console.cloud.google.com/home/recommendations/)\n\n For more information, see\n [Getting started with Recommendation Hub](/recommender/docs/recommendation-hub/identify-configuration-problems).\n2. In the **Reduce Cloud SQL instance cost** card, click **View all**.\n\n3. Click the **Shut down instance** tab.\n\n### gcloud\n\nTo list recommendations about idle instances by using `gcloud`, run the\n[`gcloud recommender recommendations list`](/sdk/gcloud/reference/recommender/recommendations/list)\ncommand as follows: \n\n```\ngcloud recommender recommendations list \\\n--project=PROJECT_ID \\\n--location=LOCATION \\\n--recommender=google.cloudsql.instance.RECOMMENDER\n```\n\nReplace the following:\n\n- \u003cvar translate=\"no\"\u003ePROJECT_ID\u003c/var\u003e: Your project ID.\n- \u003cvar translate=\"no\"\u003eLOCATION\u003c/var\u003e: A region, such as `us-central1`.\n- \u003cvar translate=\"no\"\u003eRECOMMENDER\u003c/var\u003e: The ID of the recommender as `IdleRecommender`.\n\n### API\n\nTo list recommendations about idle instances by using the\n[Recommendations API](/recommender/docs/using-api), call the\n[`recommendations.list`](/recommender/docs/reference/rest/v1beta1/projects.locations.recommenders.recommendations/list)\nmethod as follows. \n\n```\nGET https://recommender.googleapis.com/v1beta1/projects/PROJECT-ID/locations/LOCATION/recommenders/google.cloudsql.instance.RECOMMENDER/recommendations\n```\n\nReplace the following:\n\n- \u003cvar translate=\"no\"\u003ePROJECT_ID\u003c/var\u003e: Your project ID.\n- \u003cvar translate=\"no\"\u003eLOCATION\u003c/var\u003e: A region, such as `us-central1`.\n- \u003cvar translate=\"no\"\u003eRECOMMENDER\u003c/var\u003e: The ID of the recommender as `IdleRecommender`.\n\nIf the recommender detects idle instances, it lists them in a\ntable. Each row shows the instance name, a brief recommendation, the location,\nand the last refresh date.\n\nView insights and detailed recommendations\n------------------------------------------\n\nYou can view insights and detailed recommendations about idle instances by\nusing the Google Cloud console, `gcloud`, or the Recommender API. \n\n### Console\n\nTo view insights about an idle instance by using the\nGoogle Cloud console, click the recommendation button in the list of instances.\n\n### gcloud\n\nTo view insights and detailed recommendations about idle instances by using `gcloud`, run the\n[`gcloud recommender insights list`](/sdk/gcloud/reference/recommender/insights/list)\ncommand as follows: \n\n```\ngcloud recommender insights list \\\n--project=PROJECT_ID \\\n--location=LOCATION \\\n--insight-type=google.cloudsql.instance.INSIGHT_TYPE\n```\n\nReplace the following:\n\n- \u003cvar translate=\"no\"\u003ePROJECT_ID\u003c/var\u003e: Your project ID.\n- \u003cvar translate=\"no\"\u003eLOCATION\u003c/var\u003e: A region, such as `us-central1`.\n- \u003cvar translate=\"no\"\u003eINSIGHT_TYPE\u003c/var\u003e: The ID of the insight type as `ActivityInsight`.\n\n### API\n\nTo view insights and detailed recommendations about idle instances by using the\n[Recommendations API](/recommender/docs/using-api), call the\n[`insights.list`](/recommender/docs/reference/rest/v1beta1/projects.locations.insightTypes.insights/list)\nmethod as follows: \n\n```\nGET https://recommender.googleapis.com/v1beta1/projects/PROJECT-ID/locations/LOCATION/insightTypes/google.cloudsql.instance.INSIGHT_TYPE/insights\n```\n\nReplace the following:\n\n- \u003cvar translate=\"no\"\u003ePROJECT_ID\u003c/var\u003e: Your project ID.\n- \u003cvar translate=\"no\"\u003eLOCATION\u003c/var\u003e: A region, such as `us-central1`.\n- \u003cvar translate=\"no\"\u003eINSIGHT_TYPE\u003c/var\u003e: The ID of the insight type as `ActivityInsight`.\n\nA panel appears showing insights about the idle instance. The following\ncategories of information are provided along with some supporting charts.\n\nThe following table lists the insight and recommendation that the Cloud SQL\nidle instance recommender might generate to help you reduce costs. The subtypes\nare visible in the `gcloud` and API results.\n\nApply recommendations\n---------------------\n\nEvaluate the recommendations carefully and do any of the following:\n\n- To examine the recommendation, click **View instance**.\n\n A banner appears at the top of the page providing a recommendation.\n\n You might find that the instance is intentionally idle and you don't need to shut\n it down. If it's inadvertently idle, you can [stop](/sql/docs/postgres/start-stop-restart-instance#stop)\n and [delete](/sql/docs/postgres/delete-instance) the instance. Stopping an\n instance suspends instance charges. The instance data is unaffected,\n and charges for storage and IP addresses continue to apply.\n\n Exercise caution when [stopping](/sql/docs/postgres/start-stop-restart-instance#stop)\n or [deleting](/sql/docs/postgres/delete-instance) an instance. To avoid\n the loss of data, [create a backup](/sql/docs/postgres/backup-recovery/backing-up#on-demand) first.\n- To dismiss the recommendation so that it's de-emphasized and appears dimmed,\n click **Dismiss**.\n\n- To close the panel without applying or dismissing the recommendation, click\n **Cancel**.\n\nYou can also [export these recommendations to BigQuery](/recommender/docs/bq-export/export-recommendations-to-bq)\nand examine them by using [Looker Studio](/bigquery/docs/visualize-looker-studio) or [Looker](/bigquery/docs/looker).\n\nWhat's next\n-----------\n\n- [Monitor disk availability](/sql/docs/postgres/using-ood-recommender)\n- [Reduce overprovisioned Cloud SQL instances](/sql/docs/postgres/recommender-sql-overprovisioned)\n- [Blog: Maximize your Cloud ROI](https://cloud.google.com/blog/products/management-tools/active-assist-comes-to-google-cloud)\n- [Blog: Do more with less](https://cloud.google.com/blog/products/databases/reduce-cloud-sql-costs-with-optimizations-by-active-assist)\n- [Google Cloud recommenders](/recommender/docs/recommenders)"]]
