[[["이해하기 쉬움","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-07-10(UTC)"],[],[],null,["# Legacy installation scripts for the Cloud Monitoring agent\n\n| **Note:** There will be no new feature development or support for new operating systems for the legacy Monitoring agent. We recommend that you use the [Ops Agent](/monitoring/agent/ops-agent) for new workloads and eventually transition your existing VMs to use the Ops Agent. We strongly recommend against using the Monitoring agent on Windows.\n\nThe legacy installation scripts, `stack-install.sh` and\n`install-monitoring-agent.sh`, are deprecated and have been\ndecommissioned.\n\n- `stack-install.sh` is not supported and cannot be used to install any version of the Cloud Monitoring agent.\n- `install-monitoring-agent.sh` is no longer available and cannot be used to install any version of the Cloud Monitoring agent.\n\nYou must migrate to the new installation script as soon as\npossible. For more information, refer to [Installing the Cloud Monitoring\nagent](/monitoring/agent/monitoring/installation).\n\nAfter migrating to the new script, you can temporarily pin to agent version\n5.x.x to gauge the impact of the breaking changes in version 6.0.0 and later.\n\nShutdown timetable\n------------------\n\nThe following table lists the shutdown schedule for the legacy installation\nscripts for the Cloud Monitoring agent:"]]
