Question 1

How do I set up Raven.cr with my Kemal app?

Accepted Answer

Add Raven.cr to your shard.yml, require it in your code, and set the SENTRY_DSN environment variable. The README mentions built-in Kemal integration, which automatically hooks into the framework's error handling without extra code.

Question 2

Can Raven.cr handle background job errors in Sidekiq.cr?

Accepted Answer

Yes, it has built-in Sidekiq.cr support. The async configuration example shows how to enqueue error events as jobs, ensuring errors from workers are captured without blocking the job queue.

Question 3

What data does Raven.cr scrub by default to protect privacy?

Accepted Answer

By default, it removes sensitive information like credit card or Social Security numbers, and does not report POST, PUT, PATCH data or cookies. You can customize processors for more control, as per the README's reference to Sentry documentation.

Question 4

Raven.cr vs official Sentry SDKs: which should I use?

Accepted Answer

For Crystal apps, Raven.cr is the only Sentry option since there's no official SDK. In other languages, official SDKs offer better support, but Raven.cr effectively fills this gap with feature parity and framework integrations.

Question 5

How to capture unhandled exceptions in a Crystal CLI tool with Raven.cr?

Accepted Answer

Use the crash handler binary by building it with shards and running your tool through it. The README details compiling sentry.crash_handler and executing it with your app to catch crashes like segfaults.

Question 6

Does Raven.cr slow down my Crystal application?

Accepted Answer

Not significantly, thanks to async support. Events can be sent in background fibers or jobs, minimizing impact on the main thread, and configuration allows tuning for performance-critical environments.

raven.cr

What is raven.cr?

Overview

Use Cases

Best For

Found a gem we're missing?

Not Ideal For

Pros & Cons

Pros

Cons

Frequently Asked Questions