Thore CimbalandClaude Opus 5
a1def8666e
ADR-0012 made docs/issues/ canonical for the management scope only and left gitops, ThreadNet-Web and threadnet-call on GitLab "until the component adopts". That split produced exactly what it invited: two numbering worlds where management#20 and gitops#20 are different issues, drift nobody had to answer for (gitops#61 carried no milestone since 2026-08-11), and component backlogs that host sessions without lab access cannot read at all. The 46 open component issues are now files 0056-0101. The file id is the group-wide identifier; provenance lives in the frontmatter (new field `projekt` plus gitlab_iid) and in the filename, so "gitops#61" still finds 0091. Bodies are copied verbatim; comments and history stay on GitLab, as with the 2026-08-11 management import. Both scripts learned the second dimension: spiegel_issues.py routes each file to its origin project, reopens issues that are open in the repo but closed on the board, and writes the new iid back after creating one; gruppenpruefung.py checks drift across all four trackers instead of management alone. What the mirror cannot decide stays a finding, not a silent state. Two things needed a hand, both recorded in the files: gitops#61 had no milestone (M1 - it is a live account-takeover path) and carried two area labels where the schema holds one. The Gitea migration footers in the imported bodies point at decommissioned trackers; their links are removed, the provenance sentence stays. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
1.3 KiB
type, id, status, created, milestone, priority, area, projekt, gitlab_iid, related
| type | id | status | created | milestone | priority | area | projekt | gitlab_iid | related |
|---|---|---|---|---|---|---|---|---|---|
| issue | 0077 | open | 2026-07-29 | M1 | low | infrastructure | gitops | 42 |
Grafana-Dashboard für ClamAV-Scan-Ergebnisse (Issue #19)
Adoptiert aus gitops#42 (2026-08-18, ADR-0019). Kommentare und Verlauf bleiben dort; kanonisch ist ab jetzt diese Datei.
Wunsch aus Issue #19-Tests: sichtbar machen, wie oft ClamAV tatsächlich etwas blockiert
(bisher nur in Synapse-Logs sichtbar: clamav_spam_checker - WARNING - ClamAV rejected an upload: <signature>).
Da Alloy bereits alle Pod-Logs nach Loki schickt (10.0.0.3:3100, siehe
docs/deployment-guides/03-monitoring-integration.md), braucht es dafür keine neue
Instrumentierung - nur ein neues Grafana-Dashboard/Panel mit einer LogQL-Query auf
{app="synapse-main"} |= "ClamAV rejected" (Anzahl über Zeit, evtl. Tabelle mit erkannten
Signaturen). Optional zusätzlich: ein Panel für Scanner-Ausfälle (ClamAV scan failed -
fail-open-Fälle, die sonst unbemerkt blieben).
Kein Server-seitiger Code nötig, rein Grafana/Loki-Dashboard-Arbeit.
Migriert aus Gitea sorb/axion1337.chat-gitops#43 — dort erstellt am 2026-07-29 von sorb.