The page listed up to 200 methods and publications on 11 pages. Above the
table there is now one bar per area - Settings, Login, People, Boards,
Cards, Lists, Notifications, Attachments, Problems and the rest - its length
the area's calls against the busiest area's, its red end the share that
failed, with the calls, the average duration and the errors beside it.
Clicking an area shows only its operations in the table; clicking it again
shows all.
models/lib/instrumentationAreas.js groups an operation by the first area
whose pattern matches its name, and weights an area's average duration by
completed calls. tests/instrumentationAreas.test.cjs checks the grouping
against all of WeKan's 614 methods and publications - "Other" holds three -
and the summary arithmetic. The labels are existing translation keys, apart
from the new instrumentation-other ("Other"), translated into every
language. The Finnish "cards" heading read "Korttia" (the form after a
number) in every place it is used as a heading or label; it is "Kortit".
The bars are HTML and CSS, one grid with subgrid rows so names, bars and
numbers line up; the viewport matrix checks the page at every device size.
Thanks to xet7 !
1.3 KiB
Problems / Instrumentation
Open Admin Panel → Problems → Instrumentation to see live Meteor 3.6 instrumentation counters. The page shows DDP connection totals and per-method and per-publication call counts, errors, and average/maximum duration when Meteor supplies a duration. It refreshes every five seconds.
Above the table, one bar per area of WeKan - Cards, Boards, Lists, Login,
People, Notifications, Attachments, Settings, Problems and the rest - gives the
whole picture at a glance: the bar's length is the area's calls against the
busiest area's, its red end the share that failed, and beside it the calls, the
average duration and the errors. Click an area to show only its methods and
publications in the table; click it again to show all. The grouping is
models/lib/instrumentationAreas.js; an operation that fits no area is under
Other, and tests/instrumentationAreas.test.cjs keeps that to a handful of
WeKan's own.
The counters exist only in this WeKan server process. They start when the server starts, reset on restart, and show one process when multiple instances run. Operation names and counts are retained in memory (at most 200 names). Arguments, results, error details, addresses, and user/connection IDs are never retained by this report. Only a site admin can request its snapshot.