openshift/eventrouter

A simple introspective kubernetes service that forwards events to a specified sink.

View on GitHub ↗Jump to charts ↓

Data as of . Signed-in members get hourly updates — create a free account.

Summary Information

Updated 24 minutes ago
Added to GitGenius on June 23rd, 2023
Created on September 5th, 2017
Open Issues & Pull Requests: 1 (+0)
GitHub issues: Disabled - open counts may still include pull requests.
Number of forks: 42
Total Stargazers: 68 (+0)
Total Subscribers: 178 (+0)

Repository Insights (GitGenius)

Most active contributors

Sign in to see contributor activity.
Sign in

Related repositories by overlapping contributors

No overlapping-contributor repos identified yet.

Charts & Analytics

Fetching additional details & charts...

Issue Activity (beta)

GitHub issues are disabled for this repository, so issue analytics and the issue explorer are not available.

Detailed Description

Eventrouter is a Kubernetes service that forwards cluster events to a specified sink.

The tool solves the problem of event persistence and analysis in Kubernetes clusters. By default, Kubernetes only retains events for a limited time, making it difficult to perform long-term behavioral analysis or debugging of workloads. Eventrouter actively watches the event resource in the Kubernetes system and pushes those events to a user-specified sink, enabling operators to forward events to external systems for archiving, machine learning, introspection, or other purposes. The service is designed to be relatively low overhead and supports configuration of multiple sinks.

Eventrouter suits operators who need to retain and analyze Kubernetes events beyond the cluster's default retention window. It works well for teams using existing EFK (Elasticsearch, Fluentd, Kibana) stacks, as it outputs wrapped JSON objects designed for easy indexing in Elasticsearch. The tool is appropriate for any cluster where long-term event analysis, debugging, or integration with external monitoring and logging systems is required. The project explicitly does not provide query capabilities or serve as a storage layer; those responsibilities belong to the sink system receiving the forwarded events.

The project maintains a straightforward, focused codebase written in Go. Development activity shows consistent engagement with the core functionality of event watching and forwarding, with attention to supporting multiple sink configurations and maintaining low operational overhead.