├── .gitmodules ├── Monitorix └── README.md ├── README.md ├── adagios └── README.md ├── altd └── README ├── bigbrother └── README.md ├── boomerang └── README.md ├── boundary └── README.md ├── byteman └── README.md ├── cacti └── README.md ├── cavalieri └── README.md ├── cepmon └── README.md ├── check_mk └── README.md ├── circonus └── README.md ├── clockwork └── README.md ├── cloudkick-plugins └── README.md ├── collectd-graphite └── README.md ├── collectd └── README.md ├── consul └── README.md ├── critical └── README.md ├── cube └── README.md ├── cucumber-nagios └── README.md ├── darshan └── README ├── datadog └── README.md ├── dataloop.io └── README.md ├── deadman-check └── README.md ├── disqus-nagios-plugins └── README.md ├── epicnms └── README.md ├── esper └── README.md ├── etsy-nagios_tools └── README.md ├── extopus └── README.md ├── extrahop └── README.md ├── extrememon └── README.md ├── fitb └── README.md ├── flapjack └── README.md ├── folsom └── README.md ├── ganglia └── README.md ├── glances └── README.md ├── graph-explorer └── README.md ├── graphite └── README.md ├── graphiteworker └── README.md ├── graylog2 └── README.md ├── groundwork └── README.md ├── hobbit └── README.md ├── hyperic └── README.md ├── influxdb └── README.md ├── ipm └── README ├── isotope11_traffic_lights └── README.md ├── javasimon └── README.md ├── jimi-robot └── README.md ├── jmxtrans └── README.md ├── jolokia └── README.md ├── jwatchdog └── README.md ├── kairosdb └── README.md ├── kibana └── README.md ├── librato └── README.md ├── librenms └── README.md ├── lmt └── README ├── lnav └── README.md ├── logstash └── README.md ├── logster └── README.md ├── metis └── README.md ├── metrics └── README.md ├── mms-10gen └── README.md ├── mod-log-firstbyte └── README.md ├── molog └── README.md ├── moncli └── README.md ├── munin └── README.md ├── nagios-api └── README.md ├── nagios-dashboard └── README.md ├── nagios └── README.md ├── naglite2 └── README.md ├── nervous └── README.md ├── netdata └── README.md ├── netdb └── README.md ├── netdot └── README.md ├── ntopng └── README.md ├── oculus └── README.md ├── okconfig └── README.md ├── opennms └── README.md ├── opentsdb └── README.md ├── opserver └── README.md ├── overwatch └── README.md ├── pandora-fms └── README.md ├── parfait └── README.md ├── pencil └── README.md ├── plumbr └── README.md ├── plumd └── README.md ├── porkchop └── README.md ├── rackspace-cloud-monitoring └── README.md ├── reconnoiter └── README.md ├── redis-cluster-monitor └── README.md ├── remote_syslog └── README.md ├── resmon └── README.md ├── response └── README.md ├── restlos └── README.md ├── riemann └── README.md ├── rivermuse └── README.md ├── rocksteady └── README.md ├── sensu └── README.md ├── servo └── readme.md ├── seyren └── README.md ├── shinken └── README.md ├── skyline └── README.md ├── spm └── README.md ├── stajistics └── README.md ├── statsd └── README.md ├── storm └── README.md ├── sysdig └── README.md ├── tacc_stats └── README ├── tfsoa └── README.md ├── vacuumetrix └── README.md ├── visage └── README.md ├── vowpal_wabbit └── README.md ├── xdmod └── README ├── xymon └── README.md ├── zabbix └── README.md └── zenoss └── README.md /.gitmodules: -------------------------------------------------------------------------------- 1 | [submodule "critical/repo"] 2 | path = critical/repo 3 | url = https://github.com/danielsdeleo/critical.git 4 | [submodule "nagios-dashboard/repo"] 5 | path = nagios-dashboard/repo 6 | url = https://github.com/portertech/nagios-dashboard.git 7 | [submodule "collectd-graphite/repo"] 8 | path = collectd-graphite/repo 9 | url = https://github.com/joemiller/collectd-graphite.git 10 | [submodule "statsd/repo"] 11 | path = statsd/repo 12 | url = https://github.com/etsy/statsd.git 13 | [submodule "flapjack/repo"] 14 | path = flapjack/repo 15 | url = https://github.com/auxesis/flapjack.git 16 | [submodule "clockwork/repo"] 17 | path = clockwork/repo 18 | url = https://github.com/adamwiggins/clockwork 19 | [submodule "overwatch/repo"] 20 | path = overwatch/repo 21 | url = https://github.com/danryan/overwatch 22 | [submodule "pencil/repo"] 23 | path = pencil/repo 24 | url = https://github.com/fetep/pencil 25 | [submodule "graphite/rpms"] 26 | path = graphite/rpms 27 | url = https://github.com/dcarley/graphite-rpms 28 | [submodule "reconnoiter/repo"] 29 | path = reconnoiter/repo 30 | url = https://github.com/omniti-labs/reconnoiter 31 | [submodule "logster/repo"] 32 | path = logster/repo 33 | url = https://github.com/etsy/logster 34 | [submodule "boomerang/repo"] 35 | path = boomerang/repo 36 | url = https://github.com/yahoo/boomerang/ 37 | [submodule "naglite2/repo"] 38 | path = naglite2/repo 39 | url = https://github.com/lozzd/Naglite2 40 | [submodule "folsom/src"] 41 | path = folsom/src 42 | url = git://github.com/boundary/folsom.git 43 | [submodule "metrics/src"] 44 | path = metrics/src 45 | url = git://github.com/codahale/metrics.git 46 | [submodule "cucumber-nagios/repo"] 47 | path = cucumber-nagios/repo 48 | url = git://github.com/auxesis/cucumber-nagios.git 49 | [submodule "etsy-nagios_tools/repo"] 50 | path = etsy-nagios_tools/repo 51 | url = https://github.com/etsy/nagios_tools.git 52 | [submodule "remote_syslog/repo"] 53 | path = remote_syslog/repo 54 | url = https://github.com/papertrail/remote_syslog 55 | [submodule "logstash/repo"] 56 | path = logstash/repo 57 | url = https://github.com/logstash/logstash 58 | [submodule "fitb/repo"] 59 | path = fitb/repo 60 | url = git://github.com/lozzd/FITB.git 61 | [submodule "porkchop/repo"] 62 | path = porkchop/repo 63 | url = https://github.com/disqus/porkchop 64 | [submodule "disqus-nagios-plugins/repo"] 65 | path = disqus-nagios-plugins/repo 66 | url = https://github.com/disqus/nagios-plugins 67 | [submodule "nagios-api/repo"] 68 | path = nagios-api/repo 69 | url = https://github.com/xb95/nagios-api 70 | [submodule "extopus/repo"] 71 | path = extopus/repo 72 | url = https://github.com/oetiker/extopus 73 | [submodule "molog/repo"] 74 | path = molog/repo 75 | url = https://github.com/smetj/molog 76 | [submodule "graylog2/repo"] 77 | path = graylog2/repo 78 | url = https://github.com/Graylog2/graylog2-server 79 | [submodule "cloudkick-plugins/repo"] 80 | path = cloudkick-plugins/repo 81 | url = https://github.com/cloudkick/agent-plugins 82 | [submodule "collectd/repo"] 83 | path = collectd/repo 84 | url = https://github.com/octo/collectd.git 85 | [submodule "moncli/repo"] 86 | path = moncli/repo 87 | url = https://github.com/smetj/moncli.git 88 | [submodule "extrememon/extrememon"] 89 | path = extrememon/extrememon 90 | url = https://github.com/m4rienf/ExtreMon 91 | [submodule "extrememon/extrememon-Display"] 92 | path = extrememon/extrememon-Display 93 | url = https://github.com/m4rienf/ExtreMon-Display 94 | [submodule "riemann/repo"] 95 | path = riemann/repo 96 | url = https://github.com/aphyr/riemann 97 | [submodule "metis/repo"] 98 | path = metis/repo 99 | url = https://github.com/krobertson/metis 100 | [submodule "redis-cluster-monitor/repo"] 101 | path = redis-cluster-monitor/repo 102 | url = https://github.com/zealot2007/redis-cluster-monitor 103 | [submodule "isotope11_traffic_lights/repo"] 104 | path = isotope11_traffic_lights/repo 105 | url = https://github.com/johndavid400/Isotope11_traffic_lights.git 106 | [submodule "datadog/dd-agent"] 107 | path = datadog/dd-agent 108 | url = git://github.com/DataDog/dd-agent.git 109 | [submodule "datadog/dogapi"] 110 | path = datadog/dogapi 111 | url = git://github.com/DataDog/dogapi.git 112 | [submodule "servo/repo"] 113 | path = servo/repo 114 | url = https://github.com/Netflix/servo.git 115 | [submodule "cepmon/repo"] 116 | path = cepmon/repo 117 | url = https://github.com/fetep/cepmon.git 118 | [submodule "nervous/repo"] 119 | path = nervous/repo 120 | url = https://github.com/gflarity/nervous.git 121 | [submodule "response/repo"] 122 | path = response/repo 123 | url = https://github.com/gflarity/response 124 | [submodule "cube/repo"] 125 | path = cube/repo 126 | url = https://github.com/square/cube 127 | [submodule "datadog/dogapi-rb"] 128 | path = datadog/dogapi-rb 129 | url = https://github.com/DataDog/dogapi-rb.git 130 | [submodule "datadog/dogstatsd-python"] 131 | path = datadog/dogstatsd-python 132 | url = https://github.com/DataDog/dogstatsd-python.git 133 | [submodule "datadog/puppet-datadog-agent"] 134 | path = datadog/puppet-datadog-agent 135 | url = https://github.com/DataDog/puppet-datadog-agent.git 136 | [submodule "datadog/chef-handler-datadog"] 137 | path = datadog/chef-handler-datadog 138 | url = https://github.com/DataDog/chef-handler-datadog.git 139 | [submodule "datadog/dogstatsd-ruby"] 140 | path = datadog/dogstatsd-ruby 141 | url = https://github.com/DataDog/dogstatd-ruby.git 142 | [submodule "vacuumetrix/repo"] 143 | path = vacuumetrix/repo 144 | url = https://github.com/99designs/vacuumetrix 145 | [submodule "vowpal_wabbit/repo"] 146 | path = vowpal_wabbit/repo 147 | url = https://github.com/JohnLangford/vowpal_wabbit 148 | [submodule "storm/repo"] 149 | path = storm/repo 150 | url = https://github.com/nathanmarz/storm 151 | [submodule "jimi-robot/repo"] 152 | path = jimi-robot/repo 153 | url = https://github.com/arozhkov/jimi-robot 154 | [submodule "adagios/repo"] 155 | path = adagios/repo 156 | url = https://github.com/opinkerfi/adagios 157 | [submodule "pynag/repo"] 158 | path = pynag/repo 159 | url = https://github.com/pynag/pynag 160 | [submodule "okconfig/repo"] 161 | path = okconfig/repo 162 | url = https://github.com/opinkerfi/okconfig 163 | [submodule "graph-explorer/repo"] 164 | path = graph-explorer/repo 165 | url = https://github.com/vimeo/graph-explorer.git 166 | [submodule "seyren/repo"] 167 | path = seyren/repo 168 | url = https://github.com/scobal/seyren.git 169 | [submodule "influxdb/repo"] 170 | path = influxdb/repo 171 | url = https://github.com/influxdb/influxdb 172 | [submodule "librato/python-librato"] 173 | path = librato/python-librato 174 | url = https://github.com/librato/python-librato 175 | [submodule "librato/librato-services"] 176 | path = librato/librato-services 177 | url = https://github.com/librato/librato-services 178 | [submodule "librato/librato-annotate"] 179 | path = librato/librato-annotate 180 | url = https://github.com/librato/librato-annotate 181 | [submodule "librato/statsd-cookbook"] 182 | path = librato/statsd-cookbook 183 | url = https://github.com/librato/statsd-cookbook 184 | [submodule "librato/papertrail-cookbook"] 185 | path = librato/papertrail-cookbook 186 | url = https://github.com/librato/papertrail-cookbook 187 | [submodule "librato/dropwizard-librato"] 188 | path = librato/dropwizard-librato 189 | url = https://github.com/librato/dropwizard-librato 190 | [submodule "librato/metrics-librato"] 191 | path = librato/metrics-librato 192 | url = https://github.com/librato/metrics-librato 193 | [submodule "librato/statsd-librato-backend"] 194 | path = librato/statsd-librato-backend 195 | url = https://github.com/librato/statsd-librato-backend 196 | [submodule "librato/librato-metrics"] 197 | path = librato/librato-metrics 198 | url = https://github.com/librato/librato-metrics 199 | [submodule "librato/librato-java"] 200 | path = librato/librato-java 201 | url = https://github.com/librato/librato-java 202 | [submodule "librato/librato-rails"] 203 | path = librato/librato-rails 204 | url = https://github.com/librato/librato-rails 205 | [submodule "librato/librato-rack"] 206 | path = librato/librato-rack 207 | url = https://github.com/librato/librato-rack 208 | [submodule "librato/librato-storm-kafka"] 209 | path = librato/librato-storm-kafka 210 | url = https://github.com/librato/librato-storm-kafka 211 | [submodule "librato/librato-logreporter"] 212 | path = librato/librato-logreporter 213 | url = https://github.com/librato/librato-logreporter 214 | [submodule "Monitorix/repo"] 215 | path = Monitorix/repo 216 | url = https://github.com/mikaku/Monitorix 217 | [submodule "cavalieri/repo"] 218 | path = cavalieri/repo 219 | url = https://github.com/juruen/cavalieri 220 | [submodule "opserver/repo"] 221 | path = opserver/repo 222 | url = https://github.com/opserver/Opserver 223 | [submodule "librenms/repo"] 224 | path = librenms/repo 225 | url = https://github.com/librenms/librenms.git 226 | [submodule "lnav/repo"] 227 | path = lnav/repo 228 | url = https://github.com/tstack/lnav 229 | [submodule "sysdig/repo"] 230 | path = sysdig/repo 231 | url = https://github.com/draios/sysdig 232 | [submodule "skyline/repo"] 233 | path = skyline/repo 234 | url = https://github.com/etsy/skyline 235 | [submodule "oculus/repo"] 236 | path = oculus/repo 237 | url = https://github.com/etsy/oculus 238 | [submodule "consul/repo"] 239 | path = consul/repo 240 | url = https://github.com/hashicorp/consul 241 | [submodule "glances/repo"] 242 | path = glances/repo 243 | url = https://github.com/nicolargo/glances 244 | [submodule "restlos/repo"] 245 | path = restlos/repo 246 | url = https://github.com/Crapworks/RESTlos 247 | [submodule "graphiteworker/repo"] 248 | path = graphiteworker/repo 249 | url = https://github.com/Crapworks/graphiteworker.git 250 | [submodule "plumd/repo"] 251 | path = plumd/repo 252 | url = https://github.com/s4z/plumd 253 | [submodule "netdata/repo"] 254 | path = netdata/repo 255 | url = https://github.com/firehol/netdata 256 | [submodule "deadman-check/repo"] 257 | path = deadman-check/repo 258 | url = https://github.com/sepulworld/deadman-check 259 | [submodule "tfsoa/repo"] 260 | path = tfsoa/repo 261 | url = https://github.com/sepulworld/tfsoa 262 | -------------------------------------------------------------------------------- /Monitorix/README.md: -------------------------------------------------------------------------------- 1 | Monitorix is a free, open source, lightweight system monitoring tool designed to monitor as many services and system resources as possible. It has been created to be used under production Linux/UNIX servers, but due to its simplicity and small size can be used on embedded devices as well. 2 | 3 | [http://www.monitorix.org/](http://www.monitorix.org/) 4 | -------------------------------------------------------------------------------- /README.md: -------------------------------------------------------------------------------- 1 | # Tool Repo 2 | =========== 3 | This repository serves as a sort of master repository of various tools that people have come across. 4 | 5 | The format for structure should be as follows: 6 | 7 | top-level repo - 8 | project_name - 9 | README.md (review/information) 10 | git submodule to repo (if appropriate) 11 | 12 | Please do not put any actual code in here. 13 | 14 | 15 | ## Example 16 | 17 | Adding a repo: 18 | 19 | mkdir project_name 20 | git submodule add https://github.com/username/project_name project_name/repo 21 | echo "[link](http://github.com/username/project_name)" > project_name/README.md 22 | git add project_name 23 | git commit -am 'added project_name' 24 | -------------------------------------------------------------------------------- /adagios/README.md: -------------------------------------------------------------------------------- 1 | About 2 | ===== 3 | Adagios is a web based Nagios configuration interface built to be simple and intuitive in design, exposing less of the clutter under the hood of nagios. Additionally adagios has a rest interface for both status and configuration data as well a feature complete status interface that can be used as an alternative to nagios web interface. 4 | 5 | Project website is at http://adagios.org 6 | 7 | Live Demo 8 | ========= 9 | http://demo.adagios.org/ 10 | 11 | Features 12 | ======== 13 | - Full view/edit of hosts,services, etc 14 | - Tons of pre-bundled plugins and configuration templates 15 | - Network scan 16 | - Remote installation of linux/windows agents 17 | - Modern Status view as an alternative to default nagios web interface 18 | - Rest interface for status of hosts/services 19 | - Rest interface for viewing and modifying configuration 20 | - Full audit of any changes made 21 | 22 | Design principals 23 | ================== 24 | - Useful for both novices and nagios experts 25 | - No database backend 26 | - Make common operational tasks as easy as possible 27 | - Assist Nagios admins in keeping configuration files clean and simple 28 | 29 | Components 30 | ========== 31 | - Pynag - Nagios Configuration Parser 32 | - OKconfig - A robust plugin collection with preconfigured nagios template configuration files 33 | - PNP4Nagios - For Graphing Performance data 34 | - MK Livestatus - Broker module for nagios for high performance status information 35 | 36 | Source Code 37 | =========== 38 | 39 | git clone http://github.com/opinkerfi/adagios.git 40 | 41 | Install Instructions 42 | ==================== 43 | These installation instructions apply for rhel6. If running Fedora, please modify yum repos as needed. 44 | 45 | For RHEL6/CentOS6 you must install epel yum repository (fedora users skip this step): 46 | 47 | rpm -Uvh http://download.fedoraproject.org/pub/epel/6/$HOSTTYPE/epel-release-6-8.noarch.rpm 48 | 49 | Next step is to install OK yum repository: 50 | 51 | rpm -Uhv http://opensource.is/repo/ok-release-10-1.el6.noarch.rpm 52 | 53 | Install needed packages: 54 | 55 | yum --enablerepo=ok-testing install -y nagios git adagios 56 | 57 | Install okconfig (optional). Okconfig is a collection of plugins and templates for monitoring enterprise equipment. If installed Adagios will have options such as network scan and remote installation of clients. 58 | 59 | yum --enablerepo=ok-testing install -y okconfig 60 | 61 | Adagios will not work unless you turn off selinux: 62 | 63 | sed -i "s/SELINUX=enforcing/SELINUX=permissive/" /etc/sysconfig/selinux 64 | setenforce 0 65 | 66 | If you plan to access adagios through apache, make sure it is started: 67 | 68 | service httpd restart 69 | chkconfig httpd on 70 | 71 | 72 | Same goes for nagios, start it if it is ready 73 | 74 | service nagios restart 75 | chkconfig nagios on 76 | 77 | 78 | It is strongly recommended that you create a git repository in /etc/nagios/ and additionally give ownership of 79 | everything in /etc/nagios to the nagios user. 80 | 81 | cd /etc/nagios/ 82 | git init 83 | git add . 84 | git commit -a -m "Initial commit" 85 | # Make sure nagios group will always have write access to the configuration files: 86 | chown -R nagios /etc/nagios/* /etc/nagios/.git 87 | setfacl -R -m group:nagios:rwx /etc/nagios/ 88 | setfacl -R -m d:group:nagios:rwx /etc/nagios/ 89 | 90 | 91 | By default objects created by adagios will go to /etc/nagios/adagios so make sure that this directory exists and 92 | nagios.cfg contains a reference to this directory. 93 | 94 | mkdir -p /etc/nagios/adagios 95 | pynag config --append cfg_dir=/etc/nagios/adagios 96 | 97 | Congratulations! You are now ready to browse through adagios through http://$servername/adagios/. By default it 98 | will use same authentication mechanism as nagios. (on rhel default is nagiosadmin/nagiosadmin and can be 99 | changed in /etc/nagios/passwd) 100 | 101 | Using the Status view 102 | ===================== 103 | Adagios has an experimental status view intended to partially replace the classical nagios web interface. If you want to try it out hen you need mk_livestatus and pnp4nagios broker modules installed: 104 | 105 | yum install -y pnp4nagios mk-livestatus --enablerepo=ok-testing 106 | pynag config --append "broker_module=/usr/lib64/nagios/brokers/npcdmod.o config_file=/etc/pnp4nagios/npcd.cfg" 107 | pynag config --append "broker_module=/usr/lib64/mk-livestatus/livestatus.o /var/spool/nagios/cmd/livestatus" 108 | pynag config --set "process_performance_data=1" 109 | 110 | # Add nagios to apache group so it has permissions to pnp4nagios's session files 111 | usermod -G apache nagios 112 | 113 | # We need to restart both apache and nagios so new changes take effect 114 | service nagios restart 115 | service httpd restart 116 | service npcd restart 117 | chkconfig npcd on 118 | 119 | Contact us 120 | =================== 121 | If you need any help with getting adagios to work, feel free to open up an issue on github issue tracker. If you want to chat you can contact us on: 122 | 123 | - Bug reports, feature requests: https://github.com/opinkerfi/adagios/issues 124 | - Mailing list: http://groups.google.com/group/adagios 125 | - IRC: #adagios on irc.freenode.net 126 | -------------------------------------------------------------------------------- /altd/README: -------------------------------------------------------------------------------- 1 | http://www.nersc.gov/users/software/programming-libraries/altd/ 2 | -------------------------------------------------------------------------------- /bigbrother/README.md: -------------------------------------------------------------------------------- 1 | 2 | There isn't anything out there that is more oldschool than Big Brother 3 | 4 | The blinking green , red and orange lights are in the mind of every senior unix person. 5 | 6 | 7 | http://bb4.com/ 8 | 9 | -------------------------------------------------------------------------------- /boomerang/README.md: -------------------------------------------------------------------------------- 1 | End user oriented web performance testing and beaconing 2 | -------------------------------------------------------------------------------- /boundary/README.md: -------------------------------------------------------------------------------- 1 | [product page](https://boundary.com/) 2 | 3 | [github team page](https://github.com/boundary) 4 | 5 | Boundary is a network-monitoring as a service platform providing 1s status updates and real time aggregation of bandwith by port and IP. 6 | 7 | Currently in private beta. 8 | -------------------------------------------------------------------------------- /byteman/README.md: -------------------------------------------------------------------------------- 1 | Byteman is a tool which simplifies tracing and testing of Java programs. Byteman allows you to insert extra Java code into your application, either as it is loaded during JVM startup or even after it has already started running. The injected code is allowed to access any of your data and call any application methods, including where they are private. You can inject code almost anywhere you want and there is no need to prepare the original source code in advance nor do you have to recompile, repackage or redeploy your application. In fact you can remove injected code and reinstall different code while the application continues to execute. 2 | 3 | The simplest use of Byteman is to install code which traces what your application is doing. This can be used for monitoring or debugging live deployments as well as for instrumenting code under test so that you can be sure it has operated correctly. By injecting code at very specific locations you can avoid the overheads which often arise when you switch on debug or product trace. Also, you decide what to trace when you run your application rather than when you write it so you don't need 100% hindsight to be able to obtain the information you need. 4 | 5 | [link](http://www.jboss.org/byteman/) 6 | -------------------------------------------------------------------------------- /cacti/README.md: -------------------------------------------------------------------------------- 1 | http://www.cacti.net/ 2 | -------------------------------------------------------------------------------- /cavalieri/README.md: -------------------------------------------------------------------------------- 1 | *Cavalieri* is a C++ event stream processing tool to monitor distrubuted 2 | systems, it is inspired by the awesome Riemann project. 3 | 4 | [Cavalieri](http://github.com/juruen/cavalieri) 5 | -------------------------------------------------------------------------------- /cepmon/README.md: -------------------------------------------------------------------------------- 1 | Send your graphite metric stream through the powerful Esper CEP engine for better real-time data analysis. 2 | 3 | 4 | 5 | -------------------------------------------------------------------------------- /check_mk/README.md: -------------------------------------------------------------------------------- 1 | Check_MK is comprehensive IT monitoring solution in the tradition of Nagios. Check_MK is available as Raw Edition, which is 100% pure open source, and as Enterprise Edition with a lot of additional features and professional support. 2 | 3 | [link](http://mathias-kettner.com/check_mk.html) 4 | -------------------------------------------------------------------------------- /circonus/README.md: -------------------------------------------------------------------------------- 1 | 2 | http://www.circonus.com 3 | 4 | Any Data. Any System. Any Where. Circonus combines multiple monitoring, alerting, event processing, and analytics tools into one unified solution. Visualize any data, in any application, from any system (cloud or legacy), in real-time. Circonus scales from a single team, to a worldwide organization with thousands of devices tracking millions of metrics. API driven automation empowers developers and makes operational teams incredibly efficient, while analytics drive insights that improve organization-wide performance. 5 | -------------------------------------------------------------------------------- /clockwork/README.md: -------------------------------------------------------------------------------- 1 | Clockwork is a cron replacement. It runs as a lightweight, long-running Ruby 2 | process which sits alongside your web processes (Mongrel/Thin) and your 3 | worker processes (DJ/Resque/Minion/Stalker) to schedule recurring work at 4 | particular times or dates. For example, refreshing feeds on an hourly basis, 5 | or send reminder emails on a nightly basis, or generating invoices once a 6 | month on the 1st. 7 | 8 | https://github.com/adamwiggins/clockwork -------------------------------------------------------------------------------- /cloudkick-plugins/README.md: -------------------------------------------------------------------------------- 1 | [link](https://github.com/cloudkick/agent-plugins) 2 | [homepage](http://cloudkick.com) 3 | 4 | A collection of custom plugins for the Cloudkick agent and Monitoring-As-A-Service provider. Easily adapted to any number of monitoring tools. 5 | -------------------------------------------------------------------------------- /collectd-graphite/README.md: -------------------------------------------------------------------------------- 1 | This plugin acts as bridge between collectd's huge base of 2 | available plugins and graphite's excellent graphing capabilities. 3 | It sends collectd data directly to your graphite server. 4 | 5 | https://github.com/joemiller/collectd-graphite -------------------------------------------------------------------------------- /collectd/README.md: -------------------------------------------------------------------------------- 1 | collectd gathers statistics about the system it is running on and stores 2 | this information. Those statistics can then be used to find current 3 | performance bottlenecks (i.e. performance analysis) and predict future 4 | system load (i.e. capacity planning). Or if you just want pretty graphs 5 | of your private server and are fed up with some homegrown solution you're 6 | at the right place, too ;). 7 | 8 | http://collectd.org/ -------------------------------------------------------------------------------- /consul/README.md: -------------------------------------------------------------------------------- 1 | [consul](https://github.com/hashicorp/consul) - tool for service discovery, monitoring and configuration. See also http://www.consul.io 2 | 3 | -------------------------------------------------------------------------------- /critical/README.md: -------------------------------------------------------------------------------- 1 | Critical is my take on network/infrastructure monitoring. Here are the big 2 | ideas: 3 | 4 | * Infrastructure as code: The monitoring system should be an internal DSL so it 5 | can natively interact with any part of your infrastructure you can find or 6 | write a library for. You should also be able to productively alter its guts if 7 | you need to. This is a monitoring system for ops people who write code and 8 | coders who do ops. 9 | * Client-based: This scales better, and is actually easier to configure if you 10 | use configuration management, which you should be doing anyway. 11 | * Continuous verification: Critical has a single shot mode in 12 | addition to the typical daemonized operation. This allows you to verify the 13 | configuration on a host after making changes and then continuously monitor the 14 | state of the system using the same verification tests. 15 | * Declarative: Declare what the state of your system is supposed to be. 16 | * Alerting and Trending together: a client/agent can do both of these at the 17 | same time with less configuration overhead. It makes sense to keep them 18 | separate on the server side. 19 | * Licensing: "Do what thou wilt shall be the whole of the law," except for 20 | patent trolls, etc. So, Apache 2.0 it is. 21 | 22 | https://github.com/danielsdeleo/critical -------------------------------------------------------------------------------- /cube/README.md: -------------------------------------------------------------------------------- 1 | # Cube 2 | 3 | **Cube** is a system for collecting timestamped events and deriving metrics. By collecting events rather than metrics, Cube lets you compute aggregate statistics *post hoc*. It also enables richer analysis, such as quantiles and histograms of arbitrary event sets. Cube is built on [MongoDB](http://www.mongodb.org) and available under the [Apache License](/square/cube/blob/master/LICENSE). 4 | 5 | [See the wiki.](/square/cube/wiki) 6 | -------------------------------------------------------------------------------- /cucumber-nagios/README.md: -------------------------------------------------------------------------------- 1 | cucumber-nagios allows you to write high-level behavioural tests of web application, and plug the results into Nagios. 2 | 3 | -------------------------------------------------------------------------------- /darshan/README: -------------------------------------------------------------------------------- 1 | Darshan is designed to capture an accurate picture of application I/O behavior, including properties such as patterns of access within files, with minimum overhead. The name is taken from a Sanskrit word for “sight” or “vision”. 2 | 3 | Darshan can be used to investigate and tune the I/O behavior of complex HPC applications. In addition, Darshan’s lightweight design makes it suitable for full time deployment for workload characterization of large systems. We hope that such studies will help the storage research community to better serve the needs of scientific computing. 4 | 5 | Darshan was originally developed on the IBM Blue Gene series of computers deployed at the Argonne Leadership Computing Facility, but it is portable across a wide variety of platforms include the Cray XE6, Cray XC30, and Linux clusters. Darshan routinely instruments jobs using up to 786,432 compute cores on the Mira system at ALCF. 6 | 7 | http://www.mcs.anl.gov/research/projects/darshan/ 8 | -------------------------------------------------------------------------------- /datadog/README.md: -------------------------------------------------------------------------------- 1 | Datadog is a cloud-based service that brings into one convenient place metrics and events from your systems, applications and cloud providers. 2 | 3 | http://www.datadoghq.com/ 4 | -------------------------------------------------------------------------------- /dataloop.io/README.md: -------------------------------------------------------------------------------- 1 | [Product page](https://www.dataloop.io/) 2 | 3 | [Github Dataloop.IO](https://github.com/dataloop) 4 | 5 | Dataloop.IO is provided as a Cloud Service. Install our simple agent on each of your servers which works out of the box with thousands of Nagios check scripts. We accept metrics via Graphite and StatsD ports too. -------------------------------------------------------------------------------- /deadman-check/README.md: -------------------------------------------------------------------------------- 1 | [link](https://github.com/sepulworld/deadman-check) 2 | 3 | ## deadman-check 4 | 5 | Monitoring companion for [Nomad periodic jobs](https://www.nomadproject.io/docs/runtime/schedulers.html#batch) and Cron 6 | Docker container driven or command line. Intergrates with Slack messaging 7 | -------------------------------------------------------------------------------- /disqus-nagios-plugins/README.md: -------------------------------------------------------------------------------- 1 | [link](http://github.com/disqus/nagios-plugins) 2 | 3 | Only check_graphite.rb for now. 4 | -------------------------------------------------------------------------------- /epicnms/README.md: -------------------------------------------------------------------------------- 1 | Monitoring framework for time based numeric data. 2 | 3 | [link](http://code.google.com/p/epicnms/) 4 | -------------------------------------------------------------------------------- /esper/README.md: -------------------------------------------------------------------------------- 1 | Esper is a component for complex event processing (CEP), available 2 | for Java as Esper, and for .NET as NEsper. 3 | 4 | Esper and NEsper enable rapid development of applications that 5 | process large volumes of incoming messages or events. Esper and NEsper 6 | filter and analyze events in various ways, and respond to conditions 7 | of interest in real-time. 8 | 9 | [tutorial](http://esper.codehaus.org/tutorials/tutorial/tutorial.html) 10 | [related](http://www.igvita.com/2011/05/27/streamsql-event-processing-with-esper/) 11 | 12 | -------------------------------------------------------------------------------- /etsy-nagios_tools/README.md: -------------------------------------------------------------------------------- 1 | Nagios tools from the good folks at Etsy. For example, "check_graphite" 2 | 3 | https://github.com/etsy/nagios_tools 4 | -------------------------------------------------------------------------------- /extopus/README.md: -------------------------------------------------------------------------------- 1 | Tobi Oetiker is working on a new Monitoring Aggregator 2 | 3 | http://oss.oetiker.ch/extopus/ 4 | ` 5 | 6 | according to the home page : 7 | 8 | "Extopus is an aggregating frontend to monitoring systems. Its plug-in architecture provides an easy route to integrating output from a wide array of monitoring systems into a single instance of Extopus. 9 | 10 | Integration can range from simple iframe-ing a particular page from another monitoring system to accessing data from another system using rpc calls and displaying the results in a custom presentation plugin inside the Extopus frontend. 11 | 12 | The Extopus backend is written in Perl (using Mojolicious) and the frontend is written in javascript (with Qooxdoo). This architecture provides a high level of implementation flexibility and allowed us to create a highly interactive end user experience. 13 | 14 | Whether you have a small setup with a few hundred or a large one with millions of items, Extopus will provide a user friendly interface to accessing your monitoring data." 15 | -------------------------------------------------------------------------------- /extrahop/README.md: -------------------------------------------------------------------------------- 1 | [product page](http://www.extrahop.com/) 2 | 3 | [github team page](https://github.com/ExtraHop) 4 | 5 | Extrahop is a network-monitoring appliance (solution) that provides real-time insight into traffic flowing trough your systems. 6 | It runs an agent on the monitored systems that aggregate the data then parsed in the collector(s) for analysis. 7 | Provides dashboards, metrics and analysis. 8 | Collector works both as an hardware appliance and Amazon AMI and remains under the control of the organizatoin (not sharing data with EH) 9 | It can be further extended via scripts/triggers for anomaly detecion and alerting purposes. 10 | 11 | -------------------------------------------------------------------------------- /extrememon/README.md: -------------------------------------------------------------------------------- 1 | 2 | https://extremon.org/ 3 | 4 | 5 | From the Extreme Monitoring Manifesto: 6 | 7 | Live, with Subsecond temporal resolution where possible, as fast as doesn’t disrupt service, elsewhere 8 | Display on a meaningful representation, and in real-time. 9 | Simple Text-based Internet-Friendly Subscription Push API 10 | Implicit Provisioning (Test-driven infrastructure) 11 | Agent push the data as it is gathered 12 | Hot-pluggable components 13 | Re-use as many ubiquitous technologies as possible 14 | Extremon-Display is an implementation of the first and third, 6th and 7th targets: 15 | Live, with Subsecond temporal resolution where possible, 16 | Simple Text-based Internet-Friendly Subscription Push API 17 | Hot-pluggable components 18 | and Re-use as many ubiquitous technologies as possible 19 | 20 | see https://extremon.org/ 21 | 22 | For the second target, see the ExtreMon-Display project 23 | 24 | 25 | https://github.com/m4rienf/ExtreMon 26 | https://github.com/m4rienf/ExtreMon-Display 27 | -------------------------------------------------------------------------------- /fitb/README.md: -------------------------------------------------------------------------------- 1 | FITB is a tool that automatically polls every port on a list of switches you give it. Simple configuration, precise polling, easy searching and automatic discovery of both new ports and ports that go offline are the goals of FITB. 2 | -------------------------------------------------------------------------------- /flapjack/README.md: -------------------------------------------------------------------------------- 1 | Flapjack is a scalable and distributed monitoring system. It natively 2 | talks the Nagios plugin format, and can easily be scaled from 3 | 1 server to 1000. 4 | 5 | Flapjack tries to adhere to the following tenets: 6 | 7 | * it should be simple to set up, configure, and maintain 8 | * it should easily scale from a single host to multiple 9 | 10 | http://flapjack.io/ 11 | -------------------------------------------------------------------------------- /folsom/README.md: -------------------------------------------------------------------------------- 1 | Erlang application metrics gathering library. 2 | 3 | https://github.com/boundary/folsom/blob/master/README.md 4 | -------------------------------------------------------------------------------- /ganglia/README.md: -------------------------------------------------------------------------------- 1 | Ganglia is a scalable distributed monitoring system for high-performance 2 | computing systems such as clusters and Grids. It is based on a hierarchical 3 | design targeted at federations of clusters. It leverages widely used 4 | technologies such as XML for data representation, XDR for compact, portable 5 | data transport, and RRDtool for data storage and visualization. It uses 6 | carefully engineered data structures and algorithms to achieve very low 7 | per-node overheads and high concurrency. The implementation is robust, has been 8 | ported to an extensive set of operating systems and processor architectures, 9 | and is currently in use on thousands of clusters around the world. It has been 10 | used to link clusters across university campuses and around the world and can 11 | scale to handle clusters with 2000 nodes. 12 | 13 | Ganglia is a BSD-licensed open-source project that grew out of the University 14 | of California, Berkeley Millennium Project which was initially funded in large 15 | part by the National Partnership for Advanced Computational Infrastructure 16 | (NPACI) and National Science Foundation RI Award EIA-9802069. NPACI is funded 17 | by the National Science Foundation and strives to advance science by creating a 18 | ubiquitous, continuous, and pervasive national computational infrastructure: 19 | the Grid. Current support comes from Planet Lab: an open platform for 20 | developing, deploying, and accessing planetary-scale services. 21 | 22 | http://ganglia.sourceforge.net/ 23 | -------------------------------------------------------------------------------- /glances/README.md: -------------------------------------------------------------------------------- 1 | [link](https://github.com/nicolargo/glances) 2 | -------------------------------------------------------------------------------- /graph-explorer/README.md: -------------------------------------------------------------------------------- 1 | [Graph-Explorer](http://vimeo.github.io/graph-explorer) 2 | -------------------------------------------------------------------------------- /graphite/README.md: -------------------------------------------------------------------------------- 1 | Graphite is an enterprise-scale monitoring tool that runs well on cheap 2 | hardware. It was originally designed and written by Chris Davis at Orbitz in 3 | 2006 as side project that ultimately grew to be a foundational monitoring tool. 4 | In 2008, Orbitz allowed Graphite to be released under the open source Apache 5 | 2.0 license. Since then Chris has continued to work on Graphite and has 6 | deployed it at other companies including Sears, where it serves as a pillar of 7 | the e-commerce monitoring system. Today many large companies use it. 8 | 9 | http://graphite.wikidot.com/ 10 | -------------------------------------------------------------------------------- /graphiteworker/README.md: -------------------------------------------------------------------------------- 1 | ## About 2 | 3 | This is a [Gearman](http://gearman.org/) Worker that is designed to use the nagios performance data generated and published by the awesome Nagios-Plugin [Mod-Gearman](http://mod-gearman.org/) and feed them into [Graphite](http://graphite.wikidot.com/) or anything that understands one of the Graphite-Protocols. 4 | 5 | Since it is a worker you can scale it as you like by using a larger pool (processes that are spawned on the machine running the graphiteworker) or by starting it on a many machines as you like. It only opens one connection to graphite and sends all data arriving in Germans perfdata queue. You can choose if you want to use the line or the pickle protocol. Since graphite works best with the line protocol I suggest you to use it to feed your data. 6 | 7 | [link](https://github.com/Crapworks/graphiteworker) 8 | -------------------------------------------------------------------------------- /graylog2/README.md: -------------------------------------------------------------------------------- 1 | [homepage](http://graylog2.org/) 2 | 3 | [server source](https://github.com/Graylog2/graylog2-server) 4 | 5 | [webui source](https://github.com/Graylog2/graylog2-web-interface) 6 | 7 | Graylog2 is a log storing framework using a MongoDB backend and a very nice UI for filtering and search. 8 | 9 | Taulia is hosting a live Graylog2 [demo](http://public-graylog2.taulia.com/) Log in with the user admin or user and the password graylog2 10 | -------------------------------------------------------------------------------- /groundwork/README.md: -------------------------------------------------------------------------------- 1 | 2 | 3 | 4 | GroundWork 5 | 6 | build on top of nagios, Cacti and other toolso 7 | 8 | @botchagalupe once coined the term "To pull a GroundWork" meaning , taking an Open Source project, building a wrapper around it then selling it off a your own. 9 | 10 | 11 | -------------------------------------------------------------------------------- /hobbit/README.md: -------------------------------------------------------------------------------- 1 | 2 | And advanced version of Big Brother 3 | 4 | 5 | http://sourceforge.net/projects/hobbitmon/ 6 | 7 | 8 | As of 2010-07-09, this project may now be found at https://sourceforge.net/projects/xymon/. 9 | -------------------------------------------------------------------------------- /hyperic/README.md: -------------------------------------------------------------------------------- 1 | 2 | Hyperic HQ, 3 | 4 | generated a lot of fuzz back in 2007. 5 | they then got acquired by Springsource 6 | which then got acquired by VMWare 7 | gone mostly silent 8 | 9 | 10 | http://www.hyperic.com/ 11 | -------------------------------------------------------------------------------- /influxdb/README.md: -------------------------------------------------------------------------------- 1 | # InfluxDB 2 | 3 | [InfluxDB](https://github.com/influxdb/influxdb#influxdb-) is an open source distributed time series database with no external dependencies. It's useful for recording metrics, events, and performing analytics. 4 | 5 | It has a built-in HTTP API so you don't have to write any server side code to get up and running. 6 | 7 | InfluxDB is designed to be scalable, simple to install and manage, and fast to get data in and out. 8 | 9 | It aims to answer queries in real-time. That means every data point is indexed as it comes in and is immediately available in queries that should return in < 100ms. 10 | -------------------------------------------------------------------------------- /ipm/README: -------------------------------------------------------------------------------- 1 | http://ipm-hpc.sourceforge.net/ 2 | -------------------------------------------------------------------------------- /isotope11_traffic_lights/README.md: -------------------------------------------------------------------------------- 1 | [github](https://github.com/johndavid400/Isotope11_traffic_lights) 2 | 3 | # Monitoring your Continuous Integration Server with Traffic Lights and an Arduino 4 | ### A way for Isotope11 to visually monitor the testing status of its many software projects. 5 | Today I am going to walk through our recent continuous integration Traffic light 6 | notifier project that we just finished at the office. This project stemmed from 7 | my company's desire to immediately know if a developer has broken a software 8 | project, and what better way to do that than to have a huge red light flashing 9 | in your face. We connected an old salvaged traffic light fixture to our Jenkins 10 | CI-server that monitors the testing status of all of our current software 11 | projects. If all our tests are passing, the light stays green, if any test fails 12 | the light turns red to provide a visual notification of a problem. While Jenkins 13 | is running a test suite on any project, the yellow light will flash to let us 14 | know of the activity. 15 | 16 | -------------------------------------------------------------------------------- /javasimon/README.md: -------------------------------------------------------------------------------- 1 | Java Simon is a simple monitoring API that allows you to follow and better understand your application. Monitors (familiarly called Simons) are placed directly into your code and you can choose whether you want to count something or measure time/duration. 2 | 3 | [link](http://code.google.com/p/javasimon/) 4 | -------------------------------------------------------------------------------- /jimi-robot/README.md: -------------------------------------------------------------------------------- 1 | [link](https://github.com/arozhkov/jimi-robot) 2 | 3 | ## JMX Collector 4 | 5 | * Easy to setup and configure. 6 | * Light. _Well RAM is so cheap nowadays._ 7 | * Not intrusive. _As much as RMI could be._ 8 | * Integration with third-party tools. _Graphite_ 9 | * Collect simple numeric attributes from mbeans and combined data attributes. 10 | -------------------------------------------------------------------------------- /jmxtrans/README.md: -------------------------------------------------------------------------------- 1 | # jmxtrans 2 | Input: JMX 3 | Output: Statsd, Graphite, Ganglia, RRD 4 | 5 | Sort of a logstash for JMX metrics. Uses JSON for config files: 6 | 7 | [https://github.com/jmxtrans/jmxtrans](Project on github) 8 | -------------------------------------------------------------------------------- /jolokia/README.md: -------------------------------------------------------------------------------- 1 | Jolokia is remote JMX with JSON over HTTP. 2 | 3 | It is fast, simple, polyglot and has unique features. It's JMX on Capsaicin. 4 | 5 | [link](http://labs.consol.de/lang/en/jolokia/) 6 | -------------------------------------------------------------------------------- /jwatchdog/README.md: -------------------------------------------------------------------------------- 1 | jWatchdog 2 | ========= 3 | The jWatchdog project delivers a simple watchdog to actively monitor your infrastructure and send you notifications in case something goes wrong. 4 | 5 | jWatchdog is configured using a simple XML configuration file. This configuration file can be changed on-the-fly without a need to restart the watchdog. 6 | 7 | jWatchdog also comes with an Android client application capable of intercepting and alerting on jWatchdog SMS messages. 8 | 9 | [Google Code jWatchdog project](http://code.google.com/p/jwatchdog/) 10 | 11 | [jWatchdog Maven site](http://www.e-contract.be/sites/jwatchdog/) 12 | 13 | [jWatchdog Android client](https://play.google.com/store/apps/details?id=be.e_contract.jwatchdog.android) 14 | -------------------------------------------------------------------------------- /kairosdb/README.md: -------------------------------------------------------------------------------- 1 | KairosDB is a rewrite of the original OpenTSDB (http://opentsdb.net) project. 2 | 3 | [http://github.com/proofpoint/kairosdb](http://github.com/proofpoint/kairosdb) 4 | 5 | [http://code.google.com/p/kairosdb](http://code.google.com/p/kairosdb) 6 | -------------------------------------------------------------------------------- /kibana/README.md: -------------------------------------------------------------------------------- 1 | [link](http://www.elasticsearch.org/overview/kibana/) 2 | 3 | Kibana is a tool for visualizing and creating dashboards out of events collected into Elasticsearch from Logstash. 4 | -------------------------------------------------------------------------------- /librato/README.md: -------------------------------------------------------------------------------- 1 | Librato provides a complete SaaS solution for monitoring and understanding the metrics that impact businesses at all levels of the stack. They provide everything needed to visualize, analyze, and actively alert on the metrics that matter. 2 | 3 | https://metrics.librato.com/ 4 | 5 | * [dropwizard-librato](https://github.com/librato/dropwizard-librato) 6 | * [librato-annotate](https://github.com/librato/librato-annotate) 7 | * [librato-java](https://github.com/librato/librato-java) 8 | * [librato-metrics](https://github.com/librato/librato-metrics) 9 | * [librato-rack](https://github.com/librato/librato-rack) 10 | * [librato-rails](https://github.com/librato/librato-rails) 11 | * [librato-services](https://github.com/librato/librato-services) 12 | * [librato-storm-kafka](https://github.com/librato/librato-storm-kafka) 13 | * [metrics-librato](https://github.com/librato/metrics-librato) 14 | * [papertrail-cookbook](https://github.com/librato/papertrail-cookbook) 15 | * [python-librato](https://github.com/librato/python-librato) 16 | * [statsd-cookbook](https://github.com/librato/statsd-cookbook) 17 | * [statsd-librato-backend](https://github.com/librato/statsd-librato-backend) 18 | -------------------------------------------------------------------------------- /librenms/README.md: -------------------------------------------------------------------------------- 1 | LibreNMS is an autodiscovering PHP/MySQL/SNMP based network monitoring which includes support for a wide range of network hardware and operating systems including Cisco, Linux, FreeBSD, Juniper, Brocade, Foundry, HP and many more. LibreNMS is a community-based fork of Observium. 2 | 3 | https://github.com/librenms/librenms/ 4 | -------------------------------------------------------------------------------- /lmt/README: -------------------------------------------------------------------------------- 1 | Lustre monitoring Tool 2 | 3 | https://github.com/chaos/lmt/wiki 4 | -------------------------------------------------------------------------------- /lnav/README.md: -------------------------------------------------------------------------------- 1 | [link](https://github.com/tstack/lnav/blob/master/README.md) 2 | -------------------------------------------------------------------------------- /logstash/README.md: -------------------------------------------------------------------------------- 1 | [link](http://logstash.net/) 2 | logstash is a tool for managing events and logs. You can use it to collect logs, 3 | parse them, and store them for later use (like, for searching). Speaking of 4 | searching, logstash comes with a web interface for searching and drilling into 5 | all of your logs. 6 | 7 | It is fully free and fully open source. The license is Apache 2.0, meaning you 8 | are pretty much free to use it however you want in whatever way. 9 | 10 | If you are looking for a 'front-end' to search through logstash data, Kibana 11 | is a good choice. 12 | 13 | Created by Jordan Sissel (@jordansissel) 14 | -------------------------------------------------------------------------------- /logster/README.md: -------------------------------------------------------------------------------- 1 | Logster is a utility for reading log files and generating metrics in Graphite or 2 | Ganglia. It is ideal for visualizing trends of events that are occurring in your 3 | application/system/error logs. For example, you might use logster to graph the 4 | number of occurrences of HTTP response code that appears in your web server logs. 5 | -------------------------------------------------------------------------------- /metis/README.md: -------------------------------------------------------------------------------- 1 | [github](https://github.com/krobertson/metis) 2 | 3 | # Metis 4 | 5 | "Metis is an implementation of the Nagios NRPE daemon in Ruby. It provides an easy framework to write your own monitors in Ruby, have them running in a daemon, and distribute/share them with others." 6 | -------------------------------------------------------------------------------- /metrics/README.md: -------------------------------------------------------------------------------- 1 | A Java application metrics gathering library. 2 | 3 | http://metrics.codahale.com/ 4 | 5 | -------------------------------------------------------------------------------- /mms-10gen/README.md: -------------------------------------------------------------------------------- 1 | MongoDB Monitoring Service (MMS) 2 | 3 | MongoDB Monitoring Service (MMS) is a free cloud-based service provided by 10gen for monitoring MongoDB deployments in real time. MMS features charts, custom dashboards and automated alerting to track performance, utilization and other KPIs. It requires minimal setup and configuration, and within minutes devops and sysadmin teams can manage and optimize MongoDB deployments. 4 | 5 | Proactive Monitoring and Management 6 | 7 | 8 | 9 | MMS collects statistics on all key server and hardware indicators and presents the data in a powerful web console. MMS tracks over 100 metrics to monitor the health of MongoDB clusters. By default, the MMS dashboard displays 9 metrics: 10 | 11 | Op Counters – Count of operations executed per second 12 | Memory – Amount of data MongoDB is using 13 | Lock Percent – Percent of time spent in write lock 14 | Background Flush – Average time to flush data to disk 15 | Connections – Number of current open connections to MongoDB 16 | Queues – Number of operations waiting to run 17 | Page Faults – Number of page faults to disk 18 | Replication – Oplog length (for primary) and replication delay to primary (on secondary) 19 | Journal – Amount of data written to journal 20 | Designed specifically for MongoDB, MMS ensures that users have visibility into the right metrics to optimize applications during development and in production. With sharded clusters comprising dozens of nodes, MMS provides a holistic view of entire MongoDB deployments. 21 | 22 | For customers with MongoDB Subscriptions, MMS enables 10gen engineers to monitor deployments on an ongoing basis and suggest corrective action before degradation occurs. MMS also helps shorten the response time for commercial support issues. When customers file tickets with the 10gen support team, our engineers can examine their MMS data, enabling them to identify customers' system configurations and any troubling signs about their clusters. 23 | 24 | Easy Setup 25 | 26 | Setting up MMS is simple: 27 | 28 | Create an account at mms.10gen.com. 29 | Download and install the MMS agent on your cluster. 30 | Within minutes, a dashboard of your cluster will be available on mms.10gen.com. 31 | No administration or maintenance is required. 32 | -------------------------------------------------------------------------------- /mod-log-firstbyte/README.md: -------------------------------------------------------------------------------- 1 | Apache 2.x module that measures time to first byte and exposes this as a new 2 | log format string. Code originally developed at Google and largely abandoned now. 3 | 4 | Be nice to get some more traction on this and even get it built into the official 5 | Apache release. 6 | 7 | http://code.google.com/p/mod-log-firstbyte/ 8 | -------------------------------------------------------------------------------- /molog/README.md: -------------------------------------------------------------------------------- 1 | 2 | Molog : 3 | 4 | http://www.smetj.net/wiki/Molog 5 | 6 | Build a scalable monitor and search solution for application and system logs with Nagios. 7 | 8 | Molog is processing layer for a scalable logging infrastructure which consumes LogStash processed logs from RabbitMQ and sends updates to Nagios and ElasticSearch. 9 | 10 | * A stand alone daemon with configurable parallel workers. 11 | * Workers consume LogStash processed messages from RabbitMQ and perform ignore regex matching on them. 12 | * Regex rules can be applied to all LogStash generated fields. 13 | * Sends Nagios passive check results back to RabbitMQ. 14 | * Nagios check results can be consumed from RabbitMQ into Nagios using Krolyk. 15 | * Forwards and stores all messages to ElasticSearch. 16 | * Only stores references to ElasticSearch records in a MongoDB instance. 17 | * Provides REST API for querying and manipulating references and regexes. 18 | * Includes molog_cli an interactive REST client to manipulate records, matches and regexes. 19 | 20 | MoLog is written in Python. 21 | -------------------------------------------------------------------------------- /moncli/README.md: -------------------------------------------------------------------------------- 1 | 2 | https://github.com/smetj/moncli/ 3 | 4 | Moncli is a generic MONitoring CLIent which executes and processes requests on an external system in order to interact with the host's local information sources which are normally not available over the network. Once Moncli has executed and evaluated the request it submits the check results back into the message broker infrastructure, where the results are ready to be by another process. 5 | -------------------------------------------------------------------------------- /munin/README.md: -------------------------------------------------------------------------------- 1 | Munin is a networked resource monitoring tool that can help analyze resource 2 | trends and "what just happened to kill our performance?" problems. It is 3 | designed to be very plug and play. A default installation provides a lot of 4 | graphs with almost no work. 5 | 6 | http://munin-monitoring.org/ 7 | -------------------------------------------------------------------------------- /nagios-api/README.md: -------------------------------------------------------------------------------- 1 | A REST-like, JSON interface to Nagios complete with CLI interface 2 | 3 | [link](https://github.com/xb95/nagios-api) 4 | -------------------------------------------------------------------------------- /nagios-dashboard/README.md: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/monitoringsucks/tool-repos/50ac4148dfe917a949339935deade21d8cc872aa/nagios-dashboard/README.md -------------------------------------------------------------------------------- /nagios/README.md: -------------------------------------------------------------------------------- 1 | Nagios is a popular open source computer system and network monitoring software 2 | application. It watches hosts and services, alerting users when things go wrong 3 | and again when they get better. 4 | 5 | http://www.nagios.org/ 6 | -------------------------------------------------------------------------------- /naglite2/README.md: -------------------------------------------------------------------------------- 1 | Full screen Nagios viewer intended for NOC/monitoring screens 2 | -------------------------------------------------------------------------------- /nervous/README.md: -------------------------------------------------------------------------------- 1 | oNervous - Monitoring doesn't have to suck. 2 | About Nervous 3 | 4 | Nervous is a simple plugin based monitoring system with support for sending data to Graphite or Response. Nervous makes it really easy to get data into graphite. 5 | 6 | https://github.com/gflarity/nervous 7 | -------------------------------------------------------------------------------- /netdata/README.md: -------------------------------------------------------------------------------- 1 | Netdata is a compact, resource-light, but feature rich performance and monitoring solution for Linux, FreeBSD, and MacOS servers. It's written in C and takes very little resources to set up. 2 | 3 | [https://my-netdata.io/](https://my-netdata.io/) 4 | -------------------------------------------------------------------------------- /netdb/README.md: -------------------------------------------------------------------------------- 1 | NetDB monitors network devices and switch port status over time. Excellent for knowing exactly what device is plugged into what switch and where that device has been in the past. 2 | 3 | http://netdbtracking.sourceforge.net/ -------------------------------------------------------------------------------- /netdot/README.md: -------------------------------------------------------------------------------- 1 | netdot is an open source tool for collecting, organizing, and maintaining network information. 2 | 3 | http://netdot.uoregon.edu/ 4 | -------------------------------------------------------------------------------- /ntopng/README.md: -------------------------------------------------------------------------------- 1 | [product page](http://www.ntop.org/) 2 | 3 | [main repository (SVN)](https://svn.ntop.org/svn/ntop/trunk/ntopng/) 4 | 5 | [github mirror](https://github.com/xtao/ntopng) 6 | 7 | Ntopng is a new generation of the well known ntop utility. 8 | Handles protocol recognition and transmission corelatiion for graphing and analysis. 9 | New version has improved performance, updated UI and added extensibility. 10 | Supports building hierarchical structures (comms via zeromq and json) as well as recently added support for Elasticsearch integration (trunk only) 11 | -------------------------------------------------------------------------------- /oculus/README.md: -------------------------------------------------------------------------------- 1 | [oculus](https://github.com/etsy/oculus) - anomaly correlation component 2 | -------------------------------------------------------------------------------- /okconfig/README.md: -------------------------------------------------------------------------------- 1 | OKCONFIG 2 | ======== 3 | 4 | A robust template mechanism for Nagios configuration files. Providing 5 | standardized set of configuration templates and select quality plugins 6 | to enterprise quality monitoring. 7 | -------------------------------------------------------------------------------- /opennms/README.md: -------------------------------------------------------------------------------- 1 | OpenNMS is the world’s first enterprise grade network management application 2 | platform developed under the open source model. 3 | 4 | http://www.opennms.org/ 5 | -------------------------------------------------------------------------------- /opentsdb/README.md: -------------------------------------------------------------------------------- 1 | OpenTSDB is a distributed, scalable Time Series Database (TSDB) written on 2 | top of HBase. OpenTSDB was written to address a common need: store, index 3 | and serve metrics collected from computer systems (network gear, 4 | operating systems, applications) at a large scale, and make this data 5 | easily accessible and graphable. 6 | 7 | Thanks to HBase's scalability, OpenTSDB allows you to collect many thousands 8 | of metrics from thousands of hosts and applications, at a high rate (every 9 | few seconds). OpenTSDB will never delete or downsample data and can easily 10 | store billions of data points. As a matter of fact, StumbleUpon uses it to 11 | keep track of hundred of thousands of time series and collects over 12 | 100 million data points per day in their main production cluster. 13 | 14 | http://opentsdb.net/ 15 | -------------------------------------------------------------------------------- /opserver/README.md: -------------------------------------------------------------------------------- 1 | Opserver is a monitoring system by the team at Stack Exchange, home of Stack Overflow. It is a tool for monitoring: 2 | 3 | servers 4 | SQL clusters/instances 5 | redis 6 | elastic search 7 | exception logs 8 | haproxy 9 | ... and more as we go 10 | 11 | https://github.com/opserver/Opserver 12 | -------------------------------------------------------------------------------- /overwatch/README.md: -------------------------------------------------------------------------------- 1 | Overwatch is a monitoring application designed for flexibility in all aspects, 2 | from how data is collected to the way notifications are handled. 3 | 4 | https://github.com/danryan/overwatch 5 | -------------------------------------------------------------------------------- /pandora-fms/README.md: -------------------------------------------------------------------------------- 1 | 2 | 3 | Pandora FMS is famous for being the guys that were throwing bottles of beer from the 2nd floor of the Roi d'Espagne during a Fosdem Beer event. 4 | 5 | It was also the last year that the Roi d'Espagne hosted the Fosdem Beer event. 6 | 7 | 8 | http://pandorafms.org/ 9 | 10 | -------------------------------------------------------------------------------- /parfait/README.md: -------------------------------------------------------------------------------- 1 | Parfait is a performance monitoring library for Java which provides mechanisms for collecting counter and timing metrics, then exposing them through a variety of mechanisms including JMX beans and the open-source cross-platform [Performance Co-Pilot](http://oss.sgi.com/projects/pcp/). 2 | 3 | 4 | [link](http://code.google.com/p/parfait/) 5 | -------------------------------------------------------------------------------- /pencil/README.md: -------------------------------------------------------------------------------- 1 | Graphite dashboard system 2 | 3 | https://github.com/fetep/pencil 4 | -------------------------------------------------------------------------------- /plumbr/README.md: -------------------------------------------------------------------------------- 1 | Plumbr is the performance monitoring solution, known by its unique capability of linking poor user experience down to a single line in the source code as root cause. 2 | Plumbr can monitor any JVM-based application. 3 | 4 | 5 | https://plumbr.eu 6 | -------------------------------------------------------------------------------- /plumd/README.md: -------------------------------------------------------------------------------- 1 | Plumd is similar to tools like python-diamond and collectd - it's a small daemon that gathers system metrics and sends them to one or more time series databases. You can easily add support for new metrics and time series databases by adding your own reader and writer plugins. 2 | 3 | [plumd](http://github.com/s4z/plumd) 4 | -------------------------------------------------------------------------------- /porkchop/README.md: -------------------------------------------------------------------------------- 1 | Porkchop is a simple network-based system information server. You write plugins for it and it responds with the data based on your request. 2 | 3 | Check the readme for more info. 4 | 5 | [link](http://github.com/disqus/porkchop) 6 | -------------------------------------------------------------------------------- /rackspace-cloud-monitoring/README.md: -------------------------------------------------------------------------------- 1 | ## Rackspace Cloud Monitoring 2 | 3 | Rackspace Cloud Monitoring analyzes cloud services and dedicated infrastructure 4 | using a simple, yet powerful API. The API currently includes monitoring for 5 | external services. The key benefits you receive from using this API include the 6 | following: 7 | 8 | ### Use of Domain Specific Language I(DSL) 9 | The Rackspace Cloud Monitoring API uses a DSL, which makes it a powerful tool 10 | for configuring advanced monitoring features. For example, typically complex 11 | tasks, such as defining triggers on thresholds for metrics or performing an 12 | inverse string match become much easier with a concise, special purpose language 13 | created for defining alarms. For more information, see Alarms. 14 | 15 | ### Monitoring from Multiple Datacenters 16 | Rackspace Cloud Monitoring allows you to simultaneously monitor the performance 17 | of different resources from multiple datacenters and provides a clear picture of 18 | overall system health. It includes tunable parameters to interpret mixed results 19 | which help you to create deliberate and accurate alerting policies. See Alert 20 | Policies for more information. 21 | 22 | ### Alarms and Notifications 23 | When an alarm occurs on a monitored resource, Rackspace Cloud Monitoring sends 24 | you a notification so that you can take the appropriate action to either prevent 25 | an adverse situation from occurring or rectify a situation that has already 26 | occurred. These notifications are sent based on the severity of the alert as 27 | defined in the notification plan. 28 | 29 | ## Links 30 | 31 | [Documentation](http://docs.rackspace.com/cm/api/v1.0/cm-devguide/content/overview.html) 32 | 33 | ## Contact 34 | 35 | * IRC - #cloudmonitoring @ Freenode 36 | * Email - cmbeta [at] rackspace [dot] com 37 | -------------------------------------------------------------------------------- /reconnoiter/README.md: -------------------------------------------------------------------------------- 1 | Reconnoiter's goal is to better the world of monitoring by marrying fault 2 | detection and trending together. Through ease of configuration and ongoing 3 | maintenance, Reconnoiter encourages monitoring important technical metrics 4 | along side critical business metrics to improve awareness and ultimately 5 | accountability. 6 | 7 | https://labs.omniti.com/labs/reconnoiter 8 | -------------------------------------------------------------------------------- /redis-cluster-monitor/README.md: -------------------------------------------------------------------------------- 1 | 2 | [github](https://github.com/zealot2007/redis-cluster-monitor) 3 | 4 | Perhaps not ready for primetime, but for your consideration, this project's readme: 5 | 6 | --- 7 | 8 | UPDATE: please note that this is just a toy. A proper "redis-cluster" is on the 9 | official Redis roadmap. There's also the [twine 10 | project](http://github.com/alexgenaud/twine) to consider. 11 | 12 | --- 13 | 14 | Redis supports master-slave (1:N) replication but does not support *automatic* 15 | failover. That is, if the master "goes down" for any reason, your sysadmin 16 | (read: you) has to reconfigure one of the Redis slaves to be the new master. 17 | 18 | One could use monit or God or whatever alongside redis-cli to check if a host is 19 | up, then send the other hosts a SLAVEOF command to reconfigure the cluster 20 | around a new master. 21 | 22 | I created a Python script that does this instead. It only took an hour to do so 23 | no big loss. OK, I didn't think of using redis-cli initially :) 24 | 25 | Perhaps this project could at least be a part of the infrastructure (perhaps in 26 | concept only) for the forthcoming "redis-cluster" project. 27 | 28 | The [original mailing list thread](http://groups.google.com/group/redis-db/browse_thread/thread/497ee813c9960a50) 29 | discusses the origins of this project a bit. 30 | 31 | -------------------------------------------------------------------------------- /remote_syslog/README.md: -------------------------------------------------------------------------------- 1 | [link](http://github.com/papertrail/remote_syslog) 2 | -------------------------------------------------------------------------------- /resmon/README.md: -------------------------------------------------------------------------------- 1 | Resmon is a lightweight utility for local host monitoring that can be queried 2 | by tools such as nagios over http. One of the main design goals is portability: 3 | that resmon should require nothing more than a default install of Perl. Built 4 | with the philosophy that "we are smart because we are dumb," that is, local 5 | requirements should be minimal to ease deployment on multiple platforms. 6 | 7 | http://labs.omniti.com/labs/resmon 8 | -------------------------------------------------------------------------------- /response/README.md: -------------------------------------------------------------------------------- 1 | Response - Monitoring doesn't have to suck. 2 | 3 | Response is an simple Graphite proxy with plugable alerting support. It's first priority is to deliver messages to Graphite rapidly. In the event that Graphite goes down, messages will be buffered until Graphite is back. Eventually Redis will be optionally supported to provide arbitrary levels of durability/persistence 4 | 5 | 6 | https://github.com/gflarity/response 7 | -------------------------------------------------------------------------------- /restlos/README.md: -------------------------------------------------------------------------------- 1 | ## About 2 | 3 | [RESTlos] \(german for _completely_, _totally_\) is a generic [Nagios] api. Generic means, it can be used with 4 | every core that understands the nagios configuration syntax (for example icinga, shinken, etc). It provides a RESTful 5 | api for generating any standard nagios object, modify it or delete it. 6 | 7 | There are also some convenient functions for reloading the core (via command file) or verify the actual configuration 8 | via the REST interface. 9 | 10 | [link](https://github.com/Crapworks/RESTlos) 11 | -------------------------------------------------------------------------------- /riemann/README.md: -------------------------------------------------------------------------------- 1 | A network event stream processor with three years of private production use. Clojure and protobufs. 2 | 3 | [Riemann](https://github.com/aphyr/riemann) 4 | -------------------------------------------------------------------------------- /rivermuse/README.md: -------------------------------------------------------------------------------- 1 | 2 | Once touted as the ultimate opensource central event management and logging console. 3 | used to be vapourware for a long time .. 4 | 5 | 6 | 7 | RiverMuse CORE is an Open Source Fault and Event Management platform. 8 | 9 | 10 | 11 | 12 | http://www.rivermuse.com/ 13 | 14 | http://rivermuse.org/ 15 | -------------------------------------------------------------------------------- /rocksteady/README.md: -------------------------------------------------------------------------------- 1 | Rocksteady is a java application that reads metrics from RabbitMQ, parse them and turn them into events so Esper(CEP) can query against those metric and react to events match by the query. 2 | 3 | Rocksteady is an effort to utilize complex event process engine to analyze user defined metric. End goal is to derive root cause conclusion based on metric driven events. Rocksteady is only the metric analysis part of the whole picture, but we also present a solution including metric convention, metric sending, load balancing, and graphing that work well for us. 4 | 5 | http://code.google.com/p/rocksteady/ 6 | -------------------------------------------------------------------------------- /sensu/README.md: -------------------------------------------------------------------------------- 1 | [link]https://github.com/sensu/sensu 2 | 3 | Sensu is a ruby-based monitoring framework using Redis for data storage 4 | and RabbitMQ for communication. 5 | 6 | Created at http://sonian.com by @portertech and released as open source in 2011. 7 | 8 | https://github.com/sensu/sensu 9 | https://github.com/sensu/sensu-dashboard 10 | https://github.com/sensu/sensu-community-plugins 11 | -------------------------------------------------------------------------------- /servo/readme.md: -------------------------------------------------------------------------------- 1 | [link](https://github.com/Netflix/servo/wiki) 2 | 3 | The goal of Servo is to provide a simple interface for exposing and publishing application metrics in Java. 4 | 5 | The primary requirements are: 6 | 7 | + **Leverage JMX**: JMX is the standard monitoring interface for Java and can be queried by many existing tools. 8 | + **Keep it simple**: It should be trivial to expose metrics and publish metrics without having to write lots of code such as "MBean interfaces":http://docs.oracle.com/javase/tutorial/jmx/mbeans/standard.html. 9 | + **Flexible publishing**: Once metrics are exposed, it should be easy to regularly poll the metrics and make them available for internal reporting systems, logs, and services like "Amazon's CloudWatch":http://aws.amazon.com/cloudwatch/. 10 | -------------------------------------------------------------------------------- /seyren/README.md: -------------------------------------------------------------------------------- 1 | #Seyren 2 | 3 | [https://github.com/scobal/seyren](https://github.com/scobal/seyren) 4 | 5 | An alerting dashboard for Graphite 6 | 7 | 8 | -------------------------------------------------------------------------------- /shinken/README.md: -------------------------------------------------------------------------------- 1 | http://www.shinken-monitoring.org/ 2 | 3 | Nagios rewrite in Python. Lean and clean code base that is actually maintainable. 4 | 5 | Distributed architecture based on Pyro. Scalable while retaining the configuration aspects of Nagios. 6 | 7 | Can act as a conduit to send performance data to Graphite and PNP4Nagios. Graphite frontend integration. 8 | 9 | Modular nature permits integration and flexbility to any part of the system. 10 | 11 | 12 | 13 | 14 | 15 | 16 | -------------------------------------------------------------------------------- /skyline/README.md: -------------------------------------------------------------------------------- 1 | [skyline](https://github.com/etsy/skyline) - real-time anomaly detection system 2 | -------------------------------------------------------------------------------- /spm/README.md: -------------------------------------------------------------------------------- 1 | [Scalable Performance Monitoring 2 | (SPM)](http://sematext.com/spm/index.html) is the enterprise-class, 3 | cloud-based System/OS, JVM, and Application Performance Monitoring 4 | SaaS. 5 | 6 | Notable features: 7 | * rich graphs and charts 8 | * custom dashboards 9 | * custom metrics 10 | * slice and dice by time, server, and one or more application-specific 11 | dimensions at once 12 | * averages, sums, min, max, etc. 13 | * integrated alerts 14 | * integrated email report subscriptions 15 | * no loss of precision/granularity over time 16 | * multiple choices of metric granularity 17 | 18 | Currently, SPM has built-in detailed monitoring for: 19 | * [Apache Solr](http://sematext.com/spm/solr-performance-monitoring/index.html) 20 | * [ElasticSearch](http://sematext.com/spm/elasticsearch-performance-monitoring/index.html) 21 | * [Hadoop](http://sematext.com/spm/hadoop-performance-monitoring/index.html) 22 | * [HBase](http://sematext.com/spm/hbase-performance-monitoring/index.html) 23 | * [SenseiDB](http://sematext.com/spm/senseidb-performance-monitoring/index.html) 24 | * [Custom Metrics](https://sematext.atlassian.net/wiki/display/PUBSPM/Custom+Metrics) 25 | 26 | - http://github.com/sematext 27 | - http://twitter.com/sematext 28 | -------------------------------------------------------------------------------- /stajistics/README.md: -------------------------------------------------------------------------------- 1 | Stajistics is a free monitoring and runtime performance statistics collection API for Java. 2 | 3 | [link](http://code.google.com/p/stajistics/) 4 | -------------------------------------------------------------------------------- /statsd/README.md: -------------------------------------------------------------------------------- 1 | A network daemon for aggregating statistics (counters and timers), rolling them 2 | up, then sending them to graphite. 3 | 4 | - https://github.com/etsy/statsd 5 | - http://codeascraft.etsy.com/2011/02/15/measure-anything-measure-everything/ 6 | 7 | There is a wide variety of statsd-compatible servers written in almost every language. 8 | For additional statsd server implementations, see here: 9 | http://joemiller.me/2011/09/21/list-of-statsd-server-implementations/ -------------------------------------------------------------------------------- /storm/README.md: -------------------------------------------------------------------------------- 1 | Storm is a distributed realtime computation system. Similar to how Hadoop provides a set of general primitives for doing batch processing, Storm provides a set of general primitives for doing realtime computation. Storm is simple, can be used with any programming language, is used by many companies, and is a lot of fun to use! 2 | 3 | [https://github.com/nathanmarz/storm](https://github.com/nathanmarz/storm) 4 | -------------------------------------------------------------------------------- /sysdig/README.md: -------------------------------------------------------------------------------- 1 | [sysdig](https://github.com/draios/sysdig) - an open source system-level exploration and troubleshooting tool 2 | -------------------------------------------------------------------------------- /tacc_stats/README: -------------------------------------------------------------------------------- 1 | https://github.com/billbarth/tacc_stats 2 | -------------------------------------------------------------------------------- /tfsoa/README.md: -------------------------------------------------------------------------------- 1 | [link](https://github.com/sepulworld/tfsoa) 2 | 3 | ## Terraform State of Awareness Dashboard (tfsoa) 4 | 5 | A dashboard that helps centralize and monitor disparate [Terraform states](https://www.terraform.io/docs/state/) and relevant usage data across teams. 6 | Plus an admininstrator interface to view debug Terraform resource graph dependencies. 7 | -------------------------------------------------------------------------------- /vacuumetrix/README.md: -------------------------------------------------------------------------------- 1 | [link](http://github.com/99designs/vacuumetrix) 2 | 3 | Sucks up metrics from various external sources and puts the data into internal systems like Graphite and Ganglia. 4 | 5 | 6 | -------------------------------------------------------------------------------- /visage/README.md: -------------------------------------------------------------------------------- 1 | # Visage 2 | 3 | [Visage](https://github.com/auxesis/visage) is a web interface for viewing collectd statistics. 4 | 5 | It also provides a JSON interface onto collectd's RRD data, giving you an easy way to mash up the data. 6 | -------------------------------------------------------------------------------- /vowpal_wabbit/README.md: -------------------------------------------------------------------------------- 1 | This is a project started at Yahoo! Research and continuing at Microsoft Research to design a fast, scalable, useful learning algorithm. 2 | VW is the essence of speed in machine learning, able to learn from terafeature datasets with ease. Via parallel learning, it can exceed the throughput of any single machine network interface when doing linear learning, a first amongst learning algorithms. 3 | 4 | [https://github.com/JohnLangford/vowpal_wabbit](https://github.com/JohnLangford/vowpal_wabbit) 5 | 6 | -------------------------------------------------------------------------------- /xdmod/README: -------------------------------------------------------------------------------- 1 | Open XDMoD (XD Metrics on Demand) is an NSF-funded open source tool derived from XDMoD which was originally designed to audit and facilitate the utilization of the XSEDE cyberinfrastructure. Open XDMoD has been created to be functional in any HPC environment and provides a wide range of metrics on HPC resources, including resource utilization, resource performance, and impact on scholarship and research. The Open XDMoD framework is designed to meet the following objectives: (1) provide the user community with a tool to manage their allocations and optimize their resource utilization, (2) provide operational staff with the ability to monitor and tune resource performance, (3) provide management with a tool to monitor utilization, user base, and performance of resources, and (4) provide metrics to help measure scientific impact. 2 | 3 | http://sourceforge.net/projects/xdmod/ 4 | -------------------------------------------------------------------------------- /xymon/README.md: -------------------------------------------------------------------------------- 1 | 2 | 3 | 4 | Xymon is a system for monitoring of hosts and networks, inspired by the Big Brother system. It provides real-time monitoring, an easy web-interface, historical data, availability reports and performance graphs. Xymon was previously known as "Hobbit" 5 | 6 | 7 | 8 | https://www.xymon.com 9 | -------------------------------------------------------------------------------- /zabbix/README.md: -------------------------------------------------------------------------------- 1 | Zabbix is an enterprise-class open source distributed monitoring solution. 2 | 3 | http://www.zabbix.com/ 4 | -------------------------------------------------------------------------------- /zenoss/README.md: -------------------------------------------------------------------------------- 1 | 2 | http://www.zenoss.com/ 3 | --------------------------------------------------------------------------------