Skip to main content

Logs import concept

This page explains how log data moves from your game server into dzbot, why delays can happen, and which features depend on this data.

What "logs import" means​

dzbot reads server log files from Nitrado and converts them into structured events.

Those events are then used across the platform (for example in Log Explorer, map activity, kill/damage feed, and other automation features).

How the flow works (simple view)​

  1. A gameplay event happens on your server.
  2. Nitrado writes that event to server log files.
  3. dzbot checks those log files on a recurring schedule.
  4. New/changed content is imported and processed.
  5. Features that rely on logs update after processing.

In production deployments, the import check typically runs very frequently (usually every minute).

Why data can appear later​

This system is near-real-time, not instant.

Common delay sources:

  • Nitrado/source logs may not be available immediately
  • Fresh log lines can arrive later than the original gameplay moment
  • Busy periods can increase processing delay

What this means in practice:

  • Many updates appear quickly
  • 10-20 minute delays are normal in some situations
  • 30-60 minute delays can happen, especially during high load or upstream lag

For investigations, allow a short buffer before assuming data is missing.

Data freshness basics​

  • "Last updated" means when dzbot received/processed the data.
  • It does not always mean "the event just happened now".
  • Very recent windows can be incomplete while late records are still arriving.

Why this matters for daily operations​

If logs are delayed, every log-driven feature can look delayed too.

That is expected behavior and usually self-corrects as new imports finish.

Features that depend on logs import​

The following areas use imported logs data directly:

  • Admin Log Explorer
  • Embedded log explorer in player details
  • Log Requests result views
  • Kill Feed and Damage Feed
  • Map activity layers (player positions, bounty target positions, related overlays)
  • Player routes and contact analysis in admin player details
  • Position-based onboarding checks and player sync behavior
  • Coordinate picker source From placements
  • Actions that trigger on imported log events
  • Base alarm timelines and nearby activity context

Operational expectations for admins​

  • Use imported logs as the source for audit/review workflows.
  • For fresh incidents, re-check after a short wait.
  • For moderation decisions, prefer a slightly wider time window to absorb ingestion delay.