Tony_tech/athena-oracle
3
0
Fork 0
Code Issues 6 Pull Requests 2 Actions Packages Projects Releases Wiki Activity

No failure classification in run_log #2

New Issue
Closed
opened 2026-07-10 15:39:22 +00:00 by Leonard · 2 comments
Leonard commented 2026-07-10 15:39:22 +00:00
Copy Link
Copy Source

Category: Observability · Priority: MED

Summary
pipeline.py records every run to run_log with a free-text notes field. It does not distinguish 4xx (config bug, e.g. bad token) vs 5xx (upstream blip) vs 429 (rate limit). Every failure looks identical.

Why it matters
Without classification, nothing can programmatically decide retry vs fix vs alert. An expired API token (fix now) is indistinguishable from a GitHub hiccup (retry later).

What happens if not done
Operators must read raw logs by hand to diagnose; automation of remediation/alerting (issue #3) is impossible.

Suggested approach
Add a failure_class column (4xx / 5xx / 429 / zero_fetch) populated by the shared retry helper (issue #1). Keep notes for detail.

**Category:** Observability · **Priority:** MED **Summary** `pipeline.py` records every run to `run_log` with a free-text `notes` field. It does not distinguish 4xx (config bug, e.g. bad token) vs 5xx (upstream blip) vs 429 (rate limit). Every failure looks identical. **Why it matters** Without classification, nothing can programmatically decide retry vs fix vs alert. An expired API token (fix now) is indistinguishable from a GitHub hiccup (retry later). **What happens if not done** Operators must read raw logs by hand to diagnose; automation of remediation/alerting (issue #3) is impossible. **Suggested approach** Add a `failure_class` column (`4xx` / `5xx` / `429` / `zero_fetch`) populated by the shared retry helper (issue #1). Keep `notes` for detail.
Leonard commented 2026-07-12 16:33:51 +00:00
Author
Copy Link
Copy Source

Resolved by PR #12 (commit feba2fe). failure_class column added to run_log with values 4xx/5xx/429/error/zero_fetch. Populated by the shared retry helper.

Resolved by PR #12 (commit `feba2fe`). `failure_class` column added to `run_log` with values `4xx`/`5xx`/`429`/`error`/`zero_fetch`. Populated by the shared retry helper.
Leonard commented 2026-07-12 16:41:16 +00:00
Author
Copy Link
Copy Source

Resolved by PR #12 (commit feba2fe). failure_class column added to run_log with values 4xx/5xx/429/error/zero_fetch. Populated by the shared retry helper.

Resolved by PR #12 (commit feba2fe). failure_class column added to run_log with values 4xx/5xx/429/error/zero_fetch. Populated by the shared retry helper.
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
No items
No Label
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
HA_Researcher Ty tonyjbala (Tony Balascio)
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: Tony_tech/athena-oracle#2
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?