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.

Inizia esaminando come vengono attualmente emesse le metriche di Azure Monitor per Java durable functions e come viene rappresentato il contesto di WorkflowOrchestrator. L’issue propone un’annotazione Labels e la propagazione di clientId, technicalAccountId e orgId, ma non indica file o test; il lavoro sarà considerato completato quando sarà definito un design condiviso per i tag delle metriche personalizzati e la relativa validazione.