Configuring platform notifiers

Connect your applications to BugSnag On-premise.

Error reporting libraries

By default, BugSnag reporting libraries will send errors to notify.bugsnag.com and sessions, which enable BugSnag to provide and compare stability scores between releases, to sessions.bugsnag.com.

You’ll need to configure your applications to send errors and sessions to your On-premise installation, at the hostname/port you configured for the BugSnag Event Server and [BugSnag Sessions Server]/on-premise/clustered/service-ports/#bugsnag-sessions-server) endpoints.

For example, in Ruby apps:

Bugsnag.configure do |config|
  config.api_key = "YOUR_API_KEY"
  config.endpoints = Bugsnag::EndpointConfiguration.new(
    "https://notify-bugsnag.internal.example.com"
    "https://sessions-bugsnag.internal.example.com"
  )
end

For Browser JavaScript:

Bugsnag.start({
  apiKey: 'YOUR_API_KEY',
  endpoints: {
    notify: 'https://bugsnag-notify.example.com',
    sessions: 'https://bugsnag-sessions.example.com'
  }
})

For other libraries see the configuration options for your platform.

Performance libraries

By default, BugSnag performance libraries will send trace and span data to otlp.bugsnag.com/v1/traces.

You’ll need to configure your applications to send trace/span data to your On-premise installation, at the hostname/port you configured for the BugSnag Trace Server endpoint.

For example in browser JavaScript applications:

BugsnagPerformance.start({
  apiKey: 'YOUR_API_KEY',
  endpoint: 'https://otlp.example.com/v1/traces'
})

For other libraries see the configuration options for your platform.

Reporting builds

If you are using a build tool integration you’ll need to configure the Build API endpoint to the hostname/port of your BugSnag Build API endpoint. See the docs for your build tool for details.

Uploading mapping files

On platforms that require a mapping files to deobfuscate or unminify stacktraces, you’ll need to set the endpoint to the hostname/port of your BugSnag Upload Server: