warpzone-sdk 15.0.0.dev4__tar.gz → 15.0.0.dev6__tar.gz

{warpzone_sdk-15.0.0.dev4 → warpzone_sdk-15.0.0.dev6}/PKG-INFO

@@ -1,6 +1,6 @@
 Metadata-Version: 2.4
 Name: warpzone-sdk
-Version: 15.0.0.dev4
+Version: 15.0.0.dev6
 Summary: The main objective of this package is to centralize logic used to interact with Azure Functions, Azure Service Bus and Azure Table Storage
 Author: Team Enigma
 Author-email: enigma@energinet.dk

{warpzone_sdk-15.0.0.dev4 → warpzone_sdk-15.0.0.dev6}/pyproject.toml

@@ -1,6 +1,6 @@
 [project]
 name = "warpzone-sdk"
-version = "15.0.0.dev4"
+version = "15.0.0.dev6"
 description = "The main objective of this package is to centralize logic used to interact with Azure Functions, Azure Service Bus and Azure Table Storage"
 authors = [{ name = "Team Enigma", email = "enigma@energinet.dk" }]
 requires-python = ">=3.10"

{warpzone_sdk-15.0.0.dev4 → warpzone_sdk-15.0.0.dev6}/warpzone/function/monitor.py

@@ -28,7 +28,8 @@ SUBJECT_IDENTIFIER = "<Subject>"
 @contextmanager
 def run_in_trace_context(context: func.Context):
     trace_context = context.trace_context
-    with traces.set_trace_context(trace_context.trace_parent):
+    span_name = context.function_name or "azure_function"
+    with traces.set_trace_context(trace_context.trace_parent, span_name=span_name):
         yield
 
 

{warpzone_sdk-15.0.0.dev4 → warpzone_sdk-15.0.0.dev6}/warpzone/monitor/traces.py

@@ -63,35 +63,30 @@ class AzureSDKTraceFilter(SpanProcessor):
 
 
 @contextmanager
-def set_trace_context(trace_parent: str):
-    """Context manager for setting the trace context.
+def set_trace_context(trace_parent: str, span_name: str = "function_execution"):
+    """Context manager for setting the trace context with a recording span.
 
-    Attaches the propagated trace context with a NonRecordingSpan so that
-    logs emitted within this context are properly correlated with the trace
-    created by Azure Functions.
-
-    The NonRecordingSpan is necessary because the LoggingHandler needs an
-    actual span (not just a SpanContext) to extract trace correlation IDs.
-    Using NonRecordingSpan avoids creating duplicate spans while still
-    providing the trace_id and span_id for log correlation.
+    Creates a child span of the propagated trace context. This is necessary
+    because the LoggingHandler requires a recording span to properly correlate
+    logs with the trace. A NonRecordingSpan (which is what TraceContextTextMapPropagator
+    creates) may not be correctly handled during log batching/export.
 
     Args:
         trace_parent (str): Trace parent ID from the incoming request
+        span_name (str): Name for the span. Defaults to "function_execution".
     """
     carrier = {"traceparent": trace_parent}
     ctx = TraceContextTextMapPropagator().extract(carrier=carrier)
 
-    # Get the span from the extracted context - this is a NonRecordingSpan
-    # created by the propagator with the correct trace_id and span_id
-    span = trace.get_current_span(ctx)
-
-    # Set this span as the current span in context
-    ctx = trace.set_span_in_context(span)
-
+    # Explicitly attach the extracted context first
     token = context.attach(ctx)
     try:
-        yield
+        # Now start a recording span as a child of the propagated context
+        tracer = trace.get_tracer(__name__)
+        with tracer.start_as_current_span(span_name):
+            yield
     finally:
+        # Explicitly detach to restore previous context
         context.detach(token)