httptop
Watch the most frequent recent HTTP requests from the access log in a live terminal view, with an optional text filter
- Command:
/go/httptop - Category: Monitoring
- Required arguments: None
- Output: Live terminal display, refreshed every 2 seconds
- Last updated: 2026-11-20
On this page: Overview · Quick start · Syntax · Arguments · Output · Examples · Troubleshooting · Details · See also
Overview
/go/httptop shows what your web server is being asked for right now. It:
- reads the newest lines of the server's access log
- counts identical requests and shows the 20 most frequent
- redraws the screen every 2 seconds
- can narrow the view to lines containing a word, such as a domain, IP address, or URL part
It is read-only. It changes nothing on the server, and it is a quick way to spot a request that is repeating far more than normal, such as a login page being hammered. Every run is logged to /var/log/go/httptop.log.
Quick start
# Watch the busiest recent requests across all sites
/go/httptop
Press Ctrl+C to quit.
Syntax
/go/httptop [filter]
| Form | Behavior |
|---|---|
/go/httptop |
Counts the last 200 log lines. |
/go/httptop <filter> |
Keeps only lines that contain <filter>, then counts the last 100 of those. |
Arguments
| Position | Argument | Required | Notes |
|---|---|---|---|
| 1 | filter |
No | A text pattern matched against the whole log line (domain, IP, URL, method, user agent). Only the first argument is used. See Filter rules. |
Filter rules
| Rule | Detail |
|---|---|
| Matching | Uses grep, so the filter is a regular expression. In 203.0.113.5, each dot matches any character. |
| Scope | Matches anywhere in the line, not only in the columns that are displayed. |
| Case | Case-sensitive. |
| Several words | Wrap them in quotes so they count as one argument: /go/httptop "wp-login.php". |
Output
The screen shows a clock box, then up to 20 result lines.
┌─────────────────────┐
│ 2026-11-20 14:03:07 │
└─────────────────────┘
48 example.com GET /wp-login.php
31 example.com POST /xmlrpc.php
12 shop.example.net GET /products?page=2
...
The sample above is illustrative. Each result line has these parts:
| Part | Meaning |
|---|---|
| Number | How many times that exact line appeared in the sample. |
| Next field | The second field of the pipe-separated log line. |
| Request | The request field (field 11): method and URL, with HTTP/2.0 removed. |
Lines are cut at 125 characters, and the list is sorted with the highest count first.
Examples
# All sites, last 200 requests
/go/httptop
# Only requests for one domain
/go/httptop example.com
# Who is hitting the WordPress login page?
/go/httptop wp-login.php
# Only POST requests
/go/httptop POST
# Requests from one IP address
/go/httptop 203.0.113.5
Troubleshooting
| Symptom | Likely cause | Fix |
|---|---|---|
| Blank list under the clock | No log lines match the filter, or the log is empty. | Run without a filter, or check the spelling of the filter. |
| Slow to start | It looks up the server's public IPv4 and IPv6 addresses before the first screen. | Wait a few seconds. A server with no internet or IPv6 access can wait longer. |
| It stopped by itself | The loop runs 1,000 times at about 2 seconds each, so roughly 33 minutes. | Run the command again. |
A multi-word filter is ignored or prints a [[ error |
The words were not quoted. | Quote the filter: /go/httptop "two words". |
| IP filter shows unrelated lines | Dots in the filter are wildcards. | Escape them: /go/httptop 203\.0\.113\.5. |
| Requests that differ only in letter case are merged | Counting ignores case, but URLs are case-sensitive. | Treat counts as approximate, or check the raw log. |
| Not the whole picture | It only samples the newest 100 or 200 lines, so a busy server covers only seconds of traffic. | Use iptop, usertop, or sizetop for wider reports. |
Details
What it does
flowchart TD
A["/go/httptop [filter]"] --> B["Append the command to /var/log/go/httptop.log"]
B --> C["Look up the server's IPv4 and IPv6"]
C --> D{"Filter given?"}
D -- "Yes" --> E["Keep matching lines, last 100"]
D -- "No" --> F["Last 200 lines"]
E --> G["Keep field 2 and field 11"]
F --> G
G --> H["Count identical lines, top 20"]
H --> I["Clear screen and print"]
I --> J["Wait 2 seconds"]
J --> D
Steps in order
- Appends a timestamped line with the arguments to
/var/log/go/httptop.log. - Loads the helper functions from
/go/functionto find the access log. - Looks up the server's public IPv4 and IPv6 addresses.
- Starts a loop of up to 1,000 refreshes. Each refresh:
- Reads the newest log lines, filtered if a filter was given.
- Keeps field 2 and field 11 of each pipe-separated line.
- Counts identical lines and sorts them by count, highest first.
- Clears the screen, prints the clock box and the top 20, then waits 2 seconds.
Notes
- It reads the log with
sudo, so it works for any user that can usesudo. - The log must be pipe-separated, because the command reads fields 2 and 11. Lines in another format give empty or wrong columns.
- It shows the most frequent recent requests, not an exact live list of connections that are open at this moment.
- Once a suspicious IP is found, block it with
block.
See also
| Command | Description |
|---|---|
iptop |
Track the most visited IP addresses on a server |
usertop |
Check recent visitors per domain |
posttop |
Track and check IPs making POST requests |
sizetop |
Show the largest responses in the access log |
bots |
Track all bot visits to your server (good and bad bots) |
ddos |
Track and block DDoS attack IPs in GoAdmio |
block |
Block an IP address on a GoAdmio server |