30 releases 32 tags

RSS feed

• v0.10.2 97f2a40624

  Compare

  v0.10.2 — Portainer-readable log field names Stable

  joeyr released this 2026-07-31 19:57:51 -05:00 | 236 commits to main since this release

  The nightly logs now render in colour in Portainer. They were emitting under
  field names the dashboard does not read, so every line arrived as an
  undifferentiated wall: no colour on the level, and no subject until the end.

  Portainer's JSON log viewer recognises exactly five keys — time, level,
  caller, message, stack_trace — colours those, and prints everything else
  as trailing key=value. Two of ours were named past it:

  • level was uppercased to INFO/WARN/ERROR. The viewer matches it
    case-sensitively against debug/info/warn/error, so every level fell
    through to an uncoloured default. This amends 0.5.0, which uppercased it to
    stop a bare 30 rendering where the severity should be. That problem was
    real and stays fixed — the level is still a name — but the fix overshot by
    one character class and cost the colour. pino's own labels are already the
    lowercase names Portainer wants.
  • the log text sat under pino's default msg, an unknown key, so it sorted
    in among the fields rather than leading the line. It is now message.

  time also moves from epoch milliseconds to a local 2026-07-31 09:09:03
  string. Portainer renders a numeric time through Y/MM/dd hh:mmaa — 12-hour
  and with no seconds — which drops exactly the resolution this service paces
  itself in (2.5s between Riot calls, 12.5s between op.gg ones). Local rather
  than UTC because every window here is local already.

  The logger tests now assert the invariant rather than the literal strings: the
  level must be one of the four values the dashboard colours.

  Cosmetic, and confined to the dashboard: no artifact, schema, or published file
  changes, and docker service logs is unaffected either way.

  Downloads

  • Source code (ZIP)
    0 downloads
  • Source code (TAR.GZ)
    0 downloads