For organisations already managing servers with OpenText Operations Agent, the supported content pack offers a route to deploy an OpenTelemetry Collector without treating rollout as a separate tooling project.
Reuse the environment you already manage
OpenText’s ITOM Marketplace describes the Content Pack as an optional way to deploy the OpenTelemetry Collector on Operations Agent-managed servers. It can be configured through the standard policy mechanism, collect logs from various sources, and export OpenTelemetry data in OTLP format to the Operations Platform (ODL) or other Observability back-ends for insight and event extraction.
That makes the Content Pack worth evaluating when Operations Agent is already deployed: teams may be able to build on existing management practices rather than introduce a wholly separate deployment path.
Version 3.0, dated 15 October 2026, is part of release 26.4 of OpenText AI Operations Management, but it can be used with earlier versions. The no-cost Content Pack is also OpenText Supported.
What are the Changes from Version 2.0
Version 3.0 upgrades the OpenTelemetry Collector (Contrib) from version from 0.132.0 to 0.161.0. There are no policy changes in this release.
Deployment
With the Content Pack, the OpenTelemetry Collector is automatically deployed as a subagent process of the OpenText Operations Agent, so is a convenient deployment method for those thinking about deploying OpenTelemetry but not knowing where to start. It also includes:
- Prebuilt receiver configurations for filelog, JsonFilelog, syslog and Windows EventLog
- Prebuilt exporter configurations for FILE, OTLP/HTTP, OTLP/GRPC and Operations Agent (ODL Integration)
- Customisable policies so that additional processing steps can be added
- Fully parameterised policies for within-Aspect or deployment-time configuration
If you already use OpenTelemetry pipelines manually, then compare the policies against your current configurations to evaluate whether you can use this Content Pack to automate pipeline deployment and maintenance.
Conclusion
For an existing Operations Agent estate, the content pack is a practical candidate to trial. Confirm compatibility and measure the effort in your own environment before standardising on it.
If this Content Pack sounds interesting and you’d like to discuss whether it fits in with your Observability stack, or to discuss your options, get in touch and we can help get you started.