Hacktoberfest 2026:维护者为十月标记出来的 issue,仍然开放、适合新手。 浏览 Hacktoberfest issue

Migrate API v1 simulation services to centralized observability

未关闭
#685 0 条评论 0 个 reaction 已指派 0 人 在 GitHub 查看

还没有人认领这个 Issue。

评估

难度
5/5
预计耗时
一周以上
新手友好度
35/100
Issue 类型
重构
描述清晰度
基本清楚
活跃度
活跃
技术栈
google-cloud, python

调研方向

Start by locating the API v1 simulation entry, Modal gateway, executor, and batch workers named in the scope, then inspect their current Logfire and telemetry setup. Review the existing deployment configuration and service-level tests before changing the observability integration. Done means all participating services emit the version 2 schema, preserve allowlisted correlation metadata, contain no Logfire runtime path, and remain unaffected when telemetry fails.

由索引模型根据 Issue 内容生成。

描述

Summary

Migrate the API v1 simulation entry, Modal gateway, executor, and batch workers to policyengine-observability 2.0 and central Google Cloud telemetry.

Scope

  • Replace version 1 global helpers with runtime-bound operations and spans.
  • Remove Logfire initialization, secrets, dependencies, and forced OpenTelemetry disablement.
  • Carry allowlisted request and trace correlation metadata from entry to gateway to worker.
  • Configure explicit service identity, environment, collector endpoint, Google project, and Workload Identity Federation credentials for approved API v1 applications.
  • Add service-level failure-isolation tests.
  • Keep other PolicyEngine applications outside this change.

Acceptance criteria

  • Each participating service emits the version 2 structured log schema.
  • Worker operations restore incoming correlation metadata without including simulation inputs or reform payloads.
  • No Logfire runtime path remains in these services.
  • Failed telemetry setup or export does not change simulation outcomes.
  • Relevant formatting, lint, unit, integration, and deployment configuration checks pass.
主要语言
Python
星标
1
派生
1
平均合并
15 小时 10 分钟
30 天内合并 PR
12

贡献指南

打开贡献指南

从这里开始

  1. 先读完整个 Issue,再读项目的贡献指南。
  2. 在 Issue 下留言说明你要接手 —— 这能避免两个人做同样的事。
  3. Fork 仓库,在一个分支上完成修改。
  4. 提交 Pull Request,并在描述里引用这个 Issue 编号。

PolicyEngine/policyengine-sim-api 的其他 Issue

查看 PolicyEngine/policyengine-sim-api 的全部 Issue

相似的 Issue

更多 Python Issue

把新 issue 发到你的邮箱

精选适合新手参与的 GitHub issue 摘要。