Windows Event Log Manager

  •        55

Windows Event Log Manager is a tool for creating, editing, and viewing windows event logs.



Related Projects

Event Log Analyzer

Event Log Analyzer is a simple yet powerful tool to analyze event logs in Windows. It has features to group similar events together, give graphical view of distribution of events over time and in similarity. It is developed in C# and WPF and uses MVVM framework.

PowerShell EventLogWatcher Module

A PowerShell module that provides some additional functions to enhance PowerShell Eventing in relation to Windows Event Log events. Subscriptions can be made and actions taken when new events are written to a log. In a sense, this can be used as "poor mans" auditing system.

logberry - A structured logging package for Go services & applications.

Most log output libraries fall into one of two camps: * Super simple, with a global API that's really easy to use but has no structure beyond a component label and message level or type; * More complex, but focused on extensive formatting controls and/or various output serializers, pipes, aggregators, and managers.Logberry is a bit different, and places more focus on *what* you'relogging, rather than *how*. At the core, its log events are basedaround key/value pairs rather than arbitrary st

snapshot-reduce - Incrementally reduce an event-log into a snapshot view of those events

Incrementally reduce an event-log into a snapshot view of those events

100Projects - 100 Projects to be completed, for me its in Python

**Mp3 Tagger** – Modify and add ID3v1 tags to MP3 files. See if you can also add in the album art into the MP3 file’s header as well as other ID3v2 tags.**Log File Maker** – Make an application which logs various statistics in response to given events. This can be something that logs what an application does, what the system is doing, when something like a file changes etc.**Excel Spreadsheet Exporter** – Create an online application which can read in a file and create an Excel Spreadshe

Event Log Mailer

Mails events from Windows' system Event Log which matches rules in configuration. Runs as Windows service and has super simple configuration

atomic-store - Atomic event store for Scala/Akka

Atomic Store is a system for managing persistent streams of atomic events, with strict consistency. It is intended for systems in which only one event can be admitted to a canonical event log at a time, contingent upon past events. It exists to maintain the atomicity of handling of incoming events, but outsources the actual validation logic back to the event originator. In a sense, the idea here is to do as little as possible to meet this goal, but in a way that is as practical as possible.Atomic Store is built on top of Akka Persistence, which is designed to natively support highly scalable distributed systems with relaxed consistency. A distributed system can maximize its scalability by reducing coupling between its components, and synchronization of state changes is one such coupling. The general approach to relaxed consistency is to take compensatory actions to rectify inconsistencies between distributed components, in retrospect. But this is complex, and not desirable in all situations. Atomic Store is designed for situations where strict consistency is more desirable or appropriate than extreme scalability.

count-min-log - Go implementation of Count-Min-Log

Count-Min Sketch is a widely adopted algorithm for approximate event counting in large scale processing. However, the original version of the Count-Min-Sketch (CMS) suffers of some deficiences, especially if one is interested in the low-frequency items, such as in text- mining related tasks. Several variants of CMS have been proposed to compensate for the high relative error for low-frequency events, but the proposed solutions tend to correct the errors instead of preventing them. In this paper, we propose the Count-Min-Log sketch, which uses logarithm-based, approximate counters instead of linear counters to improve the average relative error of CMS at constant memory footprint.This version implements the 16 bit register version. Will add back the 8-bit version soon.

windows-event-forwarding - A repository for using windows event forwarding for incident detection and response

Over the past few years, Palantir has a maintained an internal Windows Event Forwarding (WEF) pipeline for generating and centrally collecting logs of forensic and security value from Microsoft Windows hosts. Once these events are collected and indexed, alerting and detection strategies (ADS) can be constructed not only on high-fidelity security events (e.g. log deletion), but also for deviations from normalcy, such as unusual service account access, access to sensitive filesystem or registry locations, or installation of malware persistence.The goal of this project is to provide the necessary building blocks for organizations to rapidly evaluate and deploy WEF to a production environment, and centralize public efforts to improve WEF subscriptions and encourage adoption. While WEF has become more popular in recent years, it is still dramatically underrepresented in the community, and it is our hope that this project may encourage others to adopt it for incident detection and response purposes. We acknowledge the efforts that Microsoft, IAD, and other contributors have made to this space and wish to thank them for providing many of the subscriptions, ideas, and techniques that will be covered in this post.

serilog-sinks-eventlog - A Serilog sink that writes events to the Windows Event Log

A Serilog sink that writes events to the Windows Event Log.Important: version 3.0 of this sink changed the default value of manageEventSource from true to false. Applications that run with administrative priviliges, and that can therefore create event sources on-the-fly, can opt-in by providing manageEventSource: true as a configuration option.


SOAP service for Windows Event log - eventcreateservice.php (ECS) is a simple SOAP service which uses eventcreatef.exe by Florian Weinert ( Every incoming SOAP message will be passed through to eventcreatef.exe which will write the log message to a Windows 2003/XP event log. With ECS and eventcreatef.exe you can log any event to a an eventlog of central Windows machine without Syslogd running.

SSIS Event Log Business Intelligence

The SSIS Event Log Business Intelligence package is a complete BI project focused around SSIS Event Log data. Components include: - 9 SSRS Reports - ETL Data Mart - SSIS packages to load ETL Data Mart - Analysis Services Cube - PerformancePoint Dashboard


Emit rotate events for log files based on interval. Rotate event handlers are called "rotator-tots" or just tots. Tots get passed a (readable stream, the log file path, and the data passed in when the log was asociated).

jqm-event-logger - A simple RequireJS module to log JQuery Mobile page events to console.

A simple RequireJS module to log JQuery Mobile page events to console.

Chainsaw - log viewer and analysis tool

Chainsaw is a companion application to Log4j written by members of the Log4j development community. Chainsaw can read log files formatted in Log4j's XMLLayout, receive events from remote locations, read events from a DB, it can even work with the JDK 1.4 logging events.

Zenoss - Open Source IT Management

Zenoss Core is an open source IT monitoring product that delivers the functionality to effectively manage the configuration, health, performance of networks, servers and applications through a single, integrated software package.

Meniscus - The Python Event Logging Service

Meniscus is a Python based system for event collection, transit and processing in the large. It's primary use case is for large-scale Cloud logging, but can be used in many other scenarios including usage reporting and API tracing. Its components include Collection, Transport, Storage, Event Processing & Enhancement, Complex Event Processing, Analytics.

serilog-sinks-rollingfile - Write log events to a set of rolling log files

Writes Serilog events to a set of text files, one per day.Important: By default, only one process may write to a log file at a given time. See Shared log files below for information on multi-process sharing.

Improved Dnn Event Log Email Notification provider

The email notifications for log events in Dnn are poor. This project aims to improve them through a new logging provider. The initial work uses the existing logging provider and just overrides the SendLogNotifications method. Over time hopefully this will be improved to enh...