Docs » Get started with the Splunk Distribution of the OpenTelemetry Collector » Get started with the Collector for Windows » Upgrade the Collector for Windows

Upgrade the Collector for Windows πŸ”—

The installer script uses one of the supported package managers to install the Collector, for example apt or yum.

When you update the Collector using the official packages, configuration files are never overridden. If you need to update the configuration after an update, edit them manually before backward compatibility is dropped.

General guidelines πŸ”—

Apply the following changes to the Collector configuration files for specific version upgrades.

From 0.96.1 to 0.97.0 πŸ”—

memory_ballast is no longer effective. You can now control garbage collection with a soft memory limit using the SPLUNK_MEMORY_TOTAL_MIB env var, which is set to 90% of the total memory by default. For more information, see Environment variables.

Follow these steps to ensure your Collector instances work correctly:

  • If you haven’t customized memory_ballast, remove it from the configuration.

  • If you have customized memory_ballast using SPLUNK_BALLAST_SIZE_MIB (or extensions::memory_ballast::size_mib config), remove the memory_ballast extension and use the GOMEMLIMIT environment variable to set a custom soft memory limit:

    • To increase frequency of garbage collection set GOMEMLIMIT to a higher value than the default 90% of total memory.

    • To decrease frequency of garbage collection set GOMEMLIMIT to a lower value than the default 90% of total memory.

    • For more information, see Go environment variables .

From 0.68.0 to 0.69.0 πŸ”—

The gke and gce resource detectors in the resourcedetection processor have been replaced with the gcp resource detector. If you have gke and gce detectors configured in the resourcedetection processor, update your configuration accordingly.

For more information, see Resource detection processor.

From 0.41.0 to 0.42.0 πŸ”—

The Splunk Distribution of the OpenTelemetry Collector used to evaluate user configuration twice and this required escaping of each $ symbol with $$ to prevent unwanted environment variable expansion. The issue was fixed in the 0.42.0 version. Any occurrences of $$ in your configuration need to be replaced with $.

From 0.35.0 to 0.36.0 πŸ”—

Move the config parameter exporters -> otlp -> insecure to exporters -> otlp -> tls -> insecure.

The otlp exporter configuration must look like this:

    endpoint: "${SPLUNK_GATEWAY_URL}:4317"
      insecure: true

From 0.34.0 to 0.35.0 πŸ”—

Move the ballast_size_mib parameter from the memory_limiter processor to the memory_ballast extension, and rename it to size_mib.

    size_mib: ${SPLUNK_BALLAST_SIZE_MIB}

Upgrade the Collector for Windows πŸ”—

If you used the Windows installer script, to upgrade you can manually download and run the MSI for the desired Collector version from GitHub .

Chocolatey πŸ”—

If you’re using Chocolatey, in order to keep parameters when upgrading, before installation you need to activate the following feature:

choco feature enable -n=useRememberedArgumentsForUpgrades

To upgrade, run the following command in PowerShell:

choco upgrade splunk-otel-collector

This page was last updated on Apr 23, 2024.