Search Results for "termanal only linux"

Flogger is a structured logging API for Java that decouples how you log from where logs ultimately go, making it easy to change backends without rewriting application code. Instead of building messages eagerly, it uses lazy parameter evaluation so expensive string building only happens when a log statement is actually emitted. The API encourages structured key–value context and fine-grained rate limiting, which helps keep logs informative without flooding systems during high-traffic or error...

MBM-Log allows to look deeply in collected logs (not only Top 10). All charts are generated on demand. You can easily filter data. MBM-Log can help you with FortiGate diagnostics via SSH (built in commands) Java GUI application.

This is a web application, using thing application user can see the log file with multiple search critria. This application supports Log4J and log4Net. This tool is used to filter the log file, based on multiple criteria. Admin user can configure multiple applications and group the application up to three levels. Application name will be displayed in tree structure based upon grouping. Application will be displayed based on roles. System will allow the user to filter the log file not...

LogsGrep is a unique, grep-like utility designed specifically to target log files containing multi-line entries. The primary target is Java log files (Log4J, common, ...), where it is very common to have multiline log entries (for example log entries with a stacktrace). It follows Unix philosophy, does only its primary job and expects its input to be generated by other more advanced tools (tail, cat, type, find...); There is no goal to be compatible with Unix grep. LogsGrep is...

Another logging framework for Java. I try to balance flexibility, usabilty and performance using OOP. Currently the framework is usable but it lacks a lot of functionality.

An open source data version repository model based on true INSERT only logic. Contains high performance support for data versioning and history. Enables point-in-time query and CDC sourcing including mapping each change to a transaction.

J2ME logging framework intended to be used at development time. It is only CLDC 1.1 complied. It is simple, flexible and extensible. It supports different way of formating and displaying logging information.

GILoT is an interpreting and formatting log tail:er. As each log entry is matched and formatted against customizeable rules, only relevant data is parsed. GILoT features, atm, two separate user interfaces, a console UI and an ncurses/charva TUI.

Yet another logger. Take a close look at it: It is very easy to use, very unified and extendable. You may attach your favourite set of loggers to this logger, and you still use only one API! This Java logger is used throughout the COMJAT.NET systems.

With Log4J and the Java logging framework being floodgate-based, I personally still see the need for a bit-masked logging framework, where you not only have categories but actual event types instead of event levels. This will be that framework.