feat: system coverage, deploy verdicts and incidents
メンテナーはふだん 1 日以内に返信
まだ誰も着手していません。
評価
- 難易度
- 5/5
- 見積もり時間
- 1週間以上
- 初心者へのやさしさ
- 25/100
- issue の種類
- 機能追加
- 明瞭さ
- おおむね明確
- 活発さ
- 活発
- 技術スタック
- go
調査の方向性
Start with the existing System overview dashboard, deploy markers and split, alert rules, webhook delivery, and email sending described in the issue. Then trace how Fanout accepts and processes OpenTelemetry data, and review the Collector receiver and CI/CD semantic convention details referenced here. Done means the database, queue, and TLS panels, deploy verdicts, panel alerts, incidents, and email delivery work end to end as listed; the issue says each part ships separately.
索引モデルが issue の本文から書いたものです。
説明
Goal
Fanout becomes the one place to see a whole system and act on what goes wrong in it. It keeps doing only what it does today — accept OpenTelemetry data and do everything after that — and builds on what already exists: the System overview default dashboard, deploy markers and the deploy split, alert rules with webhook delivery, and Fanout's email sending.
Principle
The boundary is the input, not the feature set. Telemetry arrives only as OpenTelemetry, a standard, so anything that sends OTLP works without a Fanout integration. On top of that data Fanout should be rich and full-featured: dashboards, analysis, alerts, deploy verdicts and incidents all belong here.
1. More of the system on System overview
Recognise standard Collector receiver output and present it, with no per-source integration in Fanout:
- Databases and queues from the
postgresql,mysql,redisandkafkametricsreceivers: connections, slow or failed queries, replication lag, consumer lag. Panels appear when their data exists and their descriptions name the receiver otherwise. - TLS certificate expiry from the
tlscheckreceiver: days until expiry per endpoint, bad when close. - The Send telemetry guide gains the receiver configuration for each.
2. Know what changed, and whether it broke something
- Real change events. Accept deploys and pipeline runs that arrive as OpenTelemetry data (the CI/CD semantic conventions, or the Collector's
githubreceiver) and draw them as deploy markers, alongside today's markers inferred from a newservice.version. - A verdict for each deploy — pass, fail or inconclusive — from the existing before-and-after deploy split, shown on the marker and in the System overview versions table.
3. Act on problems: incidents on top of alerts
- Alerts on dashboard panels, so a System overview panel turning bad (a filesystem above 90%, a host not reporting, a check with no recent result) can fire. Today alert rules see only per-service span and log rollups.
- Incidents: a firing alert opens one, with acknowledgement, an owner, and a timeline that includes nearby deploys; it is recovered only once the alert has stayed resolved.
- Email notifications next to webhooks, using the email sending Fanout already has.
Out of scope
Performance work (a scale benchmark, per-minute summaries, faster metric queries), AI and API cost tracking, and checks run by Fanout itself — Fanout does not gather or probe.
Done when
- A Collector with the receivers above produces database, queue and TLS-expiry panels on System overview, verified end to end through OTLP.
- A deploy event arriving as OpenTelemetry data appears as a marker with a pass, fail or inconclusive verdict.
- A panel-based alert opens an incident, it can be acknowledged and assigned, and it closes only after recovery holds; email and webhook delivery both work.
Each part ships on its own, in this order.
- 主要言語
- HTML
- スター
- 6
- フォーク
- 0
- 平均マージ
- 2時間 25分
- マージ済み PR（30日）
- 25
環境構築
- Dockerfile または Docker Compose ファイルあり
- プルリクエストのテンプレートあり
- コントリビューションガイドを読む
はじめの一歩
- issue を最後まで読み、次にプロジェクトのコントリビューションガイドを読みます。
- 着手することを issue にコメントします — 二人が同じ作業をするのを防げます。
- リポジトリをフォークし、ブランチを切って変更します。
- issue 番号を参照したプルリクエストを送ります。
labstack/fanout のほかの issue
-
bug
難易度 2/5 1〜3時間 初心者へのやさしさ 78/100
メンテナーはふだん 1 日以内に返信
-
難易度 5/5 1週間以上 初心者へのやさしさ 35/100
メンテナーはふだん 1 日以内に返信
-
難易度 4/5 3〜5日 初心者へのやさしさ 45/100
メンテナーはふだん 1 日以内に返信
-
難易度 5/5 1週間以上 初心者へのやさしさ 42/100
メンテナーはふだん 1 日以内に返信
-
難易度 5/5 1週間以上 初心者へのやさしさ 25/100
メンテナーはふだん 1 日以内に返信
labstack/fanout の issue をすべて見る
似ている issue
-
Notifications pagination accepts NaN and negative LIMIT/OFFSET対応中かも @Senthil455 が今日担当しました。 オープンBUGS MEDIUM
難易度 2/5 1〜3時間 初心者へのやさしさ 62/100
elixpo/blogs.elixpo#419 · コメント 2 件 ·
メンテナーはふだん 1 日以内に返信
-
[Bug]: agent_final_response still returns the abandoned branch's answer after navigate moves HEAD back対応中かも @enyst が今日担当しました。 オープンbug priority:low ready-for-dev
難易度 2/5 1〜3時間 初心者へのやさしさ 72/100
OpenHands/software-agent-sdk#5822 ·
メンテナーはふだん 1 日以内に返信
-
area: server enhancement good first issue
難易度 2/5 1〜3時間 初心者へのやさしさ 82/100
scs0209/laya-guard#52 ·
メンテナーはふだん 1 日以内に返信
-
priority:high
難易度 2/5 1〜3時間 初心者へのやさしさ 72/100
メンテナーはふだん 1 日以内に返信
-
難易度 2/5 1〜3時間 初心者へのやさしさ 72/100