Overview
OpenTelemetry Collector service running
otelcol-contrib --version reporting the pinned 0.154.0 release and systemctl status showing the otelcol-contrib.service daemon active and running the sample pipeline.
OpenTelemetry Collector service running
Health endpoint and OTLP listeners
Sample pipeline and data volume
This is a repackaged open source software product wherein additional charges apply for cloudimg support services.
Overview The OpenTelemetry Collector is the vendor-neutral, CNCF-graduated way to receive, process and export telemetry. It ingests traces, metrics and logs through pluggable receivers, transforms and batches them through processors, then exports them to dozens of observability backends. This image delivers the feature-rich contrib distribution fully installed and running as a system service with a working sample pipeline, so a telemetry pipeline appliance is processing data within minutes of launch.
Telemetry Pipeline Service The collector daemon installed from the official release package and run by the bundled systemd service, started on boot and restarted on failure. A self-contained sample pipeline ships ready to run, receiving OTLP and scraping host metrics into a file exporter and the journal, so you can confirm the pipeline is flushing telemetry the moment you log in. Replace the sample receivers and exporters with your own to start collecting and routing your real traces, metrics and logs.
OTLP Receivers Ready The OpenTelemetry Protocol receivers are configured and listening on the standard gRPC and HTTP ports, bound to loopback by default. Point your instrumented applications and SDKs at the collector, or rebind the receivers to a network interface and open the ports in the security group to accept telemetry from across your fleet. The health-check and zPages extensions are enabled so you can confirm the collector is serving and inspect its live pipeline.
Configurable Pipeline The collector reads its pipeline from a single declarative configuration file. Define receivers to ingest OTLP, Prometheus, host metrics, the journal, syslog and more; chain processors to batch, filter, transform, sample and enrich; and fan out to exporters for your backend: OTLP, Prometheus, Loki, Kafka, file and many others through the contrib distribution. A dedicated data disk holds the exported telemetry off the operating system disk.
Ready To Use Connect over SSH and the pipeline is already running. Read the welcome notes, edit the configuration file, point your receivers at your sources and your exporters at your destinations, then reload the service. The file exporter output lives on a dedicated, independently resizable data disk.
cloudimg Support 24/7 technical support by email and chat. Help with pipeline design, receiver and exporter configuration, processors and sampling, OTLP and Prometheus ingest, routing to your observability backend, scaling the collector and upgrade planning.
Use Cases A telemetry gateway aggregating traces, metrics and logs from your fleet before they leave your network. A sidecar or node agent receiving OTLP from instrumented applications. A protocol translator converting between OTLP, Prometheus and your backend's native format. A vendor-neutral collection layer that decouples your instrumentation from your observability backend.
All product and company names are trademarks or registered trademarks of their respective holders. Use of them does not imply any affiliation with or endorsement by them.
Highlights
- The OpenTelemetry Collector contrib distribution, the vendor-neutral CNCF telemetry pipeline, preinstalled and running as a systemd service with a working sample pipeline, no manual setup required
- OTLP gRPC and HTTP receivers plus a host-metrics receiver are wired through a batch processor to file and debug exporters, with the health-check and zPages extensions enabled and a dedicated, independently resizable data disk holding the exported telemetry
- Edit a single declarative configuration file to receive, process and route traces, metrics and logs to your observability backend, with 24/7 technical support from cloudimg
Details
Introducing multi-product solutions
You can now purchase comprehensive solutions tailored to use cases and industries.
Features and programs
Financing for AWS Marketplace purchases
Pricing
Free trial
- ...
Dimension | Description | Cost/hour |
|---|---|---|
t3.small Recommended | t3.small | $0.04 |
t2.micro | t2.micro instance type | $0.04 |
t3.micro | t3.micro instance type | $0.04 |
c5a.12xlarge | c5a.12xlarge instance type | $0.24 |
c5a.16xlarge | c5a.16xlarge instance type | $0.24 |
c5a.24xlarge | c5a.24xlarge instance type | $0.24 |
c5a.2xlarge | c5a.2xlarge instance type | $0.24 |
c5a.4xlarge | c5a.4xlarge instance type | $0.24 |
c5a.8xlarge | c5a.8xlarge instance type | $0.24 |
c5a.large | c5a.large instance type | $0.08 |
Vendor refund policy
Refunds available on request.
How can we make this page better?
Legal
Vendor terms and conditions
Content disclaimer
Delivery details
64-bit (x86) Amazon Machine Image (AMI)
Amazon Machine Image (AMI)
An AMI is a virtual image that provides the information required to launch an instance. Amazon EC2 (Elastic Compute Cloud) instances are virtual servers on which you can run your applications and workloads, offering varying combinations of CPU, memory, storage, and networking resources. You can launch as many instances from as many different AMIs as you need.
Version release notes
Initial release of the OpenTelemetry Collector 0.154.0 contrib distribution as a ready-to-use telemetry pipeline service with OTLP receivers and the health-check extension enabled.
Additional details
Usage instructions
Connect via SSH on port 22 as the default login user for your operating system variant (the user guide lists it per variant). This is a headless telemetry-pipeline service: there is no web interface. Read the welcome notes with: sudo cat /root/otel-collector-info.txt. Confirm the daemon is running with: systemctl status otelcol-contrib. The pipeline configuration lives at /etc/otelcol-contrib/config.yaml (edit it, then run sudo systemctl restart otelcol-contrib). The OTLP receivers listen on 127.0.0.1:4317 (gRPC) and 127.0.0.1:4318 (HTTP); the health-check extension answers on 127.0.0.1:13133 (curl http://127.0.0.1:13133 ) and zPages on 127.0.0.1:55679. The file exporter writes exported telemetry to a dedicated data disk mounted at /var/lib/otelcol. To accept telemetry from across your network, rebind the receivers in config.yaml to a network interface and open the OTLP ports in the instance security group.
Resources
Vendor resources
Support
Vendor support
cloudimg provides 24/7 technical support for this product by email and live chat. Our engineers help with deployment, configuration, updates, performance tuning and troubleshooting; critical issues receive a one hour average response. Contact support@cloudimg.co.uk .
AWS infrastructure support
AWS Support is a one-on-one, fast-response support channel that is staffed 24x7x365 with experienced and technical support engineers. The service helps customers of all sizes and technical abilities to successfully utilize the products and features provided by Amazon Web Services.
Similar products
