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.

首先檢視目前如何為 Java durable functions 發出 Azure Monitor 指標，以及如何表示 WorkflowOrchestrator context。該 issue 提議使用 Labels annotation 並傳遞 clientId、technicalAccountId 和 orgId，但未指定任何檔案或測試；完成要求是就自訂指標標籤及其驗證達成共識的設計。