Logs
The Logs area gives System administrators a browser-based Log Viewer for inspecting server and application log files. Use it when troubleshooting errors, tracing HTTP traffic, or reviewing application activity recorded by the platform.
Accessing Logs
- Sign in with a System administrator account.
- In the left sidebar, open the SYSTEM section.
- Click Logs.
The Log Viewer opens in a dedicated interface (separate from the main BIU layout). Use ← Back to BIU in the top bar to return to the application.
Log Viewer layout
The screen has three main parts:
| Area | Purpose |
|---|---|
| Top bar | Return link, page title, and a search field for finding text across log files |
| Left sidebar | Filter log types, pick the environment host, browse files, and sort the file list |
| Main panel | Log entries for the selected file, or a prompt to select a file or start searching |
Until you choose a file or run a search, the main panel shows Select a file or start searching….
Environment host
At the top of the file list, the viewer shows the current host label (for example the application environment name such as Test or Production). This identifies which server’s log files you are browsing. Remote hosts can be configured for operations teams; in a typical setup you only see the current environment.
Filtering by file type
Use Selected file types to narrow which kinds of logs appear in the sidebar. Common groups include:
| Type | Typical contents |
|---|---|
| Laravel | Application logs written by Laravel and the platform (see Common log files) |
| HTTP Access (Nginx) | Web server access records (requests, status codes, paths) |
| HTTP Error (Nginx) | Web server error records |
You can combine several types in one view. Adjust the filter when you know whether you need application errors, web server access, or both.
Browsing log files
Under Log files on host name, the sidebar lists matching files grouped by folder, for example:
- root — application logs under the Laravel
storage/logsdirectory /var/log/nginx— Nginx access and error logs on the server
Each entry shows the file name and size. Use Newest first (toggle at the top of the list) to sort by date when many rotated files exist.
File actions
Each file has a ⋮ (more) menu. Depending on the file and your permissions in Log Viewer, actions may include downloading or removing a file. Use delete actions only when you understand retention and compliance requirements; prefer leaving production logs to your hosting or operations policy.
Viewing entries in a file
- Click a file in the sidebar.
- The main panel loads log lines for that file, usually newest entries first.
- Use level filters (such as Error, Warning, Info) when available to focus on severity.
- Scroll or use pagination controls to move through long files.
Laravel stack traces can be long. Log Viewer may offer options to shorten stack traces by hiding common framework paths.
Searching
Search within the open file
After a file is loaded, use in-page search or filters provided in the viewer to jump to matching lines.
Search across files
The search field in the top bar searches across the log files that match your current Selected file types filter. This is useful when you know an error message, request ID, or user identifier but not which daily log file contains it. Cross-file search can take longer on large files; progress is shown while scanning.
Common log files
Exact names depend on environment and rotation. These are the files you will most often see:
| File | Description |
|---|---|
laravel.log | Main Laravel application log (default stack channel). Exceptions, warnings, and general application messages appear here. |
emin-YYYY-MM-DD.log | Daily emin channel log. Records structured activity such as HTTP controller actions (method, controller, client IP, user id, request and change data) and some command outcomes. Rotated daily; older files are kept for a limited number of days. |
browser.log | May be present in some environments for front-end or browser-related logging. |
| Nginx access / error logs | Under /var/log/nginx when Nginx is used in front of the app. Use for failed requests, 4xx/5xx patterns, and upstream issues. |
The emin log is especially relevant for auditing what changed in write operations (original vs updated data) when controllers use the platform logger. Treat these files as sensitive: they can contain personal data submitted in forms.
Practical troubleshooting
| Goal | Suggested approach |
|---|---|
| 500 error or exception | Open laravel.log or the latest emin-*.log, filter by Error, note timestamp and stack trace |
| User action not saved | Search emin-*.log for the user id or route; compare originalData and updatedData in the entry |
| Page not loading / timeout | Check Nginx HTTP Error logs, then laravel.log around the same time |
| Missing static asset or wrong URL | Check Nginx HTTP Access for status codes (404, 403) |
| Unknown message text | Use top-bar search across Laravel files before opening each daily file |
Times in the viewer use the application timezone unless configured otherwise.
Availability and security
- Log Viewer is served at
/log-viewerand requires an authenticated System administrator with the logs-read permission. - It can be turned off per environment (
LOG_VIEWER_ENABLED). If Logs is missing or returns forbidden, contact your platform operator.