Home

This wiki is for getting things done with Sentry-v2: recipes that start from a problem on your host and end with it handled. The reference, every config key, flag and field, lives in docs/, where it's versioned with the code and checked by the tests. When the two disagree, docs/ wins, and I'd like to hear about it.

Recipes

• Find out why a service keeps dying: tie a failing unit to the SELinux denials behind it, and read them before you change any policy.
• Keep a batch job from starving the box: a memory throttle on batch-*.service, run in dry-run first, then switched on.
• Send bundles to a webhook: a signed webhook, a key systemd hands to the daemon, and checking it on the other end.

Got one of your own? Write a recipe says how.

Where things are

You want	Go to
Install it and see a first bundle	Installation, then the quickstart
Every policy key	Policies
What an action changes and how it's undone	Actions and safety
Why a denial was or wasn't linked	Correlation
Something isn't working	Troubleshooting and the FAQ
A question	Discussions
A bug	Issues