warpzone-sdk 15.0.0.dev9__tar.gz → 15.0.0.dev10__tar.gz

{warpzone_sdk-15.0.0.dev9 → warpzone_sdk-15.0.0.dev10}/PKG-INFO

@@ -1,6 +1,6 @@
 Metadata-Version: 2.4
 Name: warpzone-sdk
-Version: 15.0.0.dev9
+Version: 15.0.0.dev10
 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.dev9 → warpzone_sdk-15.0.0.dev10}/pyproject.toml

@@ -1,6 +1,6 @@
 [project]
 name = "warpzone-sdk"
-version = "15.0.0.dev9"
+version = "15.0.0.dev10"
 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.dev9 → warpzone_sdk-15.0.0.dev10}/warpzone/function/monitor.py

@@ -15,6 +15,16 @@ SUBJECT_IDENTIFIER = "<Subject>"
 
 @contextmanager
 def run_in_trace_context(context: func.Context):
+    """Set up trace context and ensure log correlation for this function invocation.
+
+    This sets:
+    1. OpenTelemetry trace context (for distributed tracing via Service Bus)
+    2. Azure Functions invocation_id in thread-local storage (for log correlation)
+    """
+    # Ensure Azure Functions' log correlation uses this invocation's ID
+    # This prevents log leakage when multiple functions run concurrently
+    context.thread_local_storage.invocation_id = context.invocation_id
+
     trace_context = context.trace_context
     with traces.set_trace_context(
         trace_context.trace_parent, trace_context.trace_state

{warpzone_sdk-15.0.0.dev9 → warpzone_sdk-15.0.0.dev10}/warpzone/monitor/logs.py

@@ -19,9 +19,8 @@ logging.getLogger("azure.monitor.opentelemetry.exporter").setLevel(logging.WARNI
 def get_logger(name: str):
     """Get a logger instance.
 
-    The logger will automatically use the current OpenTelemetry trace context
-    for correlation in Application Insights. The trace context is set by the
-    monitor decorator's run_in_trace_context context manager.
+    Logs are correlated with the correct function invocation via Azure Functions'
+    thread-local storage invocation_id, which is set by the monitor decorator.
 
     Args:
         name: Logger name, typically __name__