Error in FleetWatch

Open
  • Is something wrong?
#7,896 9 comments 0 reactions 0 assignees View on GitHub

Maintainers usually reply within 1 day

Nobody has claimed this yet.

Assessment

Difficulty
5/5
Estimated time
Over a week
Newbie friendliness
15/100
Issue type
Bug
Clarity
Needs clarification
Activity status
Active
Tech stack
csharp
Domain
backend

Research direction

Start by inspecting the FleetWatch log site 8ee9e0785e83a261 and the incident details at Admin/_LogIncident/2c3d636ea6808973 on the affected instance. The report says triage text is not published because LogWatch:PublishTriageDraft=false, but gives no source file, reproduction steps, or expected fix; determine what owns this setting and how triage drafts should be published before estimating completion.

Written by the indexing model from the issue text.

Description

bug sev:H

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 2c3d636ea6808973
Category FleetWatch
Severity Error
Namespace memex 1 occurrence(s), 2026-11-04 21:21:19Z → 2026-11-04 21:21:19Z; pods memex-portal-deployment-67cf6d965c-l2s46
Occurrences 1
First seen 2026-11-04 21:21:19Z
Last seen 2026-11-04 21:21:19Z
Routing not determined — no configured route matches the category FleetWatch. 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-11-04 21:21:19Z memex-portal-deployment-67cf6d965c-l2s46

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

This log site's previous ticket, https://github.com/Systemorph/MeshWeaver/issues/7886, 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/2c3d636ea6808973. Recurrences are folded into this issue rather than opening new ones.
It also stands for the whole log site 8ee9e0785e83a261: other fingerprints of this site fold in here as comments rather than opening tickets of their own.

Dominant language
C#
Stars
12
Forks
5
Avg merge
5h 10m
Merged PRs (30d)
981

Getting set up

  • No Dockerfile or Docker Compose file
  • Has a pull request template
  • No contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from Systemorph/MeshWeaver

All issues in Systemorph/MeshWeaver

Similar issues

More C# issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.