Skip to main content

Log Explorer

This page documents the full log explorer workflow in the admin area:

  • Log Explorer page in admin
  • Embedded log explorer in player details
  • Log Requests workflow

Data source note: all results here depend on imported server logs. For freshness behavior and delay expectations, see Logs import concept.

Access requirements​

Rights used in this area:

  • logs.view -> open and use Log Explorer
  • log_requests.view -> open Log Requests and view request details
  • log_requests.create -> create new log requests
  • log_requests.approve -> review, approve, and reject requests

Access scope notes:

  • Viewing player detail (including embedded logs tab) also requires players.view.
  • Opening request detail after creation requires log_requests.view.
  • Without log_requests.approve, request details are limited to your own requests.

Admin Log Explorer page​

Navigation path:

  • Server Admin -> Log Explorer

Available filters​

  • Position (X, Z) with radius distance (see Coordinates)
  • Time window (Start time, End time)
  • Log types (multi-select)
  • Players (multi-select)

Position filter rule:

  • Position filtering is applied only when both X and Z are set.
  • If distance is empty while X and Z are set, default distance is 100.

Result view​

Each row contains:

  • Time
  • Player
  • Type
  • Event details
  • Position (linked map location when coordinates exist)

Data window and paging​

  • Default start time is last 7 days.
  • End time is optional.
  • Default page size is 50 entries.
  • Maximum page size is 250 entries.

Embedded Log Explorer in player details​

Navigation path:

  • Server Admin -> Players -> Open player -> Log entries tab

When this tab is shown​

The tab appears only if all conditions are met:

  • logs.view is granted
  • server subscription is active
  • at least one related username exists for log filtering

Embedded player logs are scoped to related usernames built from:

  • the player username
  • usernames of players linked through shared devices

Player filter options in this tab are limited to this related-username set.

Embedded filters and results​

The embedded view supports the same filter model as global Log Explorer:

  • position + distance
  • time window
  • types
  • players (limited to related usernames)

If no player filter is selected, the embedded view uses all related usernames.

Position filter rule:

  • Position filtering is applied only when both X and Z are set.
  • If distance is empty while X and Z are set, default distance is 100.

Embedded data window and paging​

  • Default start time is last 7 days.
  • End time is optional.
  • Default page size is 50 entries.
  • Maximum page size is 250 entries.

Log Requests​

Navigation path:

  • Server Admin -> Log Requests

Request list behavior​

  • Users with log_requests.view can open the page.
  • Users with log_requests.approve see all requests plus a dedicated pending-approvals block.
  • Users without log_requests.approve see only their own requests.
  • Request statuses: pending, approved, rejected.

Creating a request​

Requires log_requests.create.

To open the created request details page immediately after submit, log_requests.view is also required.

Request form fields:

  • Reason (required)
  • Start time and end time (required)
  • Optional Discord channel
  • Optional position + distance filter
  • Optional types filter
  • Optional players filter

Position filter rule:

  • Distance is only stored when both X and Z are set.

Time rules:

  • End must be after start.
  • Maximum window is 48 hours.

Request detail and review​

The request detail page shows:

  • status, requester, created time
  • requested time window
  • reviewed by / reviewed time (after review)
  • optional position filter and distance
  • reason
  • optional Discord channel
  • optional reviewer note

Review actions (requires log_requests.approve):

  • Approve request
  • Reject request
  • Update filters before approval (time, position/distance, types, players)
  • Set reviewer note

Approval update rules:

  • Position filter update requires both X and Z.
  • Clearing position filter requires both fields to be empty.

Only pending requests can be approved or rejected.

Logs in request detail​

  • Logs are shown only when request status is approved.
  • Pending/rejected requests do not expose log results.
  • Approved requests use the stored request filters to build the result set.
  • Result table uses the same event-detail rendering as the main Log Explorer.