Exclusions are requests Loghound never records at all. A matched request is not stored as a hit, not folded into a visit, not counted anywhere, and it cannot be recovered later, because nothing was written down.
To tidy what you watch without losing anything, use the filters on the Live page instead: they hide requests from the live stream and store everything. See Live.
- Open Settings › Exclusions.
- In the empty row, pick a Hostname, or leave every host for a rule that applies everywhere.
- Pick a Field: Request path, Client address, User-Agent, Client, Method, Status, Query string or Signed-in email.
- Type the Pattern: a regular expression with no slashes and no flags. Matching ignores case.
- Press Save exclusions. The card shows how many rules are in force.
- The pattern
*on Request path excludes a hostname entirely. It is the only place a bare star means anything. - Method, Status and Client only apply to traffic read from your access logs. A beacon report carries none of them.
- Both planes are covered: the reader applies the rules to every log line, and the beacon collector to every report.
- The beacon collector uses a change at once. The reader uses it from its next restart or reload.
- Untick On to pause a rule without deleting it; tick Remove to delete it.
Signed-in email is the one field that takes an exact address instead of a pattern, matched without regard to case, for every host or for one. It is how you keep your own visits out of your numbers.
- Make your site pass the signed-in visitor’s email to the beacon in
data-ident. Identity & signed-in shows how. - Add a rule with the field Signed-in email and your address as the pattern.
- Let the beacon run in your own browser: switch off any blocker for your own site, or there is nothing to match.
When a beacon report carries that address, from a site this installation measures, the whole visit it belongs to is excluded on both planes. Nothing more of it is written, and what the reader had already written for it is deleted within a minute. Only that one visit is touched, so a forged address can hide nothing but the forger’s own visit.
Rules travel between installations as a CSV file: Rule lists as CSV.