Configuring platform notifiers

Connect your applications to Bugsnag On-premise.

Error reporting libraries

By default, Bugsnag reporting libraries will send errors to and sessions, which enable Bugsnag to provide and compare crash rates between releases, to

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 endpoints.

For example, in Ruby apps:

Bugsnag.configure do |config|
  config.api_key = "your-api-key"
  config.endpoint = ""
  config.auto_capture_sessions = true
  config.session_endpoint = ''

For Browser JavaScript:

  <script src="//"></script>
  <script>window.bugsnagClient = bugsnag({
    apiKey: 'your-api-key',
    endpoint: '',
    autoCaptureSessions: true,
    sessionEndpoint: ''

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: