Monit is an open source utility for managing and monitoring Unix systems. You can use Monit to monitor daemon processes or other programs running on localhost, such as those started at system boot time from /etc/init/ like sendmail, sshd, apache and mysql.

Why use the Monit Telegraf Plugin?

When it comes to monitoring the performance of your website or application, you need to collect all kinds of metrics for you to review over time to determine whether things are going well or not. One of the ways you can do this is by using the open source utility called Monit. Monit can monitor background or daemon processes. Even better, Monit can automatically start a process if it does not run, restart a process if it doesn’t respond and even suspend a process if it uses too much resources. This powerful combination goes beyond just monitoring by autonomously executing an action determined by you as a reaction to specified events — essentially automatically fixing the potential issue.

The Monit Telegraf Plugin collects metrics and status information about local processes, remote hosts, file, file systems, directories and network interfaces managed and watched over by Monit. All of these metrics can be collected and stored in InfluxDB along with other metrics that may complement it, like those collected with Ping, SNMP, and a whole set of other system metrics.

How to use the Monit Telegraf Plugin

Once you have installed the Monit Telegraf Plugin, you should enable it to use the HTTPD TCP port in Monit. In addition, you will need to configure for credentials (username & password), timeouts for the HTTP requests, and an optional TLS config, and then have it start sending the Monit metrics to your InfluxDB instance.

Key Monit metrics to use for monitoring

Some of the important Monit metrics that you can use to proactively monitor include:

  • 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

For more information, please check out the documentation.

Project URL   Documentation

Related Resources

Monitoring Network Interface Template

Monitoring network interface performance is important in identifying the root cause of performance degradation and network bottlenecks.

Cisco Model-Driven Telemetry Telegraf Plugin

The Cisco Model-Driven Telemetry Telegraf Plugin consumes telemetry data from various Cisco platforms.

Arista LANZ Consumer Telegraf Plugin

The Arista LANZ Consumer Telegraf Plugin is a consumer for use with Arista Networks’ Latency Analyzer (LANZ) to stream data into InfluxDB.

Scroll to Top