Overview
Telegraf service running
telegraf --version reporting the pinned 1.39.0 release and systemctl status showing the telegraf.service daemon active and running the sample pipeline.
Telegraf service running
Built-in Prometheus metrics endpoint
Sample pipeline and data volume
This is a repackaged open source software product wherein additional charges apply for cloudimg support services.
Overview Telegraf is an open source, plugin-driven server agent for collecting and reporting metrics, events and logs. With hundreds of input plugins it gathers telemetry from the host, containers, databases, message queues, cloud services and any StatsD, SNMP, Prometheus or HTTP source, processes and aggregates it, then writes it to dozens of output destinations including InfluxDB, Prometheus, Graphite, Kafka, CloudWatch, OpenTSDB and any HTTP endpoint. This image delivers Telegraf fully installed and running as a system service with a working sample pipeline, so a metrics-collection appliance is reporting telemetry within minutes of launch.
Metrics Agent Service The telegraf daemon installed from the official InfluxData package repository and run by the bundled systemd service, started on boot and restarted on failure. A self-contained sample pipeline ships ready to run, collecting host CPU, memory, disk and system metrics into a Prometheus output and a file output, so you can confirm the agent is producing metrics the moment you log in. Replace the sample inputs and outputs with your own to start collecting and shipping your real telemetry.
Built-in Prometheus Endpoint The built-in Prometheus client output is enabled and bound to loopback, so a standard Prometheus exposition endpoint answers on the instance with the live host metrics. Scrape it from your Prometheus server, wire it into a health check, or expose it on your own terms. No web interface to secure: the metrics endpoint is read-only and stays private by default.
Configurable Pipeline Telegraf reads its pipeline from a simple TOML configuration file and a drop-in directory. Enable input plugins to collect host, container, database, queue, cloud and protocol metrics; chain processor and aggregator plugins to transform, enrich and roll up the stream; and fan out to multiple output plugins in parallel. A vast plugin ecosystem ships in the single static binary, so most sources and destinations need only a configuration block, no extra installs.
Ready To Use Connect over SSH and the agent is already running. Read the welcome notes, edit the configuration file or drop a snippet into the configuration directory, point the inputs at your sources and the outputs at your destinations, then reload the service. The sample file output lives on a dedicated, independently resizable data disk.
cloudimg Support 24/7 technical support by email and chat. Help with input and output plugin configuration, processors and aggregators, tagging and filtering, metric buffering, routing to your observability backend and upgrade planning.
Use Cases A host and infrastructure metrics agent shipping telemetry to your time-series database. A metrics collector scraping databases, message queues and cloud services. A protocol bridge translating StatsD, SNMP or Prometheus into your observability backend. A lightweight, single-binary agent for cloud-native and edge monitoring.
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
- Telegraf, the MIT-licensed open source plugin-driven server agent for collecting and reporting metrics, preinstalled and running as a systemd service with a working sample pipeline, no manual setup required
- The built-in Prometheus client output is enabled on loopback serving a standard exposition endpoint of live host metrics, and a sample file output on a dedicated, independently resizable data disk persists the metric stream
- Enable plugins in a simple TOML configuration to collect metrics, events and logs from hundreds of sources and route them to dozens of destinations, 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 Telegraf 1.39.0, the open source plugin-driven metrics agent, as a ready-to-use collection service with the built-in Prometheus client output 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 metrics-agent service: there is no web interface. Read the welcome notes with: sudo cat /root/telegraf-info.txt. Confirm the daemon is running with: systemctl status telegraf. The pipeline configuration lives at /etc/telegraf/telegraf.conf with drop-in snippets under /etc/telegraf/telegraf.d/ (edit, then run sudo systemctl restart telegraf). The built-in Prometheus client output is bound to loopback on port 9273: curl http://127.0.0.1:9273/metrics