The traces sent to Azure Monitor by the AzureExporter, collected by the opencensus Django middleware, set the custom properties django.user.id and django.user.name, and these properties are indeed well listed in Azure Monitor for these requests.
However the main request.user_Id and request.session_Id all appear empty in Azure Monitor, and indeed the AzureExporter source code does not seem to assign any of these as far as I can see.
This results in Azure Monitor listing all requests from my django application (with the correct django.user.id custom properties) with no User ID or Session ID, and the Users and Sessions sections of Azure Monitor are empty (or rather list a single user with empty ID and single session with empty ID.
Python 3.5.2 Django 2.2.10 opencensus==0.7.7 opencensus-context==0.1.1 opencensus-ext-azure==1.0.2 opencensus-ext-django==0.7.2 opencensus-ext-logging==0.1.0
The traces sent to Azure Monitor by the AzureExporter, collected by the opencensus Django middleware, set the custom properties
django.user.id
anddjango.user.name
, and these properties are indeed well listed in Azure Monitor for these requests.However the main
request.user_Id
andrequest.session_Id
all appear empty in Azure Monitor, and indeed the AzureExporter source code does not seem to assign any of these as far as I can see.This results in Azure Monitor listing all requests from my django application (with the correct
django.user.id
custom properties) with no User ID or Session ID, and the Users and Sessions sections of Azure Monitor are empty (or rather list a single user with empty ID and single session with empty ID.