Service ports

List of BugSnag services and their corresponding NodePorts.

BugSnag has a number of services, for which you may wish to setup load balancers or user-friendly hostnames. The NodePort values described here are the defaults. You can change these values in the configuration if you have selected the “Other/none” option under “Kubernetes” -> “Which cloud provider are you using?”.

BugSnag dashboard

The main BugSnag dashboard.

Node Port

30080

Ingress Name

nginx

Health check information

URL: /monitoring/health

Status Code: 200

Response Content: Empty response

BugSnag event server

The write-only error and deploy reporting endpoint.

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.

Node Port

30000

Ingress Name

event-server

Health check information

URL: /ping

Status Code: 200

Response Content: “pong”

BugSnag upload server

The write-only build artifact upload endpoint.

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.

Node Port

30001

Ingress Name

upload-server

Health check information

URL: /ping

Status Code: 200

Response Content: “pong”

BugSnag hooks server

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

Node Port

30002

Ingress Name

hooks-server

Health check information

URL: /ping

Status Code: 200

Response Content: “pong”

BugSnag sessions server

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

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.

Node Port

30003

Ingress Name

session-server

Health check information

URL: /ping

Status Code: 200

Response Content: “pong”

BugSnag Build API

The BugSnag Build API is exposed on the TCP port 30004.

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

Node Port

30004

Ingress Name

release-server

Health check information

URL: /ping

Status Code: 200

Response Content: “pong”

BugSnag Data Access API

The BugSnag Data Access API is exposed on the same NodePort as the dashboard, 30080, 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.

BugSnag trace server

The write-only trace reporting endpoint. Exposed on TCP port 30005.

This is where your applications will notify BugSnag about trace/span data. Traces/spans reported are used to monitor the performance of the operations that are important to your users. If you are sending traces/spans 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.

Node Port

30005

Ingress Name

trace-server

Health check information

URL: /ping

Status Code: 200

Response Content: “pong”

Grafana dashboard

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

Node Port

30300

Ingress Name

grafana

Health check information

URL: /api/health

Status Code: 200

Response Content: Grafana version information