Network.Bugsnag.Settings

https://docs.bugsnag.com/api/error-reporting/#application-settings

Documentation

newtype BugsnagApiKey

Constructors

BugsnagApiKey

Fields

• unBugsnagApiKey :: Text

Instances

Show BugsnagApiKey

Methods

showsPrec :: Int -> BugsnagApiKey -> ShowS

show :: BugsnagApiKey -> String

showList :: [BugsnagApiKey] -> ShowS

IsString BugsnagApiKey

Methods

fromString :: String -> BugsnagApiKey

FromJSON BugsnagApiKey

Methods

parseJSON :: Value -> Parser BugsnagApiKey

parseJSONList :: Value -> Parser [BugsnagApiKey]

data BugsnagSettings

Notifier settings

See newBugsnagSettings.

Constructors

BugsnagSettings

Fields

• bsApiKey :: BugsnagApiKey

  Your Integration API Key.

• bsAppVersion :: Maybe Text

  The version of your application

  Marking bugs as Fixed and having them auto-reopen in new versions requires you set this.

• bsReleaseStage :: BugsnagReleaseStage

  The current release-stage, Production by default

• bsNotifyReleaseStages :: [BugsnagReleaseStage]

  Which release-stages to notify in. Only Production by default

• bsBeforeNotify :: BeforeNotify

  Modify any events before they are sent

  For example to attach a user, or set the context.

• bsIgnoreException :: BugsnagException -> Bool

  Exception filtering

  Functions like notifyBugsnag will do nothing with exceptions that pass this predicate. N.B. Something lower-level, like reportError won't be aware of this.

• bsGroupingHash :: BugsnagEvent -> Maybe Text

  The grouping hash to use for any specific event

  Events (exceptions) which have the same hash will be counted as the same exception. Use Nothing (the default) to maintain Bugsnags automatic behavior (group by top in-project stack-frame).

• bsIsInProject :: FilePath -> Bool

  Predicate for in-project stack frames

  By default, all are considered in-project.

• bsFilterStackFrames :: BugsnagStackFrame -> Bool

  Stack frame filter

  Return True for any stack-frames that should be omitted from notifications.

• bsHttpManager :: Manager

  The HTTP Manager used to emit notifications

  It's more efficient, and ensures proper resource cleanup, to share a single manager across an application. Must be TLS-enabled.

newBugsnagSettings :: BugsnagApiKey -> IO BugsnagSettings

Construct settings with a new, TLS-enabled Manager

>>> :set -XOverloadedStrings
>>> settings <- newBugsnagSettings "API_KEY"
>>> bsApiKey settings
API_KEY

>>> bsReleaseStage settings
ProductionReleaseStage

>>> bsNotifyReleaseStages settings
[ProductionReleaseStage]

bugsnagSettings :: BugsnagApiKey -> Manager -> BugsnagSettings

Construct settings purely, given an existing Manager

bugsnagShouldNotify :: BugsnagSettings -> BugsnagException -> Bool

Should this BugsnagException trigger notification?

>>> :set -XOverloadedStrings
>>> settings <- newBugsnagSettings ""
>>> let exception = bugsnagException "" "" []
>>> bugsnagShouldNotify settings exception
True

>>> let devSettings = settings { bsReleaseStage = DevelopmentReleaseStage }
>>> bugsnagShouldNotify devSettings exception
False

>>> bugsnagShouldNotify devSettings { bsNotifyReleaseStages = [DevelopmentReleaseStage] } exception
True

>>> let ignore = (== "IgnoreMe") . beErrorClass
>>> let ignoreSettings = settings { bsIgnoreException = ignore }
>>> bugsnagShouldNotify ignoreSettings exception
True

>>> bugsnagShouldNotify ignoreSettings exception { beErrorClass = "IgnoreMe" }
False