> ## Documentation Index
> Fetch the complete documentation index at: https://docs.chronosphere.io/llms.txt
> Use this file to discover all available pages before exploring further.

# Upgrade the Collector

When you're ready to upgrade the Chronosphere Collector to a new version, determine
your current version before upgrading. You can then upgrade the Collector based on
your installation method.

<Note>
  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.
</Note>

## Determine your current version

Use one of the following methods to determine the current version of your Collector:

* [Check your manifest](#check-your-manifest)
* [Query the `/debug/version` endpoint](#query-the-/debug/version-endpoint)
* [Use Metrics Explorer](#use-metrics-explorer)

### Check your manifest

Open your Collector manifest and locate the `spec.template.spec.containers.env.image`
YAML collection. The string includes `vVERSION`, where `VERSION` is the Collector
version number:

```yaml theme={null}
spec:
...
  template:
    spec:
      containers:
      - env:
        image: gcr.io/chronosphereio/chronocollector:vVERSION
```

*`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](/ingest/metrics-traces/collector/debugging#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:

```json theme={null}
{
  "go_version": "go1.23.4",
  "version": "v0.116.0",
  "branch": "HEAD",
  "revision": "a4c82d1f7",
  "build_date": "2026-05-12-18:42:05",
  "build_time": "1778876525"
}
```

### Use Metrics Explorer

1. In the navigation menu select
   **<Icon icon="compass" /> Explorers <span aria-label="and then">></span> Metrics Explorer**
   to access the Metrics Explorer.

2. Enter the following query in the query field.

   ```text theme={null}
   count(chronocollector_build_information) by (build_version, instance)
   ```

3. Click **<Icon icon="refresh-cw" />Run**.

   The version of each Collector instance displays in the `build_version` column 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.

1. Open your Collector manifest and locate the
   `spec.template.spec.containers.env.image` YAML collection.

2. In the `image` string, modify the version number to the version that you want to
   upgrade to. For example, the following `image` indicates version `0.116.0` of the
   Collector:

   ```yaml theme={null}
   spec:
   ...
     template:
       spec:
         containers:
         - env:
           image: gcr.io/chronosphereio/chronocollector:v0.116.0
   ```

3. Complete a rolling restart of your pods:

   ```shell theme={null}
   kubectl rollout restart daemonset chronocollector -n NAMESPACE
   ```

   Replace *`NAMESPACE`* with your Kubernetes namespace.

4. Re-enable port forwarding for your Collector. The following command enables port
   forwarding on port `3030`:

   ```shell theme={null}
   kubectl port-forward chronocollector-POD_NAME 3030
   ```

### Upgrade a standalone deployment

If you deployed your Collector as a standalone binary, download the latest version
and redeploy the Collector.

Refer to the [Standalone Collector installation](/ingest/metrics-traces/collector/install/standalone)
page for steps on how to download the latest binary and redeploy it.