# opsgenie/kubernetes-event-exporter

Export Kubernetes events to multiple destinations with routing and filtering

Repository: https://github.com/opsgenie/kubernetes-event-exporter
Canonical: https://ross.abutalabs.com/products/kubernetes-event-exporter
Language: Go
License: Apache-2.0
License Family: permissive
Topics: kubernetes, events, exporting, alerting, observability
Archived: true
Last push: 2022-08-31T11:33:33+00:00

## Health v2 (maintenance only)
Score: 10/100 (v2, computed 2026-09-02T17:46:02.011165+00:00)
- activity 0, release rhythm 8, longevity 100
- inputs: {"age_days": 2492, "days_push": 1463, "days_rel": null, "gap_med": null, "n_releases_24m": 0}
- flags: archived
- formula: round(0.45*activity + 0.35*rhythm + 0.20*longevity); archived -> min(score, 10)

## Adoption (not part of the score)
Stars 1048, forks 415 (observed 2026-08-28T04:03:22.562372+00:00)

## What it is
A Go-based tool that watches Kubernetes cluster events and exports them to multiple destinations such as Opsgenie, Slack, and Elasticsearch, with flexible tree-based routing and filtering rules. This original repository is deprecated in favor of the resmoio/kubernetes-event-exporter fork.

## Use cases
- export kubernetes events to elasticsearch
- send critical k8s events to opsgenie for on-call alerting
- route pod events to slack channels by namespace or labels
- capture kubernetes warning events for observability
- filter out normal events and only alert on failures
- dump all cluster events to a log store for auditing

## When to choose
- you need configurable, tree-based routing of Kubernetes events to alerting or storage backends
- you want to catch events that are otherwise missed by default cluster monitoring
- you need per-namespace or per-label event routing to different receivers

## When to avoid
- you are starting a new deployment - use the maintained resmoio/kubernetes-event-exporter fork instead
- you need metrics-based monitoring rather than event export
- you want a fully managed solution without maintaining a YAML routing configuration

## Facets
- artifact type: application
- maturity: abandoned
- function: monitoring, alerting, logging, streaming
- domain: monitoring
- platform: go, self-hosted, cross-platform
- tags: kubernetes-events, event-exporter, opsgenie, deprecated, observability, slack-alerts, elasticsearch, kubernetes, devops, containers, docker

## Member repositories
- opsgenie/kubernetes-event-exporter (main) score 10

## Provenance
- Observed fields: from GitHub, fetched 2026-08-28T04:03:22.562372+00:00.
- Health v2: computed from the inputs above; adoption is never an input.
- Inferred fields (summary, facets, guidance): AI-extracted, prompt v1, taxonomy v1, on 2026-08-30T07:00:48.437934+00:00, confidence not recorded.
  - readme: https://github.com/opsgenie/kubernetes-event-exporter (fetched 2026-08-28T04:03:22.562372+00:00, sha 24c018c73a87)
- Data as of 2026-08-30T08:39:29.467469+00:00.