mirror of
https://github.com/wneessen/logranger.git
synced 2024-11-21 20:30:49 +01:00
A powerful and intelligent log processing tool written in Go
bae472502c
Bumps [docker/metadata-action](https://github.com/docker/metadata-action) from 5.5.1 to 5.6.1.
- [Release notes](https://github.com/docker/metadata-action/releases)
- [Commits](
|
||
---|---|---|
.github | ||
.idea | ||
cmd/server | ||
etc | ||
LICENSES | ||
plugins | ||
support-files | ||
template | ||
.gitignore | ||
.golangci.toml | ||
config.go | ||
connection.go | ||
Dockerfile | ||
error.go | ||
go.mod | ||
go.sum | ||
go.sum.license | ||
LICENSE | ||
listener.go | ||
README.md | ||
rule.go | ||
SECURITY.md | ||
server.go | ||
sonar-project.properties |
Logranger
Note: Logranger is still WIP
Introduction
Logranger is a powerful and intelligent log processing tool written in Go. Its main purpose is to efficiently process a large number of incoming syslog messages, enabling you filter for specific events and perform actions based on the received events.
Features
- Efficient log processing: Logranger is based on the performand go-parsesyslog package and can handle and analyze large volumes of syslog messages without compromising on its speed or performance.
- Powerful rule-based filtering: You can filter for log events based on a rules that specify regular expressions to match the events.
- Customization: Logranger is easily customizable. Its easy to implement plugin interface allows you to write your own plugins to perform custom actions with your events.
- Custom templates: Matched (or sub-matched) event log messages can be processed using Go's versatile templating language.
Plugins
By default Logranger ships with a varity of action plugins:
- File action: Store the matched (or a sub-match) event log messages in a file. The file can be used in overwrite or append mode.
License
Logranger is released under the MIT License.
Support
If you encounter any problems while using Logranger, please create an issue in this repository. We appreciate any feedback or suggestions for improving Logranger.