All Projects → monitoring-plugins → Monitoring Plugins

monitoring-plugins / Monitoring Plugins

Licence: gpl-3.0
Monitoring Plugins

Programming Languages

c
50402 projects - #5 most used programming language

Projects that are alternatives of or similar to Monitoring Plugins

Dockbix Xxl
🐳 Dockerized Zabbix - server, web, proxy, java gateway, snmpd with additional extensions
Stars: ✭ 374 (-10.95%)
Mutual labels:  monitoring
Cortex
A horizontally scalable, highly available, multi-tenant, long term Prometheus.
Stars: ✭ 4,491 (+969.29%)
Mutual labels:  monitoring
Yabeda
Extendable framework for collecting and exporting metrics from your Ruby application
Stars: ✭ 402 (-4.29%)
Mutual labels:  monitoring
Dogvscat
Sample Docker Swarm cluster stack of tools
Stars: ✭ 377 (-10.24%)
Mutual labels:  monitoring
Vizceral
WebGL visualization for displaying animated traffic graphs
Stars: ✭ 3,871 (+821.67%)
Mutual labels:  monitoring
Tautulli
A Python based monitoring and tracking tool for Plex Media Server.
Stars: ✭ 4,152 (+888.57%)
Mutual labels:  monitoring
Bgpalerter
Software to monitor streams of BGP data. Pre-configured for real-time detection of visibility loss, RPKI invalid announcements, hijacks, and more.
Stars: ✭ 367 (-12.62%)
Mutual labels:  monitoring
Zabbix Slack Alertscript
Zabbix AlertScript for Slack.com chat
Stars: ✭ 406 (-3.33%)
Mutual labels:  monitoring
Statuspage
A statuspage generator that lets you host your statuspage for free on Github.
Stars: ✭ 3,852 (+817.14%)
Mutual labels:  monitoring
Devops Readme.md
What to Read to Learn More About DevOps
Stars: ✭ 398 (-5.24%)
Mutual labels:  monitoring
Glances
Glances an Eye on your system. A top/htop alternative for GNU/Linux, BSD, Mac OS and Windows operating systems.
Stars: ✭ 19,648 (+4578.1%)
Mutual labels:  monitoring
Prometheus For Developers
Practical introduction to Prometheus for developers.
Stars: ✭ 382 (-9.05%)
Mutual labels:  monitoring
Dockprom
Docker hosts and containers monitoring with Prometheus, Grafana, cAdvisor, NodeExporter and AlertManager
Stars: ✭ 4,489 (+968.81%)
Mutual labels:  monitoring
Microsoft365dsc
Manages, configures, extracts and monitors Microsoft 365 tenant configurations
Stars: ✭ 374 (-10.95%)
Mutual labels:  monitoring
Alertmanager
Prometheus Alertmanager
Stars: ✭ 4,574 (+989.05%)
Mutual labels:  monitoring
Laravel Activitylog
Log activity inside your Laravel app
Stars: ✭ 4,123 (+881.67%)
Mutual labels:  monitoring
Guider
Performance Analyzer
Stars: ✭ 393 (-6.43%)
Mutual labels:  monitoring
Unms
Installation Scripts for Ubiquiti Network Management System
Stars: ✭ 410 (-2.38%)
Mutual labels:  monitoring
Nodejs Dashboard
Telemetry dashboard for node.js apps from the terminal!
Stars: ✭ 3,937 (+837.38%)
Mutual labels:  monitoring
Ceph Dash
Flask based api / dashboard for viewing a ceph clusters overall health status
Stars: ✭ 398 (-5.24%)
Mutual labels:  monitoring

Monitoring Plugins

  • For instructions on installing these plugins for use with your monitoring system, see below. In addition, generic instructions for the GNU toolchain can be found in the INSTALL file.

  • For major changes between releases, read the NEWS file.

  • For information on detailed changes that have been made or plugins that have been added, read the ChangeLog file.

  • Some plugins require that you have additional programs or libraries installed on your system before they can be used. Plugins that are dependent on other programs/libraries that are missing are usually not compiled. Read the REQUIREMENTS file for more information.

  • Individual plugins are self-documenting. All plugins that comply with the basic guidelines for development will provide detailed help when invoked with the -h or --help options.

You can check the latest plugins at:

Send an email to [email protected] for assistance. Please include the OS type and version that you are using. Also, run the plugin with the -vvv option and provide the resulting version information. Of course, there may be additional diagnostic information required as well. Use good judgment.

Send an email to [email protected] for developer discussions.

For patch submissions and bug reports, please use the appropriate resources at:

Installation Instructions

  1. If you are using the Git tree, you will need m4, gettext, automake, and autoconf. To start out, run:

    ./tools/setup
    

    For more detail, see the developer guidelines at https://www.monitoring-plugins.org/doc/guidelines.html.

  2. Run the configure script to initialize variables and create a Makefile, etc.

    ./configure --prefix=BASEDIRECTORY --with-cgiurl=SOMEURL
    

    Replace BASEDIRECTORY with the path of the directory under which your monitoring system is installed (default is /usr/local), and replace SOMEURL with the path used to access the monitoring system CGIs with a web browser (default is /nagios/cgi-bin).

  3. Compile the plugins with the following command:

    make
    
  4. Install the compiled plugins and plugin scripts with the following command:

    make install
    

    The installation procedure will attempt to place the plugins in a libexec/ subdirectory in the base directory you specified with the --prefix argument to the configure script.

  5. There are some plugins that require setuid. If you run make install as a non-root user, they will not be installed. To install, switch to root and run:

    make install-root
    

That's it! If you have any problems or questions, feel free to send an email to [email protected].

License Notice

You can redistribute and/or modify this software under the terms of the GNU General Public License as published by the Free Software Foundation; either version 3 of the License, or (at your option) any later version; with the additional exemption that compiling, linking, and/or using OpenSSL is allowed.

This software is distributed in the hope that it will be useful, but WITHOUT ANY WARRANTY; without even the implied warranty of MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.

See the COPYING file for the complete text of the GNU General Public License, version 3.

Note that the project description data, including the texts, logos, images, and/or trademarks, for each open source project belongs to its rightful owner. If you wish to add or remove any projects, please contact us at [email protected].