Docs » Get started with the Splunk Distribution of the OpenTelemetry Collector » Collector requirements » Exposed ports and endpoints

Exposed ports and endpoints 🔗

By default, the Collector exposes several endpoints. The components providing these endpoints attempt to listen on loopback (localhost) or all interfaces (0.0.0.0), as detailed in this document.

The endpoints exposed depend on which mode the Collector is configured in. You can deactivate components, especially receivers, if they are not required for an environment.

Check ports to make sure your environment doesn’t have conflicts and that firewalls are configured properly. Ports can be changed in the YAML configuration file.

See the table for a complete list of exposed ports and endpoints:

<protocol>:<address>:<port>/<endpoint>

Description

http(s)://0.0.0.0:13133/

Health check extension useful for collector status reporting

http(s)://0.0.0.0:[6831|6832|14250|14268]/api/traces

The Jaeger receiver supporting Thrift and gRPC protocols

http(s)://localhost:55679/debug/[tracez|pipelinez]

zPages extension for component diagnostics

http(s)://0.0.0.0:[4317|4318]

OTLP receiver using gRPC and http

http(s)://0.0.0.0:6060

HTTP forwarder used to receive Smart Agent apiUrl data

http(s)://0.0.0.0:7276

SAPM trace receiver

http://localhost:8888/metrics

Internal Prometheus metrics

http(s)://localhost:8006

Fluent forward receiver

http(s)://0.0.0.0:9080

Smart Agent receiver with the SignalFx Forwarder (deprecated)

http(s)://0.0.0.0:9411/api/[v1|v2]/spans

Zipkin receiver supporting V1 and V2

http(s)://0.0.0.0:9943

SignalFx receiver supporting metrics and logs, including trace correlation data

For more information, see the agent and gateway configuration files.

This page was last updated on Nov 20, 2024.