Projects tagged ‘log’ and ‘logger’

Octopussy is a solution to manage your logs (also frequently called a SIM/SEM/SIEM Solution). Basically, it stores your logs, produces reports, and raises alerts.

C++ Trivial Logger is a lightweight logger written in C++.

Network Logger is an application that write logs from network usage, that is, how many bytes was sent and received from your network interface. Useful when your internet provider restrict your network usage. More soon...

Log5F this is Logging Framework for Flash/Flex/AIR based application. It writen on ActionScript 3.0, during writing the code was analysed Log4J Logging Framework for Java. See http://log5f.wordpress.com

OverviewMinLog is a Java logging library. Key features: Low overhead Logging statements below a given level can be automatically removed by javac at compile time. Simple and efficient The API is ... [More] concise and very efficient at runtime. Extremely lightweight The entire project consists of one Java file with just over 100 non-comment lines of code. The JAR is 2.6kb (2kb with pack200). UsageMessages are logged using static methods: Log.info("Some message."); Log.debug("Error reading file: " + file, ex);A static import can be used to make the logging more concise: import static com.esotericsoftware.minlog.Log.*; // ... info("Some message."); debug("Error reading file: " + file, ex);While optional, for brevity the rest of this documentation assumes this static import is in place. If log statements from different libraries or areas of an application need to be differentiated, a category can be specified: info("some lib", "Some message."); debug("some lib", "Error reading file: " + file, ex);Log levelSetting the level will log that level, as well as all higher levels: Log.set(LEVEL_INFO);The levels are: LEVEL_NONE disables all logging. LEVEL_ERROR is for critical errors. The application may no longer work correctly. LEVEL_WARN is for important warnings. The application will continue to work correctly. LEVEL_INFO is for informative messages. Typically used for deployment. LEVEL_DEBUG is for debug messages. This level is useful during development. LEVEL_TRACE is for trace messages. A lot of information is logged, so this level is usually only needed when debugging a problem. Conditional loggingThe current log level can be checked before the message is logged: if (ERROR) error("Error reading file: " + file, ex); if (TRACE) { StringBuilder builder = new StringBuilder(); // Do work, append to the builder. trace(builder); }Checking the log level before calling the logging method is optional, but prevents unnecessary method calls and string concatenation for log levels that are disabled. Fixed logging levelsMinLog users can choose from the regular "minlog.jar" or from from a JAR file like "minlog-info.jar" which has a fixed logging level that cannot be changed at runtime (calls to Log.set() have no affect). During compilation, any conditional logging statements below the fixed level will be automatically optimized away by the Java compiler. Please see OverheadAndComparisons for more about the overhead when using MinLog with/without conditional logging and with/without a fixed logging level. The document also compares the MinLog overhead with log4j and java.util.logging. Output customizationThe default logger outputs messages in this format: time level: [category] messageWhere "time" is the time elapsed since the application started. For example: 00:00 TRACE: [kryo] Wrote string: moo 00:00 TRACE: [kryo] Wrote object: NonNullTestClass 00:01 TRACE: [kryo] Wrote string: this is some data 00:01 TRACE: [kryo] Compressed to 7.97% using: DeflateCompressor 00:12 TRACE: [kryo] Decompressed using: DeflateCompressor 00:12 TRACE: [kryo] Read string: this is some dataThe output can be customized: static public class MyLogger extends Logger { public void log (int level, String category, String message, Throwable ex) { StringBuilder builder = new StringBuilder(256); builder.append(new Date()); builder.append(' '); builder.append(level); builder.append('['); builder.append(category); builder.append("] "); builder.append(message); if (ex != null) { StringWriter writer = new StringWriter(256); ex.printStackTrace(new PrintWriter(writer)); builder.append('\n'); builder.append(writer.toString().trim()); } System.out.println(builder); } } // ... Log.set(new MyLogger());Using this mechanism, log messages can be filtered (eg, by category), written to a file, etc. [Less]

A small C++ logging libraryGetting StartedYou will need the boost library (at least 1.34.0) you can find it here. For help on how to compile boost: Getting Started. Once boost is compiled, you ... [More] can give it a try by compiling the examples Download the loglite using svn. Go into the folder gcc and follow the instructions supplied in the README file. You're done. Much more is possible thanks to Boost.IOStreams and Boost.Asio. Look at logging_test_iostream.cpp for an example of log compressed on the fly Look at logging_test_iostream_client.cpp and logging_test_iostream_server.cpp for logging through a network. More examples in the trunk Documentationhttp://loglite.googlecode.com/svn/trunk/doc/index.html An exampleSource code// loglite library logging_test_macro.cpp file -----------------------------// // (C) Copyright Jean-Daniel Michaud 2007. Permission to copy, use, modify, // sell and distribute this software is granted provided this copyright notice // appears in all copies. This software is provided "as is" without express or // implied warranty, and with no claim as to its suitability for any purpose. // See http://www.boost.org/LICENSE_1_0.txt for licensing. // See http://code.google.com/p/loglite/ for library home page. #include #include int infinite_loop() { LOGLITE_LOG_L1("oops..."); while (1) ; } int foo() { LOGLITE_LOG_(1, "foo called"); return 7; } int main(int argc, char **argv) { // Define the format of your log LOGLITE_INIT(("[" >> loglite::mask >> "]," >> loglite::filename >> "(" >> loglite::line >> ")," >> loglite::time >> "," >> loglite::trace >> loglite::eol)); // log format // All the logs below level 3 should sink in ./test_macro.log loglite::sink s1(new std::ofstream("./test_macro.log"), LOGLITE_MASK_LEVEL_2); // The sink will only handle the log qualifier s1.attach_qualifier(loglite::log); LOGLITE_ADD_OUTPUT_STREAM(s1); // All the logs below 3 should sink on the standard output loglite::sink s2(&std::cout, LOGLITE_MASK_LEVEL_2); // The sink will only handle the log qualifier s2.attach_qualifier(loglite::log); LOGLITE_ADD_OUTPUT_STREAM(s2); LOGLITE_LOG(LOGLITE_LEVEL_1, loglite::log, "something"); LOGLITE_LOG_L2("something else"); // A log of level 2 (L2) // Logs are not evaluated if no sink is configured to use them LOGLITE_LOG_(LOGLITE_LEVEL_3, "If you evaluate me you die!" << infinite_loop()); char you_want[256] = "you want"; LOGLITE_LOG_(LOGLITE_LEVEL_1, "Let's say " << you_want << " to display " << 2); LOGLITE_LOG_(LOGLITE_LEVEL_1, "foo will be evaluated: " << foo()); return 0; }Output[1],logging_test_macro.cpp(43),2007-Aug-24 07:36:33.858844,something [2],logging_test_macro.cpp(44),2007-Aug-24 07:36:33.858844,something else [1],logging_test_macro.cpp(47),2007-Aug-24 07:36:33.858844,Let's say you want to display 2 [1],logging_test_macro.cpp(21),2007-Aug-24 07:36:33.874469,foo called [1],logging_test_macro.cpp(48),2007-Aug-24 07:36:33.874469,foo will be evaluated: 7 [Less]

Highly customizable and interactive Eclipse plug-in to view log files. Current featuresCustomizable output styles Create different styles for groups and elements Quick output clear (double-clicking ... [More] the area) Filter output by input text Please refer to the Wiki for installation and usage instructions. [Less]

Primary Goals of Log Head: 1: Create a free, feature rich logging utility in AIR that can connect with flash. 2: Provide tools to quickly isolate and share desired traces. 3: Have tools be modular ... [More] and easily extensible 4: Provide work around for issue where AIR applications block flash traces when running [Less]

rosy.js --- javascript library (Logging and Command console)Loggingusual useInclude rosy.js like this in your page. And use rosy log window like this. var rlog = new RosyLog(); rlog.use = true; ... [More] rlog.debug('hoge'); rlog.d('h');If you select "rlog.use = true " ,you will see rosy log window then your javascript code is executed. bookmarkletLet's use rosy log window bookmarklet. http://dev.chrisryu.com/data/rosy/bookmarklet.html In this page, you can resist rosy log window bookmarklet. and please execute this bookmarklet in any page. you can use rosy log console, which can execute javascript in that page. [Less]

A simple Logging Library for .NET 3.5.