TELEMETRY PIPELINE
Redpanda Cloud

Redpanda Cloud DataSet destination plugin

The Redpanda Cloud destination plugin (name: kafka, alias: RedPandaCloud) lets you send your telemetry pipeline data to the Redpanda Cloud service.

Supported telemetry types

This plugin for Chronosphere Telemetry Pipeline 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.

General

NameKeyDescriptionDefault
BrokersbrokersRequired. List of Kafka Brokers. For example, 192.168.1.3:9092, 192.168.1.4:9092none
TopicstopicsRequired. Single entry or comma-separated list of topics that Telemetry Pipeline uses to send messages to Kafka. If only one topic is set, that one will be used for all records. If multiple topics exist, the topic set in the record by Topic_Key is used.calyptia-core
FormatformatRequired. Specifies a data format. Accepted values: json, msgpack.json

Advanced

NameKeyDescriptionDefault
Security Protocolrdkafka.security.protocolThe Security Protocol used to communicate with Redpanda.sasl_ssl
SASL Mechanismrdkafka.sasl.mechanismsThe SASL authentication mechanism for the API.SCRAM-SHA-256
Redpanda Usernamerdkafka.sasl.usernameYour Redpanda username.none
Redpanda Passwordrdkafka.sasl.passwordRequired. Password for your Redpanda username.none
Message Keymessage_keyOptional key to store the message.none
Message Key Fieldmessage_key_fieldIf set, the value of Message_Key_Field in the record will indicate the message key. If not set nor found in the record, Message_Key will be used if set.none
Timestamp Keytimestamp_keySets the key to store the record timestamp.none
Timestamp Formattimestamp_formatSets the format to iso8601 or double.double
Body Keybody_keySpecifies the key that contains the body.none
Queue Full Retriesqueue_full_retriesTelemetry Pipeline queues data into rdkafka library. If the underlying library can’t flush the records the queue might fill and block new addition of records. This option sets the number of local retries to enqueue the data. The interval between each retry is 1 second. Setting queue_full_retries to 0 to set an unlimited number of retries.10

Extended librdkafka parameters

This plugin uses the librdkafka (opens in a new tab) library. Certain configuration parameters available through the Telemetry Pipeline UI are based on librdkafka settings. These parameters generally use the rdkafka. prefix.

In addition to the parameters available through the Telemetry Pipeline UI, you can customize any of the librdkafka configuration properties (opens in a new tab) by adding them to a pipeline configuration file. To do so, append the rdkafka. prefix to the name of that property.

For example, to customize the socket.keepalive.enable property, add the rdkafka.socket.keepalive.enable key to your configuration file.