Cloudflare source plugin

The Cloudflare source plugin lets you configure Chronosphere Telemetry Pipeline to collect data from Cloudflare.

Supported telemetry types

This plugin supports these telemetry types:

Logs	Metrics	Traces

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.

Name	Key	Description	Default
none	`addr`	The address to listen to for incoming data.	`:9880`
none	`resp_headers`	The response headers to set, each separated by a newline character. Supports templating.	`Content-Type: application/json`
none	`resp_status_code`	The response status code to set. This value must be an integer. Supports templating.	`200`
none	`resp_body`	The response body to set. Supports templating.	`{\"status\": \"ok\"}`
none	`time_from`	The time to set. This value must be an RFC3339 formatted string. Supports templating.	Current RFC3339 time
none	`cert_file`	The path to the certificate file to enable TLS.	none
none	`key_file`	The path to the key file to enable TLS.	none

Example configuration

The following example shows one possible way to set the inputs section of your pipeline's YAML configuration file for the Cloudflare source plugin:

pipeline:
  inputs:
    - name: cloudflare
      addr: :9880
      resp_headers: |-
        X-Custom: some value
        X-Custom-2: some other value
      resp_status_code: 200
      resp_body: |-
        {"status":"ok"}
      time_from: |-
        {{.time}}
      cert_file: ./cert.pem
      key_file: ./key.pem

Bash Command Confluent Cloud