Skip to content

Latest commit

 

History

History

py-legacy

Folders and files

NameName
Last commit message
Last commit date

parent directory

..
1.png
1.png
 
 
2.png
2.png
 
 
3.png
3.png
 
 
README.md
README.md
 
 

README.md

⚠️ Note: these are instructions for the legacy Python implementation

⚠️ If you still want to use the legacy implementation, make sure to use the specific container image: getsentry/sentry-kubernetes:py-1.0.0a

⚠️ Here is the GitHub release that was cut as the final state for the Python-based agent: https://github.com/getsentry/sentry-kubernetes/releases/tag/py-1.0.0a

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:py-1.0.0a \
  --env="DSN=$YOUR_DSN"

Filters and options

See the full list in sentry-kubernetes.py

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:

1

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

2

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

3

Install using helm charts

$ helm repo add incubator https://kubernetes-charts-incubator.storage.googleapis.com/
"incubator" has been added to your repositories

$ helm install incubator/sentry-kubernetes --name my-release --set sentry.dsn=<your-dsn>