AIMS Telegraf agent

AIMS connects to the Telegraf open-source server plugins that allow you to get data from your stacks, sensors, and systems

Schedule a demo
  • Why AIMS
  • Telegraf data powered by AI
  • Telegraf Input Plugins

AI-powered monitoring for 300+ plugins

AIMS support all the plugins from the open-source Telegraf agent and applies AI to all the data

Fully automated

AIMS maps, learns and monitors your systems automatically

Artificial Intelligence

Automatically set dynamic thresholds down to the most granular level

Machine learning

The longer AIMS is installed, the more accurate it becomes

Extensive real-time analytics

Engage system owners, LoB owners and CxOs

Monitoring and analytics powered by AI

Predictive anomaly detection

AIMS can predict anomalies within a single system and across systems. Using dynamic alert thresholds, AIMS detects when behavior is heading out of normal ranges and alerts you earlier – so you can take action to prevent downtime.

Quickly up and running

Run a small script on your Telegraf configuration file and AIMS will pick up the configuration and be ready to accept the data.  

Real-time analytics

Drill down into any system, application, component, or performance parameter using AIMS powerful analytics tools. Create health reports, identify the root of performance issues, verify SLA requirements, plan for scaling, and more.

Power of Telegraf

Telegraf has plugins to source a variety of metrics directly from the system it’s running on, pull metrics from third-party APIs, or even listen for metrics via a statsd and Kafka consumer services.

Telegraf input plugins

AMQP Consumer

The AMQP Consumer input plugin provides a consumer for use with AMQP 0-9-1, a prominent implementation of this protocol being RabbitMQ.


The ActiveMQ input plugin gathers queues, topics, and subscriber metrics using the ActiveMQ Console API.


The Aerospike input plugin queries Aerospike servers and gets node statistics and statistics for all configured namespaces.

Amazon Cloudwatch Statistics

The Amazon CloudWatch Statistics input plugin pulls metric statistics from Amazon CloudWatch.

Amazon ECS

Amazon ECS input plugin (AWS Fargate compatible) uses the Amazon ECS v2 metadata and stats API endpoints to gather stats on running containers in a task. The Telegraf container and the workload that Telegraf is inspecting must be run in the same task. This is similar to (and reuses pieces of) the Docker input plugin, with some ECS-specific modifications for AWS metadata and stats formats.

Amazon Kinesis Consumer

The Amazon Kinesis Consumer input plugin reads from a Kinesis data stream and creates metrics using one of the supported formats

Apache Aurora

The Aurora input plugin gathers metrics from Apache Aurora schedulers

Apache HTTP Server

The Apache HTTP Server input plugin collects server performance information using the mod_status module of the Apache HTTP Server.

Typically, the mod_status module is configured to expose a page at the /server-status?auto location of the Apache server. The ExtendedStatus option must be enabled in order to collect all available fields. For information about how to configure your server reference, see the module documentation.

Apache Kafka Consumer

The Apache Kafka Consumer input plugin polls a specified Kafka topic and adds messages to InfluxDB. Messages are expected in the line protocol format. Consumer Group is used to talk to the Kafka cluster so multiple instances of Telegraf can read from the same topic in parallel.

Apache Mesos

The Apache Mesos input plugin gathers metrics from Mesos. For more information, please check the Mesos Observability Metrics page.

Apache Solr

The Apache Solr input plugin collects stats using the MBean Request Handler.

Apache Tomcat

The Apache Tomcat input plugin collects statistics available from the Apache Tomcat manager status page (http://<host>/manager/status/all?XML=true). Using XML=true returns XML data. See the Apache Tomcat documentation for details on these statistics.

Apache Zipkin

The Apache Zipkin input plugin implements the Zipkin HTTP server to gather trace and timing data needed to troubleshoot latency problems in microservice architectures.

Apache Zookeeper

The Apache Zookeeper input plugin collects variables output from the mntr command Zookeeper Admin.


The Apcupsd input plugin reads data from an apcupsd daemon over its NIS network protocol.

Azure Storage Queue

The Azure Storage Queue plugin gathers sizes of Azure Storage Queues.


The Bcache input plugin gets bcache statistics from the stats_total directory and dirty_data file.


The Beanstalkd input plugin collects server stats as well as tube stats (reported by stats and stats-tube commands respectively).

Bind 9 Nameserver Statistics

plugin decodes the JSON or XML statistics provided by BIND 9 nameservers.


The Bond input plugin collects network bond interface status, bond’s slaves interfaces status and failures count of bond’s slaves interfaces.


The Burrow input plugin collects Apache Kafka topic, consumer, and partition status using the Burrow HTTP Endpoint.

Ceph Storage

The Ceph Storage input plugin collects performance metrics from the MON and OSD nodes in a Ceph storage cluster.


The CGroup input plugin captures specific statistics per cgroup.


The Chrony input plugin gets standard chrony metrics, requires chronyc executable.

Cisco GNMI Telemetry

Cisco GNMI Telemetry is an input plugin that consumes telemetry data similar to the GNMI specification. This GRPC-based protocol can utilize TLS for authentication and encryption. This plugin has been developed to support GNMI telemetry as produced by Cisco IOS XR (64-bit) version 6.5.1 and later.

Cisco Model-Driven Telemetry

Cisco model-driven telemetry (MDT) is an input plugin that consumes telemetry data from Cisco IOS XR, IOS XE and NX-OS platforms. It supports TCP & GRPC dialout transports. GRPC-based transport can utilize TLS for authentication and encryption. Telemetry data is expected to be GPB-KV (self-describing-gpb) encoded.


The Conntrack input plugin collects stats from Netfilter’s conntrack-tools.

The conntrack-tools provide a mechanism for tracking various aspects of network connections as they are processed by netfilter. 



The Consul input plugin will collect statistics about all health checks registered in the Consul. It uses Consul API to query the data. It will not report the telemetry but Consul can report those stats already using StatsD protocol, if needed.


The Couchbase input plugin reads per-node and per-bucket metrics from Couchbase.



The CouchDB input plugin gathers metrics of CouchDB using _stats endpoint.



The CPU input plugin gathers metrics about cpu usage.



The Disk input plugin gathers metrics about disk usage by mount point.



The DiskIO input plugin gathers metrics about disk IO by device.



The Disque input plugin gathers metrics from one or more Disque servers.



The DMCache input plugin provides a native collection for dmsetup-based statistics for dm-cache.


DNS Query

The DNS Query input plugin gathers DNS query times in milliseconds - like Dig.



The Docker input plugin uses the Docker Engine API to gather metrics on running Docker containers. The Docker plugin uses the Official Docker Client to gather stats from the Engine API library documentation.


Docker Log

The Docker Log input plugin uses the Docker Engine API to collect logs from running Docker containers. The plugin uses the Official Docker Client to gather logs from the Engine API.



The Dovecot input plugin uses the dovecot Stats protocol to gather metrics on configured domains. For more information, see the Dovecot documentation.



The Elasticsearch input plugin queries endpoints to obtain node and optionally cluster-health or cluster-stats metrics.



The Ethtool plugin gathers ethernet device statistics. The network device and driver determine what fields are gathered.



The Exec input plugin parses supported Telegraf input data formats (line protocol, JSON, Graphite, Value, Nagios, Collectd, and Dropwizard) into metrics. Each Telegraf metric includes the measurement name, tags, fields, and timestamp.



The Fail2ban input plugin gathers the count of failed and banned IP addresses using fail2ban.



The Fibaro input plugin makes HTTP calls to the Fibaro controller API to gather values of hooked devices. Those values could be true (1) or false (0) for switches, percentage for dimmers, temperature, etc.



The File input plugin updates a list of files every interval and parses the contents using the selected input data format.


The Filecount input plugin reports the number and total size of files in directories that match certain criteria.



The Filestat input plugin gathers metrics about file existence, size, and other stats.



The Fireboard input plugin gathers real time temperature data from Fireboard thermometers. To use this input plugin, sign up to use the Fireboard REST API.



The Fluentd input plugin gathers Fluentd server metrics from plugin endpoint provided by in_monitor plugin. This plugin understands data provided by /api/plugin.json resource (/api/config.json is not covered).



Gathers repository information from GitHub-hosted repositories.


Google Cloud PubSub

The Google Cloud PubSub input plugin ingests metrics from Google Cloud PubSub and creates metrics using one of the supported input data formats.


Google Cloud PubSub Push

The Google Cloud PubSub Push (cloud_pubsub_push) input plugin listens for messages sent using HTTP POST requests from Google Cloud PubSub. The plugin expects messages in Google’s Pub/Sub JSON Format ONLY. The intent of the plugin is to allow Telegraf to serve as an endpoint of the Google Pub/Sub ‘Push’ service. Google’s PubSub service will only send over HTTPS/TLS so this plugin must be behind a valid proxy or must be configured to use TLS.



The Graylog input plugin can collect data from remote Graylog service URLs


The HAproxy input plugin gathers metrics directly from any running HAproxy instance. It can do so by using CSV generated by HAproxy status page or from admin sockets.



The Hddtemp input plugin reads data from hddtemp daemons.



The HTTP input plugin collects metrics from one or more HTTP (or HTTPS) endpoints. The endpoint should have metrics formatted in one of the supported input data formats. Each data format has its own unique set of configuration options which can be added to the input configuration.


HTTP Listener v2

The HTTP Listener v2 input plugin listens for messages sent via HTTP POST. Messages are expected in line protocol format ONLY (other Telegraf input data formats are not supported). This plugin allows Telegraf to serve as a proxy or router for the /write endpoint of the InfluxDB v2110 HTTP API.


HTTP Response

The HTTP Response input plugin gathers metrics for HTTP responses. The measurements and fields include response_time, http_response_code, and result_type. Tags for measurements include server and method.


Icinga 2

The Icinga 2 input plugin gather status on running services and hosts using the Icinga 2 API.


InfluxDB v1.x

The InfluxDB v1.x input plugin gathers metrics from the exposed InfluxDB v1.x /debug/vars endpoint.

InfluxDB v2

InfluxDB 2.x exposes its metrics using the Prometheus Exposition Format — there is no InfluxDB v2 input plugin.


InfluxDB Listener

The InfluxDB Listener input plugin listens for requests sent according to the InfluxDB HTTP API. The intent of the plugin is to allow Telegraf to serve as a proxy, or router, for the HTTP /write endpoint of the InfluxDB HTTP API.


The Interrupts input plugin gathers metrics about IRQs, including interrupts (from /proc/interrupts) and soft_interrupts (from /proc/softirqs).


IPMI Sensor

The IPMI Sensor input plugin queries the local machine or remote host sensor statistics using the ipmitool utility.



The Ipset input plugin gathers packets and bytes counters from Linux ipset. It uses the output of the command ipset save. Ipsets created without the counters option are ignored.



The IPtables input plugin gathers packets and bytes counters for rules within a set of table and chain from the Linux iptables firewall.



The IPVS input plugin uses the Linux kernel netlink socket interface to gather metrics about IPVS virtual and real servers.



The Jenkins input plugin gathers information about the nodes and jobs running in a jenkins instance.


Jolokia2 Agent

The Jolokia2 Agent input plugin reads JMX metrics from one or more Jolokia agent REST endpoints using the JSON-over-HTTP protocol.


Jolokia2 Proxy

The Jolokia2 Proxy input plugin reads JMX metrics from one or more targets by interacting with a Jolokia proxy REST endpoint using the Jolokia JSON-over-HTTP protocol.


JTI OpenConfig Telemetry

The JTI OpenConfig Telemetry input plugin reads Juniper Networks implementation of OpenConfig telemetry data from listed sensors using the Junos Telemetry Interface. Refer to for more details about OpenConfig and Junos Telemetry Interface (JTI).



The Kapacitor input plugin will collect metrics from the given Kapacitor instances.



The Kernel input plugin gathers kernel statistics from /proc/stat.


Kernel VMStat

The Kernel VMStat input plugin gathers kernel statistics from /proc/vmstat.



The Kibana input plugin queries the Kibana status API to obtain the health status of Kibana and some useful metrics.



The Kubernetes input plugin talks to the kubelet API using the /stats/summary endpoint to gather metrics about the running pods and containers for a single host. It is assumed that this plugin is running as part of a daemonset within a Kubernetes installation. This means that Telegraf is running on every node within the cluster. Therefore, you should configure this plugin to talk to its locally running kubelet.



Kubernetes Inventory

The Kubernetes Inventory input plugin generates metrics derived from the state of Kubernetes resources



The LeoFS input plugin gathers metrics of LeoGateway, LeoManager, and LeoStorage using SNMP. See System monitoring in the LeoFS documentation for more information.


Linux Sysctl FS

The Linux Sysctl FS input plugin provides Linux system level file (sysctl fs) metrics. The documentation on these fields can be found here.



The Logparser input plugin streams and parses the given log files. Currently, it has the capability of parsing “grok” patterns from log files, which also supports regular expression (regex) patterns.



The Logstash input plugin reads metrics exposed by the Logstash Monitoring API. The plugin supports Logstash 5 and later.



Lustre Jobstats allows for RPCs to be tagged with a value, such as a job’s ID. This allows for per job statistics. The Lustre2 input plugin collects statistics and tags the data with the jobid.



The Mailchimp input plugin gathers metrics from the /3.0/reports MailChimp API.



The MarkLogic input plugin gathers health status metrics from one or more MarkLogic hosts.



The Mcrouter input plugin gathers statistics data from a mcrouter instance. Mcrouter is a memcached protocol router, developed and maintained by Facebook, for scaling memcached ( deployments. It’s a core component of cache infrastructure at Facebook and Instagram where mcrouter handles almost 5 billion requests per second at peak.



The Mem input plugin collects system memory metrics. For a more complete explanation of the difference between used and actual_used RAM, see Linux ate my ram.



The Memcached input plugin gathers statistics data from a Memcached server.


Mesosphere DC/OS

The Mesosphere DC/OS input plugin gathers metrics from a DC/OS cluster’s metrics component.


Microsoft SQL Server

The Microsoft SQL Server input plugin provides metrics for your Microsoft SQL Server instance. It currently works with SQL Server versions 2008+. Recorded metrics are lightweight and use Dynamic Management Views supplied by SQL Server.



The MongoDB input plugin collects MongoDB stats exposed by serverStatus and few more and create a single measurement containing values.


MQTT Consumer

The MQTT Consumer input plugin reads from specified MQTT topics and adds messages to InfluxDB. Messages are in the Telegraf input data formats.



The Multifile input plugin allows Telegraf to combine data from multiple files into a single metric, creating one field or tag per file. This is often useful creating custom metrics from the /sys or /proc filesystems.



The MySQL input plugin gathers the statistics data from MySQL servers.


NATS Consumer

The NATS Consumer input plugin reads from specified NATS subjects and adds messages to InfluxDB. Messages are expected in the Telegraf input data formats. A Queue Group is used when subscribing to subjects so multiple instances of Telegraf can read from a NATS cluster in parallel.


NATS Server Monitoring

The NATS Server Monitoring input plugin gathers metrics when using the NATS Server monitoring server.


Neptune Apex

The Neptune Apex input plugin collects real-time data from the Apex status.xml page. The Neptune Apex controller family allows an aquarium hobbyist to monitor and control their tanks based on various probes. The data is taken directly from the /cgi-bin/status.xml at the interval specified in the telegraf.conf configuration file.



The Net input plugin gathers metrics about network interface usage (Linux only).



The Netstat input plugin gathers TCP metrics such as established, time-wait and sockets counts by using lsof.


Network Response

The Network Response input plugin tests UDP and TCP connection response time. It can also check response text.



The NGINX input plugin reads NGINX basic status information (ngx_http_stub_status_module).



The NGINX VTS input plugin gathers NGINX status using external virtual host traffic status module - This is an NGINX module that provides access to virtual host status information. It contains the current status such as servers, upstreams, caches. This is similar to the live activity monitoring of NGINX Plus. For module configuration details, see the NGINX VTS module documentation.



The NGINX Plus input plugin is for NGINX Plus, the commercial version of the open source web server NGINX. To use this plugin you will need a license.


The NGINX Plus API input plugin gathers advanced status information for NGINX Plus servers.


NGINX Upstream Check

The NGINX Upstream Check input plugin reads the status output of the nginx_upstream_check. This module can periodically check the NGINX upstream servers using the configured request and interval to determine if the server is still available. 


The NSQ input plugin collects metrics from NSQD API endpoints.


NSQ Consumer

The NSQ Consumer input plugin polls a specified NSQD topic and adds messages to InfluxDB. This plugin allows a message to be in any of the supported data_format types.



The Nstat input plugin collects network metrics from /proc/net/netstat, /proc/net/snmp, and /proc/net/snmp6 files.



The NTPq input plugin gets standard NTP query metrics, requires ntpq executable.



The NVIDIA SMI input plugin uses a query on the NVIDIA System Management Interface (nvidia-smi) binary to pull GPU stats including memory and GPU usage, temp and other.



The OpenLDAP input plugin gathers metrics from OpenLDAP’s cn=Monitor backend.



The OpenNTPD input plugin gathers standard Network Time Protocol (NTP) query metrics from OpenNTPD using the ntpctl command.



The OpenSMTPD input plugin gathers stats from OpenSMTPD, a free implementation of the server-side SMTP protocol.



Collect current weather and forecast data from OpenWeatherMap.



The PF input plugin gathers information from the FreeBSD/OpenBSD pf firewall. Currently it can retrive information about the state table: the number of current entries in the table, and counters for the number of searches, inserts, and removals to the table. The pf plugin retrieves this information by invoking the pfstat command.



The PgBouncer input plugin provides metrics for your PgBouncer load balancer. For information about the metrics, see the PgBouncer documentation.


Phfusion Passenger

The Phfusion 0Passenger input plugin gets Phusion Passenger statistics using their command line utility passenger-status.



The PHP-FPM input plugin gets phpfpm statistics using either HTTP status page or fpm socket.



The Ping input plugin measures the round-trip for ping commands, response time, and other packet statistics.



The Postfix input plugin reports metrics on the postfix queues. For each of the active, hold, incoming, maildrop, and deferred queues, it will report the queue length (number of items), size (bytes used by items), and age (age of oldest item in seconds).



The PostgreSQL input plugin provides metrics for your PostgreSQL database. It currently works with PostgreSQL versions 8.1+. It uses data from the built-in pg_stat_database and pg_stat_bgwriter views. The metrics recorded depend on your version of PostgreSQL.


PostgreSQL Extensible

This PostgreSQL Extensible input plugin provides metrics for your Postgres database. It has been designed to parse SQL queries in the plugin section of telegraf.conf files.



The PowerDNS input plugin gathers metrics about PowerDNS using UNIX sockets.


PowerDNS Recursor

The PowerDNS Recursor input plugin gathers metrics about PowerDNS Recursor using UNIX sockets.



The Processes input plugin gathers info about the total number of processes and groups them by status (zombie, sleeping, running, etc.). On Linux, this plugin requires access to procfs (/proc); on other operating systems, it requires access to execute ps.



The Procstat input plugin monitors system resource usage of an individual processes using their /proc data.

Prometheus Format

The Prometheus Format input plugin input plugin gathers metrics from HTTP servers exposing metrics in Prometheus format.


Puppet Agent

The Puppet Agent input plugin collects variables outputted from the last_run_summary.yaml file usually located in /var/lib/puppet/state/ Puppet Agent Runs. For more information, see Puppet Monitoring: How to Monitor the Success or Failure of Puppet Runs



The RabbitMQ input plugin reads metrics from RabbitMQ servers via the Management Plugin.


Raindrops Middleware

The Raindrops Middleware input plugin reads from the specified Raindrops middleware URI and adds the statistics to InfluxDB.



The Redis input plugin gathers the results of the INFO Redis command. There are two separate measurements: redis and redis_keyspace, the latter is used for gathering database-related statistics.


The RethinkDB input plugin works with RethinkDB 2.3.5+ databases that requires username, password authorization, and Handshake protocol v1.0.



The Riak input plugin gathers metrics from one or more Riak instances.



The Salesforce input plugin gathers metrics about the limits in your Salesforce organization and the remaining usage. It fetches its data from the limits endpoint of the Salesforce REST API.



The Sensors input plugin collects collects sensor metrics with the sensors executable from the lm-sensor package.



The SMART input plugin gets metrics using the command line utility smartctl for SMART (Self-Monitoring, Analysis and Reporting Technology) storage devices. SMART is a monitoring system included in computer hard disk drives (HDDs) and solid-state drives (SSDs), which include most modern ATA/SATA, SCSI/SAS and NVMe disks. The plugin detects and reports on various indicators of drive reliability, with the intent of enabling the anticipation of hardware failures. See smartmontools.



The SNMP input plugin gathers metrics from SNMP agents.



The SNMP Trap plugin receives SNMP notifications (traps and inform requests). Notifications are received over UDP on a configurable port. Resolve OIDs to strings using system MIB files (just like with the SNMP input plugin).


Socket Listener

The Socket Listener input plugin listens for messages from streaming (TCP, UNIX) or datagram (UDP, unixgram) protocols. Messages are expected in the Telegraf Input Data Formats.



The Stackdriver input plugin gathers metrics from the Stackdriver Monitoring API.



The StatsD input plugin is a special type of plugin which runs a backgrounded statsd listener service while Telegraf is running. StatsD messages are formatted as described in the original etsy statsd implementation.



The Suricata input plugin reports internal performance counters of the Suricata IDS/IPS engine, such as captured traffic volume, memory usage, uptime, flow counters, and more. It provides a socket for the Suricata log output to write JSON output to and processes the incoming data to fit Telegraf’s format.



The Swap input plugin gathers metrics about swap memory usage. For more information about Linux swap spaces, see All about Linux swap space




The Synproxy plugin gathers synproxy metrics. Synproxy is a Linux netfilter module used for SYN attack mitigation.



The Syslog input plugin listens for syslog messages transmitted over UDP or TCP. Syslog messages should be formatted according to RFC 5424.



The Sysstat input plugin collects sysstat system metrics with the sysstat collector utility sadc and parses the created binary data file with the sadf utility.



The System input plugin gathers general stats on system load, uptime, and number of users logged in. It is basically equivalent to the UNIX uptime command.


Systemd Units

The Systemd Units plugin gathers systemd unit status metrics on Linux. It relies on systemctl list-units --all --type=service to collect data on service status.


The Tail input plugin “tails” a log file and parses each log message.


Teamspeak 3

The Teamspeak 3 input plugin uses the Teamspeak 3 ServerQuery interface of the Teamspeak server to collect statistics of one or more virtual servers.


Telegraf v1.x

The Telegraf v1.x input plugin collects metrics about the Telegraf v1.x agent itself. Note that some metrics are aggregates across all instances of one type of plugin.



The Temp input plugin collects temperature data from sensors.


Tengine Web Server

The Tengine Web Server input plugin gathers status metrics from the Tengine Web Server using the Reqstat module.



The Trig input plugin inserts sine and cosine waves for demonstration purposes.



The Twemproxy input plugin gathers data from Twemproxy instances, processes Twemproxy server statistics, processes pool data, and processes backend server (Redis/Memcached) statistics.



The Unbound input plugin gathers statistics from Unbound, a validating, recursive, and caching DNS resolver.



The uWSGI input plugin gathers metrics about uWSGI using the uWSGI Stats Server.



The Varnish input plugin gathers stats from Varnish HTTP Cache.


VMware vSphere

The VMware vSphere input plugin uses the vSphere API to gather metrics from multiple vCenter servers (clusters, hosts, VMs, and data stores). For more information on the available performance metrics, see Common vSphere Performance Metrics



The Webhooks input plugin starts an HTTPS server and registers multiple webhook listeners.


Windows Performance Counters

The Windows Performance Counters input plugin reads Performance Counters on the Windows operating sytem. Windows only.


Windows Services

The Windows Services input plugin reports Windows services info. Windows only.



The Wireless input plugin gathers metrics about wireless link quality by reading the /proc/net/wireless file. This plugin currently supports Linux only.


X.509 Certificate

The X.509 Certificate input plugin provides information about X.509 certificate accessible using the local file or network connection.



The ZFS input plugin provides metrics from your ZFS filesystems. It supports ZFS on Linux and FreeBSD. It gets ZFS statistics from /proc/spl/kstat/zfs on Linux and from sysctl and zpool on FreeBSD.



Guide to Anomaly Detection in IT Operations

Anomaly Detection is a fundamental requirement to succeed in IT Operations as the IT complexities keep increasing. In this guide, we dive into the key components, variants, fundamental differences between approaches, and end with some notes on what you may consider in your evaluation of Anomaly Detection.