feat(bottlecap): handle timeouts

bottlecap/src/bin/bottlecap/main.rs

@@ -28,7 +28,7 @@ use bottlecap::{
     telemetry::{
         self,
         client::TelemetryApiClient,
-        events::{TelemetryEvent, TelemetryRecord},
+        events::{Status, TelemetryEvent, TelemetryRecord},
         listener::TelemetryListener,
     },
     traces::{
@@ -452,7 +452,9 @@ async fn extension_loop_active(
                                     // pass the invocation deadline to
                                     // flush tasks here, so they can
                                     // retry if we have more time
-                                    if flush_control.should_flush_end() {
+                                    //
+                                    // We always want to flush on a timeout
+                                    if flush_control.should_flush_end() || status == Status::Timeout {
                                         tokio::join!(
                                             logs_flusher.flush(),
                                             metrics_flusher.flush(),

bottlecap/src/lifecycle/invocation/processor.rs

@@ -274,6 +274,18 @@ impl Processor {
             // Increment the error type metric
             if status == Status::Timeout {
                 self.enhanced_metrics.increment_timeout_metric();
+
+                // Invocation Span will never have the `trace_id` or `span_id` set
+                self.span.trace_id = generate_span_id();
+                self.span.span_id = generate_span_id();
+                self.span.error = 1;
+                self.span.meta.insert(
+                    "error.msg".to_string(),
+                    "Datadog detected an Impending Timeout".to_string(),
+                );
+                self.span
+                    .meta
+                    .insert("error.type".to_string(), "Impending Timeout".to_string());
             }
         }