[[["わかりやすい","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-04 UTC。"],[],[],null,["# Cloud Logging and Monitoring agents deprecation policy\n\nThis document details the deprecation policy for the following\nLogging and Monitoring agents and related\nclient-side components:\n\n- [Ops Agent](/stackdriver/docs/solutions/agents/ops-agent)\n- [Legacy Cloud Logging agent](/logging/docs/agent)\n- [Legacy Cloud Monitoring agent](/monitoring/agent)\n- [Stackdriver Metadata agent](https://github.com/Stackdriver/metadata-agent/blob/master/README.md)\n- [Heapster](https://github.com/Stackdriver/heapster/blob/master/README.md) (for GKE version 1.15 and below)\n- [Cloud Monitoring-Prometheus integration](/monitoring/kubernetes-engine/prometheus)\n\nDeprecating a release version\n-----------------------------\n\n### Release version support\n\nAll agents and their client-side components follow\nthe \\\u003cMAJOR\\\u003e.\\\u003cMINOR\\\u003e.\\\u003cPATCH\\\u003e versioning convention. For example,\n**stackdriver-agent 5.5.2**. A new release increments:\n\n- The **MAJOR** version when making backwards-incompatible changes,\n- The **MINOR** version when adding functionality in a backwards-compatible manner,\n- The **PATCH** version when making backwards-compatible bug fixes.\n\nSupporting a version of the agent means that bugs in the agents are debugged and\nfixed on each of the supported platforms. Customers may need to upgrade their\nagent to the latest minor release of the same major version to take advantage of\nany bug fixes. However, they are not required to upgrade to a later major\nversion of the agent, which may contain backward incompatible changes.\n\nIf a security issue or critical bug found in one of the supported major versions\nalso exists in other supported major versions, the bug fix is backported to all\nsupported major versions unless the fix is not backwards compatible.\nNew features will not be backported.\n\nBackwards-compatible changes, including new features or bug fixes, go to minor\nreleases of the most recent major version at any time. Backwards-incompatible\nchanges are incorporated into the next major release.\n\n### Decommission\n\nThe lifespan of any major version of a Cloud Logging or Cloud Monitoring agent is at\nleast 12 months. A major version (e.g., version N) is decommissioned 12 months\nafter the release of the next major version (e.g., version N+1). Decommissioning\na major version means that it doesn't receive any further bug fixes or minor\nreleases. It also means that customer support is no longer available for that\nversion. Once a version is decommissioned, the agent's installer files for that\nversion are removed and not available to download.\n\nSubsequent agent releases where only the minor version is updated don't reset\nthe clock. The lifespan of any minor version follows its major version's\ndeprecation and decommission schedule.\n\nYou will not receive a Mandatory Service Announcement (MSA) for each release.\nInstead, you can find the **planned decommission date** on the agent README\npages.\n\nWhen an environment, for example, Amazon Elastic Compute Cloud (EC2), or an\noperating system reaches its end of life, agent support is deprecated as well.\nThe actual decommission happens when support for the environment or operating\nsystem ends, unless a specific decommission date has already been set for an\nagent. Refer to the\n[Deprecating support for environments, operating systems, and features](#env)\nsection of this guide for more information.\n\n### Transition plan for existing agents and components\n\nVersions of the agents and client-side components that existed before this\ndeprecation policy will be available and supported at least until\nFebruary 28, 2020. However, bug fixes will not be backported for these releases.\n\n#### Click the **+** sign to see which versions of the agents\nand components are affected by the transition plan\n\n\n\u003cbr /\u003e\n\nTo see the decommission dates for other versions of the agents and components,\nrefer to the README page for each component.\n\nDeprecating support for environments, operating systems, and features\n---------------------------------------------------------------------\n\n### Environments and operating systems support\n\nLogging and Monitoring agents are binaries that\nare installed in client\nenvironments. Each agent supports different environment and operating system\ncombinations. An example combination is Amazon Linux on EC2.\n\n### Feature support\n\nA feature refers to a unit of functionality of the agents that satisfies a\nrequirement, represents a design decision, and/or provides a potential\nconfiguration option. An example feature would be support for ingesting metrics\nfor a monitored resource.\n\n### Deprecation\n\nWhen support for an environment, operating system, or feature is deprecated, you\nwill receive an MSA to announce the deprecation, including a link to this\ndeprecation policy. The MSA is bound to the major version of the agent and\ncomponent release.\nThe decommission date for the environment, operating system, or feature is the\nsame as the decommission date for that major version of the agent release. That\nmajor version is the last major version that supports the environment, operating\nsystem, or feature.\n\n### Decommission\n\nWhen support for an environment, operating system, or feature is\ndecommissioned, customer support is no longer provided for that environment,\noperating system, or feature. An MSA will be sent out to announce the\ndecommissioning."]]