Kubernetes warnings and errors can be easy to miss when they are scattered among individual resources. sentry-kubernetes watches selected events and forwards them to a Sentry project, making them available through Sentry’s grouping and notification workflow. It is a reporter running in the cluster, not an installation of the Sentry server. Configure the namespaces and outgoing event data deliberately, and remember that Kubernetes events provide neither a complete audit trail nor a substitute for availability monitoring.
Current guidance
This resource is the getsentry Kubernetes event reporter. Its current README explicitly labels the Go implementation beta and directs users of the historical Python implementation to a legacy directory. It watches Kubernetes warnings and errors and sends them to a Sentry project, making it a different component from the self-hosted Sentry server.
Review namespace scope, RBAC and outgoing data before enabling cluster-wide collection. The documented default watches only the default namespace, while historical-event collection, CronJob integration and annotation-selected DSNs are separate options. Those choices affect coverage and where workload information can be sent; a successful pod startup does not establish that all intended namespaces are observed.
For migration, compare event grouping, filters, environment tags and notification behavior with the old agent using a controlled warning event. Confirm that sensitive resource names or messages meet the destination’s retention policy. Kubernetes events are not a complete audit log, and this reporter should not replace API audit logging or metrics-based availability checks. Treat the beta status as an adoption constraint rather than silently promoting it to a production-support guarantee.
Historical upstream link check · 2026-10-09
The recorded upstream address responded successfully (HTTP 200) on 2026-10-09. Link availability does not certify the historical installation instructions or current security support.
Website availability is separate from project, chart and image support. Use the current guidance and primary sources on this page to assess the distribution.
Historical Kubedex content
Preserved for context. Commands, versions, prices and results below reflect the original research.
Sentry-kubernetes is a utility that pushes Kubernetes events to Sentry. 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 clearly presented and intelligently grouped. Typical Sentry features such as notifications can then be used to help operation and developer visibility.
Find out about exceptions right away
Set up Sentry in minutes with just a few lines of code. Get notifications via email, SMS, or chat as part of an existing workflow when errors occur or resurface.
Quickly find and fix production errors
Triage, reproduce and resolve errors with max efficiency and visibility. Exception handling with Sentry helps developers build better apps and iterate faster.
See the impact of each release
Integrate error tracking with your commit and deploy workflows. Aggregate events to see where bugs happen, how often, and who are affected before users even notice.
Error tracking built for the community
Sentry started as and remains a 100% open-source project, now delivered as a hosted service. Development aligns to security, observability, and production at scale.
Give users the power to help debug errors
Automatically prompt users for feedback so they know that you know things aren’t working.
Let them know you resolved their issue
Reach out to let affected users know they’ve experienced an error and help is on the way.
Sources & further reading
Spotted something that needs another look?
Help improve this page →