Ports

Pipelines in Chronosphere Telemetry Pipeline expose various ports to send and receive data. These ports correspond to different components of each pipeline.

View exposed ports for a pipeline

To view a list of exposed ports for a pipeline, use the following command:

calyptia get endpoints --pipeline PIPELINE

Replace PIPELINE with the name of your pipeline.

Inputs and outputs

Most source plugins and some destination plugins expose an associated port. Plugins that expose a port will set a default value for that port, but you can override this value when you configure plugins through the Telemetry Pipeline web interface or through pipeline configuration files.

Health check pipelines

The health check pipeline within each Core Instance exposes an HTTP server on TCP port 2020.

Uniqueness

For all pipelines within a single Core Instance, each open port must use a unique port number and protocol. This restriction applies to components within the same pipeline and components across different pipelines. However, different components can share a port number if one component uses TCP and another uses UDP.

For example, if Pipeline A and Pipeline B belong to the same Core Instance, both pipelines can't have a source plugin that exposes TCP port 1600, but Pipeline A can expose TCP port 1600 and Pipeline B can expose UDP port 1600. Similarly, Pipeline C can't have two different source plugins that both expose TCP port 1850, but it can have one plugin that exposes TCP port 1850 and another plugin that exposes TCP port 1851.