Skip to content

Browsing logs on the dashboard

Discord is where your logs arrive; the dashboard is where you search them. Open app.logdog.gg, pick your server, and you get two log pages:

  • VRChat Audit Logs: everything LogDog pulled from your VRChat group's audit log (joins, bans, kicks, instances, roles, calendar events, posts).
  • LogDog Activity: everything done through LogDog (settings, moderation from Discord or the dashboard, playlists, events), including what LogDog did on its own.

Both pages are ledgers: rows grouped by day, a short line per event, and a drawer with the full story when you click one.

Who can see them

Both pages need the Manager level on the dashboard (the same access as the other dashboard pages). Editing a reason from the dashboard needs Admin.

VRChat Audit Logs

Each row shows the time, the event, the actor (who did it), the target (who or what it happened to) and a context line: the reason on a ban, the world an instance was opened in, a role that was given, the outcome of a join request. A thin colored edge marks the severity, the same colors as the Discord embeds.

Names are links: a VRChat user opens their moderation history page, a world opens its world page, a calendar event opens the event, a role opens Role Sync.

Finding things

  • Time range chips (24h, 7 days, 30 days, 90 days).
  • Category and Event type dropdowns, straight from your routing catalog.
  • Search across names, worlds and ids: a user's display name, a world's name, a usr_ or wrld_ id, a post or event title.
  • More filters: actor, target and delivery (sent, failed, pending, skipped). Active filters show as chips you can remove one at a time; Clear keeps the time range.
  • Export CSV downloads the filtered list.

The drawer

Click a row and a drawer opens on the right with the whole event. The address bar carries ?x=<id>, so the link is shareable, Back closes it, and the arrow keys walk the list.

What it holds, top to bottom:

  • The sentence (ForgeMod_Ada kicked LoudLad42), the event type, where it happened, and the date and time.
  • Actions: Open in Discord, Add or Edit reason, Full history, Instance stats, World page, Open the event, Role Sync (whichever apply).
  • Reason, with who added it and where (in Discord or on the dashboard).
  • About the user: trust rank, age verification, account created, Discord account (or Not linked), member since, and this group's counts (warns, kicks, bans, requests, denied).
  • User history: the last few events on that user in your group, with a Full history button.
  • The object: The instance (world, access, region, capacity), This session (open for, peak, last count, last visited, with an Instance stats button), The event, The role, The request, or the post.
  • A delivery problem box only when the Discord post did not happen, with what to do.
  • Also on this event: what LogDog did on it (a reason added, a ban requested, a request approved).
  • Two folds: The Discord message as it was posted, and Details for support (ids and timings to paste into a support post).

Open event page (the icon in the drawer bar) shows the same blocks on their own page at /audit-logs/<id>, with a Copy link button (the link to send to a colleague) and Newer / Older buttons that walk the ledger, with a "N of M in the last 7 days" counter for recent events.

Editing a reason from the dashboard

On a ban, kick, warning, removal or denied request, Add reason / Edit reason in the drawer writes the reason to the Discord message too: the embed gains (or updates) its Reason field and the button reads Edit reason. Reasons added from Discord and from the dashboard are the same reason; the drawer says which one it came from. See Reading your logs for the Discord side and reason presets.

LogDog Activity

The same ledger for what your team and LogDog did through LogDog: Who, What (Added a world to Game night, Turned off an event, Changed a reason), the Target (linked to the world, user, playlist, event or VRChat event it was about), the Change (now Off ยท was On, the new reason, the previous channel), and the Result (Done, Failed, Partly done).

Rows LogDog did on its own (automatic event worlds, background jobs) are tinted and read LogDog in the Who column. The Who dropdown filters to Users only or LogDog only; More filters adds the user, the source (dashboard, slash command, automation) and the result.

Clicking a row opens the drawer:

  • The sentence (Plaz5 changed a reason on GriefWolf77's ban), the result, how it was done (from the dashboard, with a slash command, automatically) and when.
  • What changed: labelled lines with the old value struck through, when LogDog recorded it.
  • What happened, on a failure: the cause in plain words.
  • What LogDog did: the follow-on work, one short line each (Updated the message in #mod-log).
  • Around the same time: the same user's other changes within ten minutes, linked.
  • Go to: the pages this record touches.
  • Details for support, folded.

Each record also has its own page (the drawer's Open event page icon, or a shared /activity/<id> link), with the same Newer / Older walking as the audit event page.

Older records

Records from before LogDog Activity existed (the /auditlog era) still show, marked older record, with the target and action but no before/after values.

Dates and times

Every time on both pages follows your settings: the time zone (detected from your browser unless you override it), and a Date format and Time format you can set on the dashboard's Settings page under Personal preferences (Auto follows your browser's locale). Within the last seven days a time reads relatively (12 min ago, 3 hr ago); older than that it is the date. Hover any time for the full date and time.