A powerful and intelligent log processing tool written in Go
Find a file
dependabot[bot] 15e778b665
Bump github/codeql-action from 3.26.7 to 3.26.8
Bumps [github/codeql-action](https://github.com/github/codeql-action) from 3.26.7 to 3.26.8.
- [Release notes](https://github.com/github/codeql-action/releases)
- [Changelog](https://github.com/github/codeql-action/blob/main/CHANGELOG.md)
- [Commits](8214744c54...294a9d9291)

---
updated-dependencies:
- dependency-name: github/codeql-action
  dependency-type: direct:production
  update-type: version-update:semver-patch
...

Signed-off-by: dependabot[bot] <support@github.com>
2024-09-20 08:52:13 +00:00
.github Bump github/codeql-action from 3.26.7 to 3.26.8 2024-09-20 08:52:13 +00:00
.idea Add SPDX license identifiers and update copyright year 2023-12-15 16:35:41 +01:00
cmd/server Refactor variable names for improved code readability 2024-03-21 20:22:33 +01:00
etc Relocate logranger.toml and update .gitignore 2023-12-21 20:17:10 +01:00
LICENSES Add CC0-1.0 license and update workflow files 2024-03-21 16:02:13 +01:00
plugins Refactor variable names for improved code readability 2024-03-21 20:22:33 +01:00
support-files Add SPDX license headers to support-files 2023-12-27 18:29:36 +01:00
template Refactor variable names for improved code readability 2024-03-21 20:22:33 +01:00
.gitignore Add more pattern to .gitignore 2023-12-22 17:31:28 +01:00
.golangci.toml Update Go version in .golangci.toml 2024-02-08 16:16:03 +01:00
config.go Refactor variable names for improved code readability 2024-03-21 20:22:33 +01:00
connection.go Refactor variable names for improved code readability 2024-03-21 20:22:33 +01:00
Dockerfile Bump golang from fae53d4 to ac67716 2024-09-09 08:13:39 +00:00
error.go Correct typo in error.go comments 2023-12-22 16:08:02 +01:00
go.mod Update project references to use GitHub repository 2024-03-21 15:39:31 +01:00
go.sum Update go-parsesyslog dependency and refine server connection handling 2023-12-22 15:24:58 +01:00
go.sum.license Add SPDX license details to go.sum.license 2023-12-15 17:41:15 +01:00
LICENSE Initial commit 2023-12-08 14:31:37 +01:00
listener.go Refactor variable names for improved code readability 2024-03-21 20:22:33 +01:00
README.md Update project references to use GitHub repository 2024-03-21 15:39:31 +01:00
rule.go Refactor variable names for improved code readability 2024-03-21 20:22:33 +01:00
SECURITY.md Update project names in SECURITY.md 2024-03-21 20:26:20 +01:00
server.go Refactor variable names for improved code readability 2024-03-21 20:22:33 +01:00
sonar-project.properties Add SPDX license identifiers and update copyright year 2023-12-15 16:35:41 +01:00

Logranger

GoDoc Go Report Card #logranger on Discord REUSE status buy ma a coffee

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.