Enhanced capabilities for Azure Monitor metrics for functions

Today, durable framework provides good metrics to see the load on the clusters on Azure Monitor. Eg. how many instances for a specific function are in failed/successful state.
But sometimes we need more than just these counts. Eg, each of these functions are triggered with some context, like this for triggered for which clientId, orgId etc. Now, these can be tags for the uber level failed/successful orchestrator/activity function.

I wanted to check if such an enhancement request could be catered to. I could think of a way like this :

@FunctionName("WorkflowOrchestrator")
@Labels [(clientId = ""), (technicalAccountId = ""), (orgId = "")]
public ObjectNode workflowOrchestrator(@DurableOrchestrationTrigger(name = "runtimeState") TaskOrchestrationContext ctx)

We could have a Labels annotation with a list of custom tags that could be added at the time of calling the function or be as a part of the context. And these could then be propagated as tags on Azure Monitor.

Commencez par examiner comment les métriques Azure Monitor sont actuellement émises pour Java durable functions et comment le contexte de WorkflowOrchestrator est représenté. L’issue propose une annotation Labels et la propagation de clientId, technicalAccountId et orgId, mais ne nomme aucun fichier ni test ; la tâche sera considérée comme terminée lorsqu’un design convenu pour les tags de métriques personnalisés et leur validation sera défini.