Question 1

What is HyperDX?

Accepted Answer

HyperDX is an open-source observability platform that unifies logs, traces, metrics, and front-end session replay in a single interface, so you can correlate signals while debugging instead of switching between tools. It is built on ClickHouse for fast queries over large data and is OpenTelemetry-native. This all-in-one install bundles ClickHouse and runs the app on port 8310, with OpenTelemetry ingest on ports 4320 and 4321.

Question 2

Which ports does it use?

Accepted Answer

Four: the app UI on host port 8310 (from the container's 8080), an API on 8311, and two OpenTelemetry ingest endpoints — 4320 for OTLP over HTTP and 4321 for OTLP over gRPC. Your applications send telemetry to the OTLP ports, and you view it through the UI. Put the UI behind a reverse proxy with TLS, and keep the ingest ports reachable only by the services you are instrumenting.

Question 3

How is it different from Prometheus and Grafana?

Accepted Answer

Prometheus and Grafana, usually alongside Loki and Tempo, form a stack of separate best-of-breed components you run and wire together — very flexible but several moving parts. HyperDX aims to be one integrated platform that handles logs, traces, metrics, and session replay together with built-in correlation, on ClickHouse. Both are valid; HyperDX trades the stack's flexibility for a single unified system, and it adds session replay that the classic stack does not include.

Question 4

Do I need OpenTelemetry to use it?

Accepted Answer

Effectively yes — HyperDX ingests telemetry over OpenTelemetry, the vendor-neutral standard, so you instrument your applications to emit OTLP data and point their exporters at HyperDX's ingest ports. The upside of this design is that you are not tied to a proprietary agent: because OpenTelemetry is an open standard, you could point the same instrumentation at a different backend later, which avoids the lock-in that proprietary observability agents create.

Question 5

Why does it use ClickHouse?

Accepted Answer

ClickHouse is a columnar database designed for fast analytical queries over very large volumes of data, which is exactly the shape of observability workloads — huge amounts of logs, traces, and metrics that you need to search and aggregate quickly. HyperDX stores everything in ClickHouse for that speed, and this all-in-one image bundles it so there is nothing separate to set up. The practical implication is that ClickHouse wants adequate resources, and you should plan retention since telemetry grows fast.

Port	Purpose
8310	HyperDX app UI (mapped from container port 8080)
8311	HyperDX API (mapped from container port 8000)
4320	OpenTelemetry OTLP over HTTP ingest (mapped from container port 4318)
4321	OpenTelemetry OTLP over gRPC ingest (mapped from container port 4317)

🔭 Setup HyperDX — Open-Source Observability with Logs, Traces, and Session Replay

📦 Resources & Setup Scripts

Quick Install:

Tutorial Steps

1 Download the Script

2 Make it Executable

3 Run the Installer

4 Open HyperDX and Send Telemetry

Ports Used

Overview

Why Use It

When You Need It

Who Should Use It

Real Use Cases

Main Features

How to Use After Installation

Security Best Practices

Ports and Firewall Notes

Backup and Maintenance

Common Mistakes

Troubleshooting

Alternatives

When Not to Use It

PrismaTechWork Professional Help

Frequently Asked Questions