Live shows your access log as it is written: one row per request, within about a second of your web server writing it. Every other view is history; this one is what is happening now.
A verdict (human or bot) belongs to a whole visit and is reached once the visit is scored. So no row on Live carries a verdict. The last column says only what this one request shows: a crawler name in the User-Agent, a path that matched an attack pattern, an image rather than a page.
- As it happens: the table, with Time, Host, Client address, Request, Status and Client. It keeps the last 300 requests.
- A requests-per-second chart above the table, and a status line: Connecting, Streaming, Reconnecting or Paused, with how much of the log is not read yet and how many lines could not be parsed.
- Pause stops the stream; Resume picks up where it stopped, so nothing that arrived in between is skipped.
- Files being read, folded at the bottom: each log file, the host it is pinned to, its format and whether the panel can read it.
Open a row to see everything about it: the request (path, query string, status, bytes, time the server took, search terms), the client (address, browser, operating system, device, whether it says it is a crawler, TLS), where it came from (referrer and how it counts), what the line shows, and what the index already knows about this address: verdicts from its visits that have already been scored.
- The filter box hides rows already on screen by host, address, path, status or client.
- Exclusions opens the live rules: four built-in groups (images, scripts and other assets; crawl files such as
robots.txtand sitemaps; machine endpoints such as/api/and.json; Loghound’s own beacon) and rules of your own. A hidden request never reaches your screen. - Nothing here changes what is stored. Every hidden request was recorded in full and is in every other view. To refuse requests for good, use Exclusions in Settings. Live rules export and import as a file: Rule lists as CSV.
Live reads your log files directly and read-only, through the same safety checks as the reader. It never moves the reader’s place in a file. The website selector filters the parsed lines, because one file can carry several websites.
Overview & Live
- Overview
- Live