Skip to content
This repository was archived by the owner on Aug 30, 2023. It is now read-only.

Conversation

@kaylarose
Copy link
Contributor

Add a simple way to put Raven in "Debug Mode" - basically a way prevent it from sending messages to the server - but still allow Raven to handle exceptions and messages as-normal.

This prevents exceptions/messages during Development Cycles from cluttering up the Sentry stream - as well as being able to debug values for Messages that are sent to Raven.

Example Usage:

    [RavenClient clientWithDSN:@"XYZ"];
#ifdef DEBUG
    [RavenClient sharedClient].debugMode = YES;
#endif
    [[RavenClient sharedClient] setupExceptionHandler];

NSLog Output:

Sentry JSON (will not be sent in Debug Mode):
[JSON BODY]

@asbjornu
Copy link
Contributor

asbjornu commented Feb 1, 2015

While I don't oppose this change, I do think you would be better off having different DSNs for each environment you deploy your application to. We, for instance, have one for development, one for staging and one for production. Then you can also set up different alert policies on each project, so you only get e-mail on production errors, for instance.

To group each project (environment) into a common bundle, you can create a "Team" that holds the name of the application.

@dcramer
Copy link
Member

dcramer commented Feb 1, 2015

We enable this behavior on other platforms simply by not configuring a DSN. 

@timorzadir
Copy link
Contributor

For the sake of consistency, I think we should enable this feature by not configuring a DSN as suggested by @dcramer.

@timorzadir timorzadir merged commit 368c7ed into getsentry:master Feb 27, 2015
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants