360-FAAR (Firewall Analysis Audit and Repair) is an offline, command line, Perl firewall policy manipulation tool to filter, compare to logs, merge, translate, and output firewall commands for new policies, in Checkpoint dbedit, Cisco ASA, or ScreenOS commands. It is all contained in one file. It can read policy and logs for: Checkpoint FW1 (in odumper.csv / logexport format), Netscreen ScreenOS (in get config / syslog format), and Cisco ASA (show run / syslog format). It uses both inclusive and exclusive CIDR and text filters, permitting you to split large policies into smaller ones for virutalization at the same time as removing unused connectivity. It supports policy to log association, object translation, rulebase reordering and simplification, rule moves, and duplicate matching automatically. It allows you to seamlessly move rules to where you need them. 'print' mode creates a spreadsheet for your audit needs with one command.
LPAR2RRD makes historical, future trends and nearly "realtime" CPU utilization graphs of LPARs and shared CPU usage of IBM Power servers. It collects complete physical and logical configuration of all servers/LPARs. It is agent-less (it gets everything from the HMC/SDMC or IVM). It supports all kinds of logical partitions (AIX/AS400/Linux/VIOS).
Check_MK is a complex addon for Nagios/Icinga and consists of three subprojects. The check and inventory system Check_MK is a general purpose Nagios plugin for retrieving data. It adopts a new approach for collecting data and obsoletes NRPE, check_by_ssh, NSClient, and check_snmp. It features a significant reduction of CPU use on the Nagios host and automatic inventory of items to be checked, and is especially useful with larger Nagios installations. "MK Livestatus" gives immediate and fast access to live and historic Nagios status data. It's a supported backend for many addons including NagVis, NagiosBP, and Thruk. "Check_MK Multisite" is a feature complete replacement for the Nagios GUI, and uses MK Livestatus as a backend. It is very fast, and supports efficient distributed monitoring.
Nagstamon is a Nagios status monitor with a UI that resides in the systray or as a floating statusbar on your desktop. It informs you in realtime about the status of your Nagios, Icinga, Opsview, Ninja, Check_MK/Multisite, Centreon, or Thruk-monitored network. It alerts you with sound and visual notification. Failed hosts and services are easy to connect with by SSH, RDP, and VNC. Custom actions can be run on certain events. It works best with GNOME, but also with KDE, Mac OS X, and Windows.
Jmx4Perl provides an alternate way of accessing Java JEE Server management interfaces that are based on JMX (Java Management Extensions). It is an agent-based approach where a small Web application deployed on the application server provides HTTP/JSON-based access to JMX MBeans registered within the application server. It is set up from a handful of Perl modules, which can be integrated seamlessly in your own programs. It also includes a Nagios plugin, check_jmx4perl, a jmx4perl command line tool for remote JMX queries and operations, and a readline-based JMX shell j4psh, with context sensitive command completion and syntax highlighting.
The NSCA-ng package provides a client-server pair which makes the Nagios command pipe accessible to remote systems, with per-client passwords and fine-grained authorization control. This allows for submission of passive check results, downtimes, and many other commands to Nagios (or compatible monitoring solutions). Check results of arbitrary size and multiline plugin output are supported.
Flawless traps exceptions and then uses git blame to send an email to the developer who wrote the buggy code. Even if a particular line of code causes thousands of exceptions, only one email will be sent. It uses git-blame to figure out which developer is responsible for a particular exception, and will only email that developer. If you set report_only_after_minimum_date, then Flawless will only report exceptions caused by code modified after report_only_after_minimum_date. You can mark certain files/functions as library code, and when an exception originates in those files/functions, the caller will be blamed for the error instead of the library code.