Introducing Structured, Searchable, Interactive Web Server Logs

Announcements
1

The Web Server Log viewer has been redesigned from the ground up.

Instead of scrolling through raw text, you now get a searchable table, interactive timeline, and powerful filtering tools to quickly find the entries that matter.

image2
image21962×1084 176 KB

What’s New

  • Structured table view: Log entries are organized into columns (Time, IP Address, Method, Path, Status) with expandable rows for full details on each request

  • Interactive timeline: A bar chart at the top of the viewer shows how requests are distributed over time. Hover over a bar to see request counts and types, or click to jump directly to those entries in the table

  • Search and filter: Search by path, IP address, or status code. Filter by HTTP method (GET, POST, etc.) or response status (200, 404, etc.) using the dropdown menus

  • One-click actions: Reload to fetch the latest entries, copy log data to your clipboard, or download the raw log file

  • Raw view still available: Switch back to the original raw-text view at any time using the Raw toggle

Supported log types: NGINX Access, NGINX Error, Apache Access, Apache Error, and G-Firewall.

Note: The viewer displays the most recent 500 lines from the underlying log files. NGINX buffers logs and writes them after the buffer reaches approximately 16 KB, unless your web application is in Development Mode.

To access the new Web Server Log, navigate to your web application and Web Server Log, as shown below:

image1
image11999×1238 210 KB

Learn more about the new Web Server Log view in RunCloud →

5 Likes
2

This is a fantastic improvement and will make troubleshooting so much easier. Great work, RunCloud team! :clap:

1 Like
3

Agreed, great and essential improvement!

1 Like
4

After trying to use this a few times, yes, the interface is useful. However, 500 lines is not enough. In reality, even with low to medium traffic websites, 500 lines may be an hour or two of traffic, especially with bot traffic. When I go and try to investigate something that happened overnight, these logs don’t reach back far enough. I don’t remember having this issue with the previous logs.

5

Hey @nate,

Noted, thank you for the honest feedback. This is always much appreciated. :raising_hands:

I’ve raised this with the team already and will keep this thread up-to-date in terms of whether we can offer a configurable history (i.e., let users choose what history they want to have, and what the potential impacts are of increasing the time period, etc.).

Have a great weekend ahead!