EOL.Wiki EOL.Wiki
← ← Back to all products

OpenTelemetry Collector

Active
Tools & Monitoring Latest Version: 0.154.0 Latest Release: Jun 8, 2026

The OpenTelemetry Collector is a vendor-agnostic agent for receiving, processing, and exporting telemetry data.

Versions

6

Latest Version

0.154.0

Active Support

1

EOL

5

Lifecycle Timeline

Today
0.154
0.154
0.153
0.153
0.140
0.140
0.130
0.130
0.120
0.120
0.110
0.110
Active SupportSecurity SupportEOL

Versions

ReleaseRelease DateActive SupportEOLLatest VersionLTSStatus
0.154Jun 8, 2026YesNo0.154.0No
Active
0.153May 25, 2026NoYes0.153.0No
EOL
0.140Nov 17, 2025NoYes0.140.0No
EOL
0.130Jul 14, 2025NoYes0.130.0No
EOL
0.120Feb 18, 2025NoYes0.120.0No
EOL
0.110Sep 23, 2024NoYes0.110.0No
EOL

Frequently Asked Questions

Which versions of OpenTelemetry Collector have reached end of life?
The following OpenTelemetry Collector versions have reached end of life and no longer receive security updates: 0.153, 0.140, 0.130, 0.120, 0.110. It is recommended to upgrade to a supported version.
Is it safe to continue using OpenTelemetry Collector 0.153?
OpenTelemetry Collector 0.153 has reached end of life and no longer receives security patches or bug fixes. Continuing to use it may expose your systems to known vulnerabilities. We strongly recommend upgrading to a supported version.
What is the latest version of OpenTelemetry Collector?
The latest version of OpenTelemetry Collector is 0.154.0, released in the 0.154 release cycle.
How many versions of OpenTelemetry Collector are currently supported?
OpenTelemetry Collector currently has 1 actively supported version(s): 0.154.
When does OpenTelemetry Collector 0.154 reach end of life?
OpenTelemetry Collector 0.154 does not have a specific end-of-life date announced yet.
What should I do when OpenTelemetry Collector reaches end of life?
When a OpenTelemetry Collector version reaches end of life, you should: 1) Plan your migration to a supported version as soon as possible. 2) Review the release notes for breaking changes. 3) Test your applications thoroughly in a staging environment. 4) Update your dependencies to ensure compatibility with the new version.