Documentation

Telegraf

  • Telegraf v1.14.0+

Monit Input Plugin

This plugin gathers metrics and status information about local processes, remote hosts, files, file systems, directories and network interfaces managed and watched over by Monit.

The plugin supports Monit version 5.16+. To use this plugin you have to enable the HTTPD TCP port in Monit.

Introduced in: Telegraf v1.14.0 Tags: network OS support: all

Global configuration options

In addition to the plugin-specific configuration settings, plugins support additional global and plugin configuration settings. These settings are used to modify metrics, tags, and field or create aliases and configure ordering, etc. See the CONFIGURATION.md for more details.

Configuration

# Read metrics and status information about processes managed by Monit
[[inputs.monit]]
  ## Monit HTTPD address
  address = "http://127.0.0.1:2812"

  ## Username and Password for Monit
  # username = ""
  # password = ""

  ## Amount of time allowed to complete the HTTP request
  # timeout = "5s"

  ## Optional TLS Config
  # tls_ca = "/etc/telegraf/ca.pem"
  # tls_cert = "/etc/telegraf/cert.pem"
  # tls_key = "/etc/telegraf/key.pem"
  ## Use TLS but skip chain & host verification
  # insecure_skip_verify = false

Metrics

  • monit_filesystem

    • tags:
      • address
      • version
      • service
      • platform_name
      • status
      • monitoring_status
      • monitoring_mode
    • fields:
      • status_code
      • monitoring_status_code
      • monitoring_mode_code
      • mode
      • block_percent
      • block_usage
      • block_total
      • inode_percent
      • inode_usage
      • inode_total

  • monit_directory

    • tags:
      • address
      • version
      • service
      • platform_name
      • status
      • monitoring_status
      • monitoring_mode
    • fields:
      • status_code
      • monitoring_status_code
      • monitoring_mode_code
      • permissions

  • monit_file

    • tags:
      • address
      • version
      • service
      • platform_name
      • status
      • monitoring_status
      • monitoring_mode
    • fields:
      • status_code
      • monitoring_status_code
      • monitoring_mode_code
      • size
      • permissions

  • monit_process

    • tags:
      • address
      • version
      • service
      • platform_name
      • status
      • monitoring_status
      • monitoring_mode
    • fields:
      • status_code
      • monitoring_status_code
      • monitoring_mode_code
      • cpu_percent
      • cpu_percent_total
      • mem_kb
      • mem_kb_total
      • mem_percent
      • mem_percent_total
      • pid
      • parent_pid
      • threads
      • children

  • monit_remote_host

    • tags:
      • address
      • version
      • service
      • platform_name
      • status
      • monitoring_status
      • monitoring_mode
    • fields:
      • status_code
      • monitoring_status_code
      • monitoring_mode_code
      • hostname
      • port_number
      • request
      • response_time
      • protocol
      • type

  • monit_system

    • tags:
      • address
      • version
      • service
      • platform_name
      • status
      • monitoring_status
      • monitoring_mode
    • fields:
      • status_code
      • monitoring_status_code
      • monitoring_mode_code
      • cpu_system
      • cpu_user
      • cpu_wait
      • cpu_load_avg_1m
      • cpu_load_avg_5m
      • cpu_load_avg_15m
      • mem_kb
      • mem_percent
      • swap_kb
      • swap_percent

  • monit_fifo

    • tags:
      • address
      • version
      • service
      • platform_name
      • status
      • monitoring_status
      • monitoring_mode
    • fields:
      • status_code
      • monitoring_status_code
      • monitoring_mode_code
      • permissions

  • monit_program

    • tags:
      • address
      • version
      • service
      • platform_name
      • status
      • monitoring_status
      • monitoring_mode
    • fields:
      • status_code
      • monitoring_status_code
      • monitoring_mode_code

  • monit_network

    • tags:
      • address
      • version
      • service
      • platform_name
      • status
      • monitoring_status
      • monitoring_mode
    • fields:
      • status_code
      • monitoring_status_code
      • monitoring_mode_code

  • monit_program

    • tags:
      • address
      • version
      • service
      • platform_name
      • status
      • monitoring_status
      • monitoring_mode
    • fields:
      • status_code
      • monitoring_status_code
      • monitoring_mode_code

  • monit_network

    • tags:
      • address
      • version
      • service
      • platform_name
      • status
      • monitoring_status
      • monitoring_mode
    • fields:
      • status_code
      • monitoring_status_code
      • monitoring_mode_code

Example Output

monit_file,monitoring_mode=active,monitoring_status=monitored,pending_action=none,platform_name=Linux,service=rsyslog_pid,source=xyzzy.local,status=running,version=5.20.0 mode=644i,monitoring_mode_code=0i,monitoring_status_code=1i,pending_action_code=0i,size=3i,status_code=0i 1579735047000000000
monit_process,monitoring_mode=active,monitoring_status=monitored,pending_action=none,platform_name=Linux,service=rsyslog,source=xyzzy.local,status=running,version=5.20.0 children=0i,cpu_percent=0,cpu_percent_total=0,mem_kb=3148i,mem_kb_total=3148i,mem_percent=0.2,mem_percent_total=0.2,monitoring_mode_code=0i,monitoring_status_code=1i,parent_pid=1i,pending_action_code=0i,pid=318i,status_code=0i,threads=4i 1579735047000000000
monit_program,monitoring_mode=active,monitoring_status=initializing,pending_action=none,platform_name=Linux,service=echo,source=xyzzy.local,status=running,version=5.20.0 monitoring_mode_code=0i,monitoring_status_code=2i,pending_action_code=0i,program_started=0i,program_status=0i,status_code=0i 1579735047000000000
monit_system,monitoring_mode=active,monitoring_status=monitored,pending_action=none,platform_name=Linux,service=debian-stretch-monit.virt,source=xyzzy.local,status=running,version=5.20.0 cpu_load_avg_15m=0,cpu_load_avg_1m=0,cpu_load_avg_5m=0,cpu_system=0,cpu_user=0,cpu_wait=0,mem_kb=42852i,mem_percent=2.1,monitoring_mode_code=0i,monitoring_status_code=1i,pending_action_code=0i,status_code=0i,swap_kb=0,swap_percent=0 1579735047000000000
monit_remote_host,dc=new-12,host=palladium,monitoring_mode=active,monitoring_status=monitored,pending_action=none,platform_name=Linux,rack=rack-0,service=blog.kalvad.com,source=palladium,status=running,version=5.27.0 monitoring_status_code=1i,monitoring_mode_code=0i,response_time=0.664412,type="TCP",pending_action_code=0i,remote_hostname="blog.kalvad.com",port_number=443i,request="/",protocol="HTTP",status_code=0i 1599138990000000000

Was this page helpful?

Thank you for your feedback!

© 2025 InfluxData, Inc.

Where are you running InfluxDB?

Select your InfluxDB Cloud region and cluster or your InfluxDB OSS URL and we’ll customize code examples for you. Identify your InfluxDB Cloud cluster.

  • InfluxDB Cloud
  • InfluxDB OSS or Enterprise
AWS

  • US West (Oregon)

GCP
Azure
Default
Custom

For more information, see InfluxDB Cloud regions or InfluxDB OSS URLs.

Thank you for your feedback!

Let us know what we can do better:

Thank you!

No thanks

New in InfluxDB 3.5

Key enhancements in InfluxDB 3.5 and the InfluxDB 3 Explorer 1.3.

See the Blog Post

InfluxDB 3.5 is now available for both Core and Enterprise, introducing custom plugin repository support, enhanced operational visibility with queryable CLI parameters and manual node management, stronger security controls, and general performance improvements.

InfluxDB 3 Explorer 1.3 brings powerful new capabilities including Dashboards (beta) for saving and organizing your favorite queries, and cache querying for instant access to Last Value and Distinct Value caches—making Explorer a more comprehensive workspace for time series monitoring and analysis.

For more information, check out:

InfluxDB Docker latest tag changing to InfluxDB 3 Core

On November 3, 2025, the latest tag for InfluxDB Docker images will point to InfluxDB 3 Core. To avoid unexpected upgrades, use specific version tags in your Docker deployments.

If using Docker to install and run InfluxDB, the latest tag will point to InfluxDB 3 Core. To avoid unexpected upgrades, use specific version tags in your Docker deployments. For example, if using Docker to run InfluxDB v2, replace the latest version tag with a specific version tag in your Docker pull command–for example:

docker pull influxdb:2