Loggerz- A .Net Error Logging framework

  •        52

A new and hopefully exciting error logging framework that will integrate nicely into any windows/web application.




Related Projects

quiver-log - Logging utility for dart modeled on log4j/logback

Quiver log is a set of logging utilities that make it easy to configure and manage Dart's built in logging capabilities.Dart's built-in logging utilities are fairly low level. This means each time you start a new project you have to copy/paste a bunch of logging configuration code to setup output locations and logging formats. Quiver-log provides a set of higher-level abstractions to make it easier to get logging setup correctly. Specifically, there are two new concepts: appender and formatter. Appenders define output locations like the console, http or even in-memory data structures that can store logs. Formatters, as the name implies, allow for custom logging formats.

funnel - A minimalistic 12 factor log router written in Go

The 12 factor rule for logging says that an app "should not attempt to write to or manage logfiles. Instead, each running process writes its event stream, unbuffered, to stdout." The execution environment should take care of capturing the logs and perform further processing with it. Funnel is this "execution environment".All you have to do from your app is to print your log line to stdout, and pipe it to funnel. You can still use any logging library inside your app to handle other stuff like log level, structured logging etc. But don't bother about the log destination. Let funnel take care whether you want to just write to files or stream your output to Kafka. Think of it as a fluentd/logstash replacement(with minimal features!) but having only stdin as an input.

tinylog - tinylog is a lightweight logging framework for Java and Android.

tinylog is a lightweight open-source logging framework for Java and Android, optimized for ease of use. The logger of tinylog is static, so it isn't necessary to create an instance of the logger before logging. By default all log entries of the level info or higher are written to the console.


A small logging library for Objective-C applications (Mac OS X and iPhone OS/iOS) which provides conditional logging based on log levels and log components. Additionally, different logging strategies can be used, e.g. writing log messages to a file or sending them to the system log, while using the same logging interface.

exlog - Tool to keep a logbook. For example a personal log, exercise log or travel log.

Tool to keep a logbook. For example a personal log, exercise log or travel log.

log - Structured logging package for Go.

Package log implements a simple structured logging API inspired by Logrus, designed with centralization in mind. Read more on Medium.

sawbuck - Automatically exported from code.google.com/p/sawbuck

Sawbuck is a log viewer and controller for Windows Chrome logging, and for other applications or plugins that use the logging facility in Chrome base.Logging in Chrome is integrated with Event Tracing for Windows (ETW), which allows ETW controllers like Sawbuck to control log verbosity at runtime. The Chrome logging integration also captures the call stack at the logging site, which can then be resolved and displayed by log viewers such as Sawbuck.

Sentry - Realtime Platform-Agnostic Error Logging and Aggregation platform

Sentry is a realtime event logging and aggregation platform. It specializes in monitoring errors and extracting all the information needed to do a proper post-mortem without any of the hassle of the standard user feedback loop.

McKinsey - Technical Intern Exercise Code Challenge

Technical Intern Exercise Code Challenge

tech-ex - technical exercise

technical exercise

slf4j - Simple Logging Facade for Java

The Simple Logging Facade for Java (SLF4J) serves as a simple facade or abstraction for various logging frameworks (e.g. java.util.logging, logback, log4j) allowing the end user to plug in the desired logging framework at deployment time.

logging - A Dart package for debug and error logging.

By default, the logging package does not do anything useful with the log messages. You must configure the logging level and add a handler for the log messages.Here is a simple logging configuration that logs all messages via print.

SharePoint Logging Library By Ayman El-Hattab

This library helps you writing code that incorporates logging to SharePoint logs. Writing to the same trace log alleviates the need for developers to log their development information in other places such as the Windows Event Log which is commonly used by system administrators.

log - :green_book: Simple, configurable and scalable Structured Logging for Go.

There's allot of great stuff out there, but also thought a log library could be made easier to use, more efficient by reusing objects and more performant using channels.DebugLevel - Info useful to developers for debugging the application, not useful during operations.

log - Logging packages for Go

You are more than welcome to ask questions on the Go mailing-list and open issues here if you find bugs.Package stdlog provides simple and fast logging to the standard output (stdout) and is optimized for programs launched via a shell or cron. It can also be used to log to a file by redirecting the standard output to a file. This package is thread-safe.

NLog - Advanced .NET Logging

NLog is a logging platform for .NET with rich log routing and management capabilities. It uses familar logger pattern known from log4xxx. NLog is very easy to use and configure. Advanced routing options include buffering, asynchronous logging, load balancing, failover, and more.

mlog - A simple logging module for go, with a rotating file feature and console logging.

A simple logging module for go, with a rotating file feature and console logging.By default, the log will be rolled over to a backup file when its size reaches 10Mb and 10 such files will be created (and eventually reused).

Logrus - Structured, pluggable logging for Go.

Logrus is a structured logger for Go (golang), completely API compatible with the standard library logger. There is a support to add hooks for logging levels. For example to send errors to an exception tracking service on Error, Fatal and Panic, info to StatsD or log to multiple places simultaneously, e.g. syslog.