microsoft / microsoft/durabletask-java
Enhanced capabilities for Azure Monitor metrics for functions
还没有人认领这个 Issue。
- 主要语言
- Java
- 星标
- 29
- 派生
- 18
- 平均合并
- 1 天 10 小时
- 30 天内合并 PR
- 2
描述
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.
贡献指南
从这里开始
- 先读完整个 Issue,再读项目的贡献指南。
- 在 Issue 下留言说明你要接手 —— 这能避免两个人做同样的事。
- Fork 仓库,在一个分支上完成修改。
- 提交 Pull Request,并在描述里引用这个 Issue 编号。
调研方向
首先检查当前如何为 Java durable functions 发出 Azure Monitor 指标,以及如何表示 WorkflowOrchestrator 上下文。该 issue 提议使用 Labels 注解并传递 clientId、technicalAccountId 和 orgId,但未指定任何文件或测试;完成要求是就自定义指标标签及其验证达成一致的设计。
由索引模型根据 Issue 内容生成。
评估
- 技术栈
- azure, java
- 领域
- observability
- Issue 类型
- 功能
- 难度
- 5/5
- 预计耗时
- 一周以上
- 活跃度
- 停滞
- 描述清晰度
- 需要澄清
- 新手友好度
- 25/100