Logger and Logs

Where every dirk script's log lines are kept, read back, and sent on.

---

#📝 Logger

Pick where dirk scripts that log send their entries. As well as a Discord channel webhook, you can route logs through an external logging service — Loki / Grafana, Datadog or Fivemanage — and any dirk script that logs (fishing included) then flows through it. Discord and an external service can run side by side.

Service credentials are server-only — they never leave the server and are never sent to clients.

Scripts no longer carry their own webhook settings; an existing one is carried over the first time the script loads. Reading those lines back, and choosing what is sent on to Discord, is the Logs page below.

---

#🗒️ Logs

The Logs page has three tabs.

Events is every log line every dirk script has written, newest first, filtered and paged on the server so a busy table stays quick. Pick a script down the left, then narrow by player, event, level or time — and open any line for the full payload, including all of that player's identifiers rather than just the server ID they happened to have at the time.

Config changes is the audit trail for the panel itself: every saved edit, who made it, and the value before and after. Each line can be reverted, which stages the change for you to review and save like any other edit.

Delivery is where those lines go. Keeping them on this server is what the Events tab reads, and retention decides how long a line survives — older rows are deleted hourly in slices, so a long-idle server does not lock the table catching up.

Under that, redirects send matching lines on to Discord as well as keeping them here, never instead. A redirect can post to a webhook URL or to a channel your bot posts in, and can be filtered by script, event or level — so anticheat warnings can go to one channel while everything else goes to another. Messages are batched, so a busy minute is a few posts rather than hundreds.