Load balancer configuration for BugSnag On-premise.
The following load balancer configuration is only recommended if you are using BugSnag Performance SDKs or sending OpenTelemetry trace data via HTTP.
Public Port: 80/443
Backend Protocol: HTTP
Backend Protocol Version: HTTP/1.1
Backend Service Port: Trace server
The following load balancer configuration is recommended in order to process OpenTelemetry trace data.
Public Port: 4317
Backend Protocol: HTTPS
Backend Protocol Version: HTTP/2 (gRPC)
Backend Service Port: Trace server OTLP
Public Port: 4318
Backend Protocol: HTTP
Backend Protocol Version: HTTP/1.1
Backend Service Port: Trace server
If you wish to send OpenTelemetry spans with the API key as a subdomain you must create a wildcard DNS record pointing to the load balancer.
For example, if the load balancer is accessible at otlp.example.com, create a wildcard DNS record for *.otlp.example.com pointing to the load balancer.
Ensure that any certificate used by the load balancer includes this wildcard domain (*.otlp.example.com) in the Subject Alternative Name (SAN) field.
Reconfigure your installation using the Replicated KOTS admin console, setting Service access > OTEL endpoint to the wildcard domain root e.g. otlp.example.com.
The following load balancer configuration is recommended in order to process SmartBear MCP server requests.
Public Port: 80/443
Backend Protocol: HTTP
Backend Protocol Version: HTTP/1.1
Backend Service Port: SmartBear MCP server
The following load balancer configuration is recommended in order to process SmartBear MCP OAuth server requests.
Public Port: 80/443
Backend Protocol: HTTP
Backend Protocol Version: HTTP/1.1
Backend Service Port: SmartBear MCP OAuth server
Reconfigure your installation using the Replicated KOTS admin console, setting MCP settings > MCP OAuth server host to the domain root e.g. https://oauth.example.com.