> For the complete documentation index, see [llms.txt](https://docs.sealights.io/knowledgebase/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.sealights.io/knowledgebase/setup-and-configuration/sealights-agents-and-plugins/https-collector/monitoring-and-troubleshooting.md). # Monitoring and Troubleshooting ## HTTPS Collector Web Interface The HTTPS Collector has a web interface available at `https://:/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](/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:

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

--- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation by asking a question. Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters: ``` GET https://docs.sealights.io/knowledgebase/setup-and-configuration/sealights-agents-and-plugins/https-collector/monitoring-and-troubleshooting.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case. 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.