Chronosphere supports Collector versions for one year from their release dates. Use
only a supported version, unless explicitly instructed otherwise by Chronosphere
Support. If you experience issues, upgrade to the latest supported version.
Determine your current version
To determine the current version of your Collector, you can:Check your manifest
Open your Collector manifest and locate thespec.template.spec.containers.env.image
YAML collection. The string includes vVERSION, where VERSION is the Collector
version number:
VERSION is the current version number of the Collector.
Query the /debug/version endpoint
The Collector exposes a /debug/version endpoint that you can query to return the
Collector version. To learn about the supported methods for accessing debug endpoints,
see Access the debug endpoints.
The query response returns a JSON representation of the Collector version information,
which is the same information the Collector prints when starting. For example:
Use Metrics Explorer
- In the navigation menu select Explorers > Metrics Explorer to access the Metrics Explorer.
-
Enter the following query in the query field.
-
Click Run.
The version of each Collector instance displays in the
build_versioncolumn of the query results table. For example:Time build_version instance 2025-10-10 11:07:15 v0_116_0 test-env/chronocollector-test3-2z8dx 2025-10-10 11:07:15 v0_115_0 test-env/chronocollector-test3-4vcd9
Upgrade to a new version
After determining your current version, you’re ready to upgrade your Collector. Your installation method determines how you upgrade the Collector.Upgrade a Kubernetes deployment
If you deployed your Collector as a Kubernetes DaemonSet or Deployment, complete the following steps to upgrade your Collector.-
Open your Collector manifest and locate the
spec.template.spec.containers.env.imageYAML collection. -
In the
imagestring, modify the version number to the version that you want to upgrade to. For example, the followingimageindicates version0.116.0of the Collector: -
Complete a rolling restart of your pods:
Replace
NAMESPACEwith your Kubernetes namespace. -
Re-enable port forwarding for your Collector. The following command enables port
forwarding on port
3030:

