Prevent API v1 metric export loss and automate collector deployment
维护者通常 2 天内回复
还没有人认领这个 Issue。
评估
- 难度
- 5/5
- 预计耗时
- 一周以上
- 新手友好度
- 38/100
- Issue 类型
- 功能
- 描述清晰度
- 基本清楚
- 活跃度
- 活跃
- 技术栈
- github-actions, google-cloud, python
调研方向
Start by locating the API v1 Python process setup and the authenticated collector configuration and deployment workflow. Review the existing Google Monitoring location, instance identifiers, and deployment verification approach before making changes. Done means the stated acceptance criteria pass: trace and metric RPCs succeed, logs RPC is unavailable, Cloud Run is ready, and post-deployment logs show none of the five observed rejection forms.
由索引模型根据 Issue 内容生成。
描述
Problem
The central OpenTelemetry Collector rejected 863 metric points across 46 export errors in the reviewed production interval. The failures included missing Google Monitoring location values and time-series collisions caused by processes sharing one service.instance.id. Collector configuration changes also lack a maintained deployment and verification workflow.
Proposed change
- Add the configured Google Monitoring
locationto metrics only. - Give every API v1 Python process a stable unique instance identifier.
- Add a manually dispatched workflow that validates, builds, deploys, and verifies the authenticated collector.
- Tag collector images with the source commit.
- Verify trace and metric RPCs succeed and the logs RPC is unavailable.
- Document deployment inputs, IAM requirements, and post-deployment metric verification.
Acceptance criteria
- Trace resources retain the workload's actual
cloud.region. - Metrics include the collector's configured location.
- The workflow fails clearly for missing or malformed deployment configuration.
- The deployed Cloud Run service must become ready before endpoint verification.
- Post-deployment logs show no recurrence of the five observed metric rejection forms.
- 主要语言
- Python
- 星标
- 18
- 派生
- 33
- 平均合并
- 2 天 21 小时
- 30 天内合并 PR
- 24
环境准备
- 没有 Dockerfile 或 Docker Compose 文件
- 没有 Pull Request 模板
- 阅读贡献指南
从这里开始
- 先读完整个 Issue，再读项目的贡献指南。
- 在 Issue 下留言说明你要接手 —— 这能避免两个人做同样的事。
- Fork 仓库，在一个分支上完成修改。
- 提交 Pull Request，并在描述里引用这个 Issue 编号。
PolicyEngine/policyengine-api 的其他 Issue
-
Keep staging candidate integration tests on the deployment runner可能已有人在做 @anth-volk 于 1 天前认领。 未关闭
难度 4/5 3-5 天 新手友好度 52/100
PolicyEngine/policyengine-api#3869 ·
维护者通常 2 天内回复
-
State society-wide reports run on the sparse national dataset可能已有人在做 @anth-volk 于 2 天前认领。 未关闭
难度 4/5 3-5 天 新手友好度 35/100
PolicyEngine/policyengine-api#3864 ·
维护者通常 2 天内回复
-
难度 5/5 一周以上 新手友好度 38/100
PolicyEngine/policyengine-api#3823 ·
维护者通常 2 天内回复
-
API v2: report validations as an append-only, provenance-keyed resource on reports可能重新可做 @anth-volk 于 30 天前认领，目前没有进行中的 PR。 未关闭
PolicyEngine/policyengine-api#3818 · 已指派 1 人 ·
维护者通常 2 天内回复
-
难度 5/5 一周以上 新手友好度 25/100
PolicyEngine/policyengine-api#3816 ·
维护者通常 2 天内回复
查看 PolicyEngine/policyengine-api 的全部 Issue
相似的 Issue
-
难度 2/5 1-3 小时 新手友好度 72/100
Graphify-Labs/graphify#4241 · 1 条评论 ·
维护者通常 1 天内回复
-
难度 1/5 1 小时以内 新手友好度 72/100
-
DeviceTracker未关闭
难度 2/5 1-3 小时 新手友好度 63/100
XiaoMi/ha_xiaomi_home#1821 ·
维护者通常 1 天内回复
-
Maven path-index: "Ambiguous or noncanonical artifact path" error does not report the offending path未关闭
难度 2/5 1-3 小时 新手友好度 76/100
pulp/pulp_maven#524 ·
维护者通常 1 天内回复
-
难度 1/5 1-3 小时 新手友好度 82/100
维护者通常 1 天内回复