Zorka is a sophisticated programmable profiling/monitoring agent for Java suitable for running with production applications. The agent integrates seamlessly with popular monitoring systems and protocols (Zabbix, Nagios, syslog, SNMP) and offers additional tracing/profiling capabilities that - along with the accompanying data collector - help with spotting performance issues and general problems. The agent also exposes JMX data to conventional monitoring systems. Platforms (more or less) supported out of the box include: JBoss 4/5/6/7, Wildfly 8, Tomcat 6/7/8, Jetty 6/7/8/9, Websphere, Weblogic, GlassFish 4.0, WSO2 ESB, Mule ESB, and Jasig CAS. There is also dedicated support for the popular Java libraries Spring, Quartz, CXF, and Axis 1.x. The agent should run on most other platforms with limited functionalities (that is, lack of support for platform-specific features). It works with JDK6, JDK7, and JDK8. JDK5 support is also possible after preprocessing the agent binary with retrotranslator. Functionality can be easily added by implementing simple BSH scripts.
Pandora FMS is a software-monitoring tool created for all kinds of companies. It is specially designed for large environments, and works by first managing servers, applications, and communications, and then notifying clients of problems and failures before they occur. Pandora FMS also includes a configurable report system that evaluates and notifies the client on the level of fulfillment and compliance of their systems. It supports all kinds of technologies unifying the management tools of your system, such as performance monitoring, network monitoring, and availability management. Pandora FMS makes your company management more agile and improves your process performance.
PHP Server Monitor is a script that checks whether the servers/Websites on your list are running. Each server has its own notification settings. Notifications are made via email or text messages. Using the Web-based interface, you can add servers and manage users for each server.
STOR2RRD provides storage performance and capacity monitoring for IBM DS8000, IBM Storwize, and IBM SVC. It generates historical, future trends, and nearly "realtime" performance utilization graphs of monitored storages. It graphically presents the IO rate, data throughput, and response times for all Ports, Pools, Ranks, Mdisks, Volumes (LUNs), and drives. It collects complete physical and logical configuration of all storages.
Upsilon is a distributed, flexible, and extensible system monitoring application. Being distributed means you run service checks on Upsilon nodes in your network where it makes sense, either on every server or on a management network, inside or outside the firewall. You can run checks on secure, hard to reach networks, and push those results to a central server. You can optionally execute "agentless" checks just by using SSH. Being flexible means that if you can script it, you can monitor it. Unlike most monitoring systems, the monitoring scripts are external to the main server, so you can use Upsilon to execute your monitoring scripts in an extremely robust way. Upsilon has been used to monitor many different things and is API-compatible with all nagios monitoring scripts. Being extensible means you can add monitoring checks to Upsilon at runtime without needing to restart the server. The upsilon-node and upsilon-web projects both have their own REST APIs.
nxgipd is a monitoring daemon for UTC / GE Interlogix / Caddx alarm systems that use the Networx NX-584 protocol. Supported alarm systems and panels include the NX-8, NX-8V2, and NX-8E. The daemon process requires minimal memory and CPU resources. It continuously monitors the alarm panel and logs any activity into local log file and/or to syslog. The nxstat program can be used to query panel status in real-time. It typically requires a NX-584E (home automation) module or for the built-in serial port to be enabled (NX-8E panel).
jWatchdog delivers a simple watchdog to actively monitor your infrastructure and send you notifications in case something goes wrong. It is configured using a simple XML configuration file. This configuration file can be changed on-the-fly without a need to restart the watchdog. jWatchdog does not offer data collection itself. It assumes that you already collected the data on which you want to run jWatchdog. The de facto standard tool Collectd is recommended for data collection. jWatchdog assumes that you use the RRDTool collectd output plugin to store the collected data in RRD files, or use Graphite as a datasource.