Struct TelemetryCompletionHandler

pub struct TelemetryCompletionHandler { /* private fields */ }

A handler that ensures telemetry data is properly exported upon Lambda function completion.

This type manages the completion of telemetry data export based on the configured mode:

• In Sync mode, directly exports the data in the handler thread

  • Simple execution path with no IPC overhead
  • Efficient for small payloads and low resource environments
  • Guarantees span delivery before response

• In Async mode, notifies the internal extension to export the data

  • Requires coordination with extension process
  • Additional overhead from IPC
  • Provides retry capabilities through extension

• In Finalize mode, lets the processor handle the export strategy

  • Full control over export timing and behavior
  • Compatible with BatchSpanProcessor
  • Best for specialized export requirements

Thread Safety

The handler is thread-safe and can be cloned and shared between threads.

Example

use lambda_otel_lite::{init_telemetry, TelemetryConfig};
use lambda_runtime::{service_fn, Error, LambdaEvent};

async fn handler(event: LambdaEvent<serde_json::Value>) -> Result<serde_json::Value, Error> {
    // ... handler logic ...
    Ok(event.payload)
}

#[tokio::main]
async fn main() -> Result<(), Error> {
    let completion_handler = init_telemetry(TelemetryConfig::default()).await?;
    lambda_runtime::run(service_fn(|event| async {
        let result = handler(event).await;
        completion_handler.complete();
        result
    })).await
}

Implementations

impl TelemetryCompletionHandler

pub fn mode(&self) -> ProcessorMode

Returns the current processor mode

pub fn provider(&self) -> &Arc<SdkTracerProvider>

Get a reference to the tracer provider

pub fn complete(&self)

Signals completion of the current Lambda invocation, triggering telemetry export.

The behavior depends on the processor mode:

• In Sync mode:

  • Directly exports spans in the handler thread
  • Simple execution path with no IPC overhead
  • Blocks until export completes
  • Best for small payloads or when immediate delivery is required

• In Async mode:

  • Notifies the extension to handle export
  • Non-blocking operation in handler thread
  • Requires coordination with extension process
  • Provides retry capabilities through extension

• In Finalize mode:

  • Lets the configured processor handle export
  • Behavior depends on processor implementation
  • Useful for custom export strategies
  • No additional action taken by handler

pub fn force_export(&self)

Forces immediate export of all telemetry data, regardless of mode.

This is useful when you need to ensure all telemetry data is exported immediately, such as during shutdown or error handling.

Trait Implementations

impl Clone for TelemetryCompletionHandler

fn clone(&self) -> TelemetryCompletionHandler

Returns a copy of the value.

fn clone_from(&mut self, source: &Self)

Performs copy-assignment from source.