
Detect potentially unreliable log patterns
detect_log_anomalies.RdReturns a long evidence table with one row per detected log anomaly. The
function is intentionally conservative: it focuses on structural reliability
signals that can be derived from ordinary Testcenter logs, such as malformed
LOADCOMPLETE rows, player loading/running inconsistencies, connection loss,
unresolved focus loss, runtime errors, timestamp problems, and inconsistent
page counters.
Usage
detect_log_anomalies(
logs,
session_cols = NULL,
unit_cols = NULL,
focus_loss_threshold_ms = 5 * 60 * 1000,
connection_transition_threshold = 10L,
include_unknown_events = FALSE
)Arguments
- logs
Tibble. Logs retrieved with
get_logs()or read withread_logs().- session_cols
Optional character vector with columns defining a test session. By default, all available columns among
group_id,group,login_name,login,login_code, andbooklet_idare used.- unit_cols
Optional character vector with columns defining units. By default, available columns among
unit_keyandunit_aliasare used.- focus_loss_threshold_ms
Numeric. Focus losses longer than this threshold are flagged.
- connection_transition_threshold
Integer. Sessions with more connection state transitions than this threshold are flagged.
- include_unknown_events
Logical. Should event types unknown to eatPrepTBA be returned as informational anomalies? Defaults to
FALSEbecause large log datasets may contain many player-specific entries.