Service ports

Map Bugsnag's services to user-friendly hostnames and ports.

Bugsnag exposes a number of services, which you may wish to map to user-friendly hostnames and ports. Depending on your network configuration, you may need to configure your firewall, proxy or load balancer to make these changes.

Bugsnag dashboard

The main Bugsnag dashboard. Exposed on TCP port 49080.

We recommend you expose this on your internal network, so your teams can access Bugsnag in their browsers.

Health check information

URL: http://bugsnag.your-domain.com:49080/monitoring/health

Status Code: 200

Response Content: Empty response

Bugsnag event server

The write-only error and deploy reporting endpoint. Exposed on TCP port 49000.

This is where your applications will notify Bugsnag about errors and deploys. If you are sending crashes to Bugsnag from client-side applications (JavaScript & mobile) or applications outside your data center, you’ll need to expose this endpoint to the public internet.

Health check information

URL: http://bugsnag.your-domain.com:49000/ping

Status Code: 200

Response Content: “pong”

Bugsnag upload server

The write-only build artifact upload endpoint. Exposed on TCP port 49001.

If you are using Bugsnag with obfuscated iOS, macOS, Android, or JavaScript applications, we’ll recombine crashes with these build artifacts to help you with debugging.

Health check information

URL: http://bugsnag.your-domain.com:49001/ping

Status Code: 200

Response Content: “pong”

Bugsnag hooks server

The webhook endpoint used for two-way issue tracker integrations. Exposed on TCP port 49002.

We recommend you expose this to any issue tracker integrations you have configured.

Health check information

URL: http://bugsnag.your-domain.com:49002/ping

Status Code: 200

Response Content: “pong”

Bugsnag sessions server

The write-only sessions reporting endpoint. Exposed on TCP port 49003.

This is where your applications will notify Bugsnag about sessions. Sessions reported are used to calculate stability scores used on the releases dashboard. If you are sending session reports to Bugsnag from client-side applications (javascript & mobile) or applications outside your data center, you’ll need to expose this endpoint to the public internet.

Health check information

URL: http://bugsnag.your-domain.com:49003/ping

Status Code: 200

Response Content: “pong”

Bugsnag Build API

The Bugsnag Build API is exposed on the TCP port 49004.

This is where your applications can provide extra information whenever you build, release, or deploy your application.

Health check information

URL: http://bugsnag.your-domain.com:49004/ping

Status Code: 200

Response Content: “pong”

Bugsnag Data Access API

The Bugsnag Data Access API is exposed on the same TCP port as the dashboard, 49080, however to access this you have to set the X-Bugsnag-API: true header.

Health check information

The health check for the API is the same as the Bugsnag dashboard. Please see the health check section for the dashboard.

Grafana dashboard

Exposed on TCP port 49300.

This is where you can monitor your On-premise instance using pre built graphs and alerts.