Monitoring and Troubleshooting

HTTPS Collector Web Interface

The HTTPS Collector has a web interface available at https://<Collector Url>:<port>/web and provides you:

1. Flows: Full view of all incoming messages to the collector (including a full test search in all content and headers)

2. Agents and NodeJS Agents: A full detailed page for each Agent that is created for aggregation (including Node JS NYC collector)

3. Logs: Ability to stream and manipulate all the logs from the collector with options like full filters, saving…

4. About page on the collector, its version…

Flows
Agents
Logs
About

Note, there is a separate web interface for both the standard collector port and the proxy port

Health API Endpoint

Each collector exposes a health endpoint at: https://{collector-host}:{collector-port}/health and the result of the call will be JSON with metadata, statistics, and timestamps of collector operations.

If health works correctly and you still have problems, check that https://{collector-host}:{collector-port}/api is reachable. If not, something is blocking the collector from reaching SeaLights Cloud Services.

Open Telemetry Metrics

The HTTPS Collector supports exporting HTTP metrics using the OpenTelemetry Protocol (OTLP). This allows metrics to be sent to any OTLP-compatible observability backend, including platforms such as Datadog, Grafana, and Prometheus (via an OpenTelemetry Collector).

Turning on this feature can be done by adding the otel section for the respective functionality in the config.yaml file. See Configuration File Reference more details

The metrics that are exported are:

Metric Name	Type	Unit	Description
http.server.request.duration	Histogram	seconds	Duration of HTTP requests
http.server.request.body.size	Counter	bytes	Size of HTTP request bodies
http.server.response.body.size	Counter	bytes	Size of HTTP response bodies
http.server.active_requests	UpDownCounter	requests	Number of active HTTP requests