Search Results for "static code analysis"

Monolog sends your logs to files, sockets, inboxes, databases and various web services. See the complete list of handlers below. Special handlers allow you to build advanced logging strategies. This library implements the PSR-3 interface that you can type-hint against in your own libraries to keep a maximum of interoperability. You can also use it in your applications to make sure you can always use another compatible logger at a later time. As of 1.11.0 Monolog public APIs will also accept...

DBD2 inserts database records from TCP input. It is a companion project to Syslgod2 and an application in its own right. It ships with a backgrounding client for generic use. The client sends whatever information the user puts on the command-line to the back-end daemon via TCP. Upon successful transmission, the client exits. On failure, it backs off and retries until its life-time timer expires. The back-end daemon accepts data from Syslogd2 or its own client and inserts that data...

Autologging eliminates boilerplate logging setup code and tracing code, and provides a means to separate application logging from program flow and data tracing. Autologging provides two decorators and a custom log level: "autologging.logged" decorates a class to create a __log member. By default, the logger is named for the class's containing module and name (e.g. "my.module.ClassName").

Slogbase is a lightweight database attached to objects in Second Life that provides the same functionality as Apache Web Server logs. It uses ordinary LSL code in Second Life to send sensor data to an external PHP/MySQL application.

BASE is the Basic Analysis and Security Engine. It is based on the code from the Analysis Console for Intrusion Databases (ACID) project. This application provides a web front-end to query and analyze the alerts coming from a SNORT IDS system.

This project involves adding code to the Linux kernel to implement crash dumps for performing post-failure analysis of a kernel crash.