Struct SlsLoggerPlugin 

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

Node that batches access-log entries and ships them to Alibaba Cloud SLS.

Fields

sink: BatchSink

log_format: Option<HashMap<String, Value>>

include_req_body: bool

include_resp_body: bool

Implementations

impl SlsLoggerPlugin

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

Builds the plugin from node config.

Accepted keys (all of host/port/project/logstore/ access_key_id/access_key_secret are required):

• host (string): SLS endpoint, e.g. cn-hangzhou.log.aliyuncs.com.
• port (integer): endpoint port, e.g. 443.
• project (string): SLS project; prefixed to host as the request authority <project>.<host>.
• logstore (string): destination logstore.
• access_key_id / access_key_secret (strings): RAM credentials used to sign each request.
• timeout (integer ms, default 5000): per-flush HTTP deadline.
• include_req_body / include_resp_body (bool, default false).
• log_format (object, optional): custom flat entry.
• Batch tuning (see BatchConfig).

type: sls-logger
config:
  host: cn-hangzhou.log.aliyuncs.com
  port: 443
  project: my-project
  logstore: gateway
  access_key_id: ${SLS_KEY_ID}
  access_key_secret: ${SLS_KEY_SECRET}

Trait Implementations

impl Plugin for SlsLoggerPlugin

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.