You are reading the documentation for v1.3.0. The current release is v1.4.0. Go to the latest version of this page →

How to see that it is happening

Withholding is reported, not silent. GET /api/bng/audit/shipping/status
returns the daemon's per-destination snapshot, and each destination carries:

field means
entries_withheld how many entries this destination did not get
withheld_by_source the same, broken out per source
opt_in_sources which withheld sources this destination is opted into
withheld_note the plain-language reason, empty when nothing was held

So the operator asking "why does my SIEM have no RADIUS entries?" reads:

"corp-siem": {
  "entries_shipped": 412,
  "entries_withheld": 37,
  "withheld_by_source": {"radius-exchanges": 37},
  "opt_in_sources": [],
  "withheld_note": "37 from radius-exchanges: withheld because these entries
    carry subscriber identifiers and this destination has not opted in. They
    are still in the local audit log and on the operator timeline. To ship
    them, add "radius-exchanges" to this destination's opt_in_sources."
}

The same numbers are on the destination's row in Settings → Audit
shipping
: a destination that had entries held back carries a N withheld
chip whose tooltip is the note above, and one that is opted in says so.

The counters run from the last time the destination list was loaded, and they
count entries the tail handed to that destination — a destination added
after a burst of RADIUS entries will report zero, because it was never offered
them.