TELEMETRY PIPELINE
TCP

TCP source plugin

The TCP source plugin lets you send custom records to an HTTP endpoint. You can use this plugin to configure Chronosphere Telemetry Pipeline to collect data from machines on a network.

Supported telemetry types

This plugin supports these telemetry types:

LogsMetricsTraces

Configuration parameters

Use the parameters in this section to configure your plugin. The Telemetry Pipeline web interface uses the values in the Name column to describe the parameters. Items in the Key column are the YAML keys to use in pipeline configuration files.

Required

NameKeyDescriptionDefault
PortportRequired. The TCP port used for listening for incoming messages.5170

Advanced

NameKeyDescriptionDefault
FormatformatSets the format. Accepted values: json, none.none
SeparatorseparatorSets separator.none
Chunk Sizechunk_sizeSets the chunk size for incoming messages.none
Buffer Sizebuffer_SizeSets the chunk size for incoming JSON messages. These chunks are then stored and managed in the space available by buffer_size.none

Security and TLS

NameKeyDescriptionDefault
TLStlsEnable or disable TLS/SSL support. Accepted values: true, false.false
TLS Certificate Validationtls.verifyEnable or disable TLS/SSL certificate validation. TLS must be enabled for certificates to be validated. Accepted values: off, on.on
TLS Debug Leveltls.debugSet TLS debug verbosity level. Accepted values: 0 (No debug), 1 (Error), 2 (State change), 3 (Informational), 4 (Verbose).1
CA Certificate File Pathtls.ca_fileAbsolute path to CA certificate file.none
Certificate File Pathtls.crt_fileAbsolute path to certificate file.none
Private Key File Pathtls.key_fileAbsolute path to private key file.none
Private Key Path Passwordtls.key_passwdPassword for private key file.none
TLS SNI Hostname Extensiontls.vhostHostname to be used for TLS SNI extension.none