Skip to content
Kubernetes event reporter for Sentry
Python Dockerfile
Branch: master
Clone or download

Latest commit

derom and HazAT Add namespace filter (#29)

* add filter to Readme

* Fix formatting of readme
Latest commit 521b512 Dec 17, 2019


Type Name Latest commit message Commit time
Failed to load latest commit information.
1.png Add screenshots Nov 9, 2017
2.png Add screenshots Nov 9, 2017
3.png Add screenshots Nov 9, 2017
Dockerfile Bump Python version. Mar 1, 2019
LICENSE Initial commit. Nov 6, 2017 Add namespace filter (#29) Dec 17, 2019
requirements.txt Bump urllib3 from 1.24.1 to 1.24.2 Oct 21, 2019 Add namespace filter (#29) Dec 17, 2019


Errors and warnings in Kubernetes often go unnoticed by operators. Even when they are checked they are hard to read and understand in the context of what else is going on in the cluster. sentry-kubernetes is a small container you launch inside your Kubernetes cluster that will send errors and warnings to Sentry where they will be cleanly presented and intelligently grouped. Typical Sentry features such as notifications can then be used to help operation and developer visibility.

Create a new project on Sentry and use your DSN when launching the sentry-kubernetes container:

kubectl run sentry-kubernetes \
  --image getsentry/sentry-kubernetes \

Filters and options

See the full list in

ENV var Description
EVENT_NAMESPACES_EXCLUDED A comma-separated list of namespaces. Ex.: 'qa,demo'. Events from these namespaces won't be sent to Sentry.

Events are grouped in Sentry:


They come with useful tags for filtering, and breadcrumbs showing events that occurred prior to the warning/error:


And include all of the extra data attached to the event:


Install using helm charts

$ helm repo add incubator
"incubator" has been added to your repositories

$ helm install incubator/sentry-kubernetes --name my-release --set sentry.dsn=<your-dsn>
You can’t perform that action at this time.