Muse Proxy is a highly customizable multi-platform proxy server. It is easy to use and configure, acting successfully as a gateway to authenticated restricted content, rewriting Web server, Web Access Management, proxy server, and reverse proxy. It has been used for more than 10 years within the Muse Federated Search Platform to manage the authentication to resources and the navigation to full text, by restoring the server session on the end-user browser.
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.
Monitoring::Spooler is a handy queue manager for queueing and delivery of monitoring notifications. It is able to handle several groups of on-call personnel and provides an extensible plugin mechanism to connect it to virtually any remote service which provides some kind of API. It is designed to work nicely with App::Standby.
SpurTracer is a push-notification based monitoring solution for heterogenous loosely coupled IT infrastructures. It complements a service-endpoint monitoring solution like Nagios with a component-level interface auto-discovery. It automatically provides a certain level of functional tracing along with many non-functional measurements (e.g. call, error and timeout rates, interface latency, component execution, etc.). While being zero config itself, SpurTracer relies on you adding push notification support to the components you want to monitor. The best way to use SpurTracer is by adding punctual tracing to components in your infrastructure on-demand.