Struct TencentCloudClsPlugin 

pub struct TencentCloudClsPlugin {
    sink: BatchSink,
    log_format: Option<HashMap<String, Value>>,
    include_req_body: bool,
    include_resp_body: bool,
    global_tag: HashMap<String, Value>,
}

Node that batches access-log entries and ships them to Tencent Cloud CLS.

Fields

sink: BatchSink

log_format: Option<HashMap<String, Value>>

include_req_body: bool

include_resp_body: bool

global_tag: HashMap<String, Value>

Static tags merged into every entry before batching (global_tag).

Implementations

impl TencentCloudClsPlugin

pub fn from_config( config: &HashMap<String, Value>, resources: &Arc<PluginResources>, ) -> Result<Self, String>

Builds the plugin from node config.

Accepted keys:

• cls_host (alias endpoint) (string, required): CLS upload host, e.g. ap-guangzhou.cls.tencentcs.com.
• cls_topic (alias topic_id) (string, required): destination topic id, sent as the topic_id query parameter.
• secret_id / secret_key (strings, required): API credentials.
• scheme (http|https, default https).
• ssl_verify (bool, default true): verify TLS certificates.
• timeout (integer ms, default 10000): per-flush HTTP deadline.
• global_tag (object, optional): fields merged into every entry.
• include_req_body / include_resp_body (bool, default false).
• log_format (object, optional): custom flat entry.
• Batch tuning (see BatchConfig).

type: tencent-cloud-cls
config:
  cls_host: ap-guangzhou.cls.tencentcs.com
  cls_topic: xxxxxxxx-xxxx-xxxx
  secret_id: ${CLS_SECRET_ID}
  secret_key: ${CLS_SECRET_KEY}
  scheme: https

Trait Implementations

impl Plugin for TencentCloudClsPlugin

fn plugin_type(&self) -> &str

Unique identifier for the plugin type (e.g., “proxy-rewrite”, “upstream”).

fn execute<'life0, 'life1, 'async_trait>( &'life0 self, ctx: Context, _named_inputs: &'life1 HashMap<String, Value>, ) -> Pin<Box<dyn Future<Output = Result<PluginOutput, PluginExecutionError>> + Send + 'async_trait>>

where Self: 'async_trait, 'life0: 'async_trait, 'life1: 'async_trait,

Executes the plugin logic against the request/response context.