Critical in LogWatcher.Pipeline

Aperta
  • Qualcosa non va?
#7,956 0 commenti 0 reazioni 0 assegnatari Vedi su GitHub

I maintainer di solito rispondono entro 1 giorno

Nessuno ha ancora preso questa issue.

Valutazione

Difficoltà
4/5
Tempo stimato
3-5 giorni
Idoneità per principianti
20/100
Tipo di issue
Bug
Chiarezza
Da chiarire
Stato di attività
Attiva
Stack tecnologico
csharp
Ambito
backend

Direzione di ricerca

Start by locating the MeshWeaver.LogWatcher.Pipeline logger and the code that reads log lines for triage. The issue says the triage text is not published because LogWatch:PublishTriageDraft=false, but gives no file, test, or expected change. Determine how that setting and incident-node publishing are intended to work; done means the triage write-up reaches the intended destination without publishing raw log lines.

Scritto dal modello di indicizzazione a partire dal testo della issue.

Descrizione

bug sev:M

The triage write-up stays on the incident node: the agent reads the raw log lines, so its text is not published (LogWatch:PublishTriageDraft=false).

Evidence
Fingerprint log-window-skipped-memex-cloud
Category MeshWeaver.LogWatcher.Pipeline
Severity Critical
Namespace memex-cloud 1 occurrence(s), 2026-11-07 01:18:06Z → 2026-11-07 01:18:51Z; pods
Occurrences 2
First seen 2026-09-27 11:02:50Z
Last seen 2026-11-07 01:18:51Z
Routing not determined — no configured route matches the category MeshWeaver.LogWatcher.Pipeline. This repository is the configured fallback, not a finding about who owns the fault; the category names the LOGGER, which may not be the subject.
Recent sightings
Logged at Pod
2026-09-27 11:03:19Z -
2026-11-07 01:18:51Z -

The log lines themselves are not published: formatted log text can carry the values a call site logged. They stay on Admin/_LogIncident/log-window-skipped-memex-cloud on the instance that recorded them.

This log site's previous ticket, https://github.com/Systemorph/MeshWeaver/issues/7043, was closed about a different fingerprint, and this fault fired after that close. It is left closed: an occurrence of this fingerprint is no evidence that the fault it was closed for came back. This issue now tracks the log site, and later fingerprints of it fold in here.

Opened automatically from Admin/_LogIncident/log-window-skipped-memex-cloud. Recurrences are folded into this issue rather than opening new ones.
It also stands for the whole log site df7022d82cca1b39: other fingerprints of this site fold in here as comments rather than opening tickets of their own.

Lingua principale
C#
Stelle
12
Fork
5
Merge medio
5h 11m
PR unite (30g)
978

Preparare l'ambiente

  • Nessun Dockerfile né file Docker Compose
  • Ha un modello di pull request
  • Nessuna guida per i contributori

Come iniziare

  1. Leggi tutta la issue e poi la guida ai contributi del progetto.
  2. Commenta sulla issue per dire che te ne occupi tu — evita che due persone facciano lo stesso lavoro.
  3. Fai un fork del repository e lavora su un branch.
  4. Apri una pull request che faccia riferimento al numero della issue.

Altre issue di Systemorph/MeshWeaver

Tutte le issue di Systemorph/MeshWeaver

Issue simili

Altre issue su C#

Ricevi le nuove issue nella tua casella

Un breve riepilogo di issue GitHub adatte ai principianti.