# Monitoring and Troubleshooting

## HTTPS Collector Web Interface <a href="#https-collector-web-interface" id="https-collector-web-interface"></a>

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…

<table data-header-hidden><thead><tr><th width="115.33331298828125"></th><th></th></tr></thead><tbody><tr><td><strong>Flows</strong></td><td><p><img src="/files/KBrnxL73yzd5dppKJYsv" alt="" data-size="original"></p><p><img src="/files/UBC1ztE42j34F3fUsM5t" alt="" data-size="original"></p></td></tr><tr><td><strong>Agents</strong></td><td><p><img src="/files/XtH0YSKGCXYkIEOJ7nCT" alt="" data-size="original"></p><p><img src="/files/PBztd8UfgCcCd59uSBcb" alt="" data-size="original"></p></td></tr><tr><td><strong>Logs</strong></td><td><img src="/files/HR7uxeROfky3I2buotrL" alt="" data-size="original"></td></tr><tr><td><strong>About</strong></td><td><img src="/files/d7UQTBuboJzzNYg8sIdB" alt="" data-size="original"></td></tr></tbody></table>

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

## Health API Endpoint <a href="#health-api-endpoint" id="health-api-endpoint"></a>

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 <a href="#open-telemetry-metrics" id="open-telemetry-metrics"></a>

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](/knowledgebase/setup-and-configuration/sealights-agents-and-plugins/https-collector/download-and-installation.md#configuration-file-reference) more details

The metrics that are exported are:

<table><thead><tr><th width="274">Metric Name</th><th width="152">Type</th><th width="92">Unit</th><th>Description</th></tr></thead><tbody><tr><td><code>http.server.request.duration</code></td><td>Histogram</td><td>seconds</td><td>Duration of HTTP requests</td></tr><tr><td><code>http.server.request.body.size</code></td><td>Counter</td><td>bytes</td><td>Size of HTTP request bodies</td></tr><tr><td><code>http.server.response.body.size</code></td><td>Counter</td><td>bytes</td><td>Size of HTTP response bodies</td></tr><tr><td><code>http.server.active_requests</code></td><td>UpDownCounter</td><td>requests</td><td>Number of active HTTP requests</td></tr></tbody></table>


---

# Agent Instructions: Querying This Documentation

If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://docs.sealights.io/knowledgebase/setup-and-configuration/sealights-agents-and-plugins/https-collector/monitoring-and-troubleshooting.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.