Ukadc.Diagnostics

  •        60

The idea behind this project was to provide a framework that uses the inbuilt features of the System.Diagnostics namespace, and show how logging and tracing can be integrated into a client application whilst taking advantage of the services exposed by System.Diagnostics. There...

http://ukadcdiagnostics.codeplex.com/

Tags
Implementation
License
Platform

   




Related Projects

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.

AgileDesign Utilities Library


This library provides common functionality usable for most software projects: Logger - Asynchronous logging wrapper on top of new Microsoft logging class TraceSource with simplified API NameOf - Avoid using string names using static reflection Left(), Right() and No...

Essential Diagnostics


Using and extending System.Diagnostics trace logging. This project uses the inbuilt features of the System.Diagnostics namespace, and shows how logging and tracing can be integrated into a client application whilst taking advantage of the services exposed by System.Diagnostics.

fsharplu - This library provides a set of F# helpers for string manipulations, logging, collection data structures, file operations, text processing, security, async, parsing, diagnostics, configuration files and Json serialization


This library provides F# lightweight utilities for string manipulations, logging, collection data structures, file operations, text processing, security, async, parsing, diagnostics, configuration files and Json serialization.This is by no means a full-fledged utility library for F#, but rather a small collection of utilities and other thin wrappers accumulated throughout the development of various internal projects at Microsoft and meant to facilitate development with the .Net framework using the F# programming language.



go-spew - Implements a deep pretty printer for Go data structures to aid in debugging


Go-spew implements a deep pretty printer for Go data structures to aid in debugging. A comprehensive suite of tests with 100% test coverage is provided to ensure proper functionality. See test_coverage.txt for the gocov coverage report. Go-spew is licensed under the liberal ISC license, so it may be used in open source or commercial projects.If you're interested in reading about how this package came to life and some of the challenges involved in providing a deep pretty printer, there is a blog post about it here.

Log2Console - A Generic Log Viewer (for Log4Net, NLog...)


Log2Console is a development tool offering a nice UI to display, filter and search log messages from different logging services: Log4Net, Log4j and NLog. It can directly receive log events locally or remotely, or read them from a log file... It is written with C#.

ruby-kafka - A Ruby client library for Apache Kafka


A Ruby client library for Apache Kafka, a distributed log and message bus. The focus of this library will be operational simplicity, with good logging and metrics that can make debugging issues easier.Although parts of this library work with Kafka 0.8 – specifically, the Producer API – it's being tested and developed against Kafka 0.9. The Consumer API is Kafka 0.9+ only.

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.

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.

node-comment-macros - JavaScript comment macros useful for injecting logging, tracing, debugging, or stats related code


Node / JavaScript comment macros useful for injecting logging, tracing, debugging, or stats related code.I wouldn't recommend this at the library level, normally even at the application level I wouldn't recommend it, but some of our projects require a lot of logging and metrics, so this helps cut the clutter.

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.

LibComponentLogging-Core


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.

TracerX Logger/Viewer for .NET


TracerX is a .NET logger with a powerful viewer that supports filtering/coloring by threads, category, trace level, and more. Output can go to a circular log file, event log, console/command window, or Trace.WriteLine(). The viewer can collapse and expand method calls, view/walk

node-diagnostics - Logging and Timer to perform some basic profiling and diagnostics


Logging and Timer to perform some basic profiling and diagnostics

Visual Log Parser


Visual LogParser GUI is a free Visual tool for the Microsoft LogParser engine. It enable user to query any log files or data source with an advanced SQL syntax. Visual LogParser offer an dockable MDI interface, color syntax hightlighting, customisation of the log source pro...

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 - 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.