Date: 2026-09-25 Status: Proposed, Update Requested, may do it, probably not, is likely to be candidate for what would be Scheduled agents. or Schedules in general. like [[ADR-028-Schedules]], Isn't ADR-28 actually the thing that want's to be used? like the way this feature is now, today, it seems like a simple weekly schedule, like, i cant even interact with this, or it doesnt feel like it, or its not intuitive, and the feat is broken somehow anyways, or its not clear that sentry isnt healthy, and . well, i could keep going at this. So, yeah, should this really ever have been an ADR ? it;s like very user dependent as well, not all Node operators would want the weekly Node health mail, so...
brandon: "so, i do receive the e-mail, but there are errors in there about trying to reach sentry or something, so. yeah, and also, i do feel like the NODE Agent should be receiving this as well, so i receive it, and the NODE Agent at the same time, so, while it is working on it, i have a chance to direct it while it's going through some kind of weekly analysis. And this should by like, Dynamic, and, I guess as a USER i want to be able to interact with this and set it change the prompt, etc, in the Agent Element"
"let's say QNTX also has it's own built in messages it would like to send sometimes via email"
"for a user that is one of the root identities, i want to receive a weekly report." "y attestations got created per namespace" "x users registered per namespace" "z node restarts" "downtime over last week" "downtime over last 3 weeks" "CPU over 7 days graph" "MEM over 7 days graph" "boot.subsystem.took over 7 days" "7d total host.net.in" "7d total host.net.out" "query took over 7d, top three slowest query" "host swap over 7d graph" "top 3 4xx, top 3 5xx" "top 3 handler failures" "can you do it please to the degree that is feasible given sentry access?"
"I WANT TO SEE THE THREE MOST FREQUENTLY OCCURING ONES" "AND FOR HANDLER THE SAME" "I WANT TO SEE WHAT WAS TRIED TO ACCESS INSTEAD"
auth.User Namespace and CreatedAt), restarts (node:started),
handler failures (failed Pulse jobs).