A user checking the Splunk OTel Collector support receivers will notice there is no receiver that can monitor TCP ports. There is a TCP Check Receiver available in contrib, however there this is not yet available in the Splunk OTel Collector distribution. The workaround is to use the Prometheus Blackbox Exporter.
1) Check the Splunk OTel Collector support receivers page, there is no receiver that can monitor TCP ports.
2) Check the contrib distribution, there is TCP Check Receiver, however there is no ETA for when this will be available in the Splunk OTel Collector. Please vote on this Splunk Ideas ticket.
3) HTTP Check Receiver can only check HTTP or HTTPS destinations.
1) Find the Prometheus Blackbox Exporter tar ball to download
Visit the prometheus blackbox exporter releases page here.
Right click the blackbox_exporter*linux-amd64.tar.gz you would like to download and copy the link.
2) Download the Prometheus Blackbox Exporter
Change the link in the sample below to reflect the version to download.
$ wget https://github.com/prometheus/blackbox_exporter/releases/tag/v0.26.0/blackbox_exporter-0.26.0.linux-amd64.tar.gz
3) Unzip the Prometheus Blackbox Exporter
$ tar -xzvf blackbox_exporter-0.26.0.linux-amd64.tar.gz
blackbox_exporter-0.26.0.linux-amd64/
blackbox_exporter-0.26.0.linux-amd64/LICENSE
blackbox_exporter-0.26.0.linux-amd64/NOTICE
blackbox_exporter-0.26.0.linux-amd64/blackbox.yml
blackbox_exporter-0.26.0.linux-amd64/blackbox_exporter
4) Move the blackbox_exporter to your local bin directory so it can be executed
$ sudo mv blackbox_exporter-*/blackbox_exporter /usr/local/bin/
5) Add the blackbox configuration
Make the configuration file directory
$ sudo mkdir -p /etc/blackbox
Edit the blackbox configuration file
$ sudo vim /etc/blackbox/blackbox.yml
modules:
tcp_connect:
prober: tcp
timeout: 5s
6) Start blackbox exporter
$ /usr/local/bin/blackbox_exporter --config.file=/etc/blackbox/blackbox.yml
time=2025-05-23T00:05:45.088Z level=INFO source=main.go:86 msg="Starting blackbox_exporter" version="(version=0.26.0, branch=HEAD, revision=444e3d089ae1aeeed385712ef84a5fa4f0c083ec)"
time=2025-05-23T00:05:45.088Z level=INFO source=main.go:87 msg="(go=go1.23.6, platform=linux/amd64, user=root@87341586bc85, date=20250226-12:29:43, tags=unknown)"
time=2025-05-23T00:05:45.089Z level=INFO source=main.go:99 msg="Loaded config file"
time=2025-05-23T00:05:45.089Z level=INFO source=tls_config.go:347 msg="Listening on" address=[::]:9115
time=2025-05-23T00:05:45.089Z level=INFO source=tls_config.go:350 msg="TLS is disabled." http2=false address=[::]:9115
7) Install Splunk OTel Collector
Splunk OTel Collector install documentation here.
Exampe:
$ curl -sSL https://dl.signalfx.com/splunk-otel-collector.sh > /tmp/splunk-otel-collector.sh && \
sudo sh /tmp/splunk-otel-collector.sh --realm <Your Realm> -- <Your Token String> --mode agent --without-instrumentation --discovery
8) Configure the Otel Collector to Scrape Blackbox Exporter
Add prometheus to the receivers section of your /etc/otel/collector/agent_config.yaml file. Change the targets to your servers and ports.
receivers:
prometheus:
config:
scrape_configs:
- job_name: 'blackbox-tcp'
metrics_path: /probe
params:
module: [tcp_connect]
static_configs:
- targets:
- kiamaelectrical.com:443
- 172.31.89.226:22
relabel_configs:
- source_labels: [__address__]
target_label: __param_target
- source_labels: [__param_target]
target_label: instance
- target_label: __address__
replacement: 127.0.0.1:9115 # Blackbox Exporter address
Enable prometheus in the services section of your configuration file.
service:
pipelines:
metrics:
receivers: [hostmetrics, otlp, signalfx, prometheus]
processors: [memory_limiter, batch, resourcedetection]
exporters: [signalfx]
9) Restart your Splunk OTel Collector
sudo systemctl restart splunk-otel-collector
10) Create a chart in Splunk Observability Cloud and filter by sf_metric:probe_success
Screenshot showing the TCP ports monitored in Splunk Observability Cloud

Other metrics Prometheus BlackBox Exporter offers shown in screenshot below.

| Revision | Publish Date | Comments |
|---|---|---|
1.0 |
01-Oct-2026
|
Initial Release |