On this page
Two entries in the server sidebar sound like logs and record completely different things. Logs, under System, is the panel's own activity timeline. Event log, under Clouduxe Prism, is the protection layer's packet-drop stream. Neither one holds your application's logs.
What the Logs tab records
The tab is headed "Activity log" and the timeline card is "Recent activity". Three kinds of entry appear in it.
Anything currently running is pinned to the top with a spinner while it is in flight, then drops into the timeline when it finishes.
Three lifecycle entries, one each: "Server provisioned" with the order it came from, "Server build completed" with the OS template that was installed, and "Server configuration updated".
Protection changes, which are the substance of this log. Inbound rule edits, applied presets, engine toggles, and blocked or allowed addresses are recorded as they happen, each with the account that made the change. Changes an operator made on your behalf appear here too, because entries are matched on the server's IP address as well as on the contract.
How far back it goes
The three lifecycle entries are not a history. They are reconstructed from single timestamps the hypervisor reports, so there is exactly one "Server configuration updated" row showing the most recent change and nothing before it. A reinstall does not add a row either. It overwrites the "Server build completed" timestamp in place.
Protection changes are the only genuine append-only record on the page, and the tab shows the latest 50. Anything older than that is not displayed.
The panel states this itself in the "About this log" card at the bottom of the tab: lifecycle history from before your server was provisioned is not exposed by the underlying hypervisor API, which is why those entries are reconstructed rather than listed.
Power actions are not recorded
Boot, Shutdown, Restart, and Power off leave no entry. Not on this tab, and not anywhere else in the panel. There is no history of who restarted a server, or when, or from which account.
This is the single most common reason customers open this tab, so it is worth being blunt about: if a server went down and you need to know whether someone with panel access rebooted it, the answer is not here and cannot be recovered from the panel. Open a support ticket with the server and the approximate time, and ask the team to check.
The Event log tab is protection, not server events
Despite the name, Event log has nothing to do with your server's lifecycle. It is the Clouduxe Prism drop stream: every packet the edge dropped for this server, newest first, under the table heading "Logged drops".
Two limits carried in the panel's own wording apply to it. It is capped at the latest 50 drops, and the edge records a 1-in-64 sample, so what you are reading is a representative slice rather than every packet. Treat the volumes as estimates.
It appears in the server sidebar under Clouduxe Prism when attack analytics is available for your server. For what the numbers mean and how to read a mitigation, see Reading the Attacks tab.
Your application and system logs are on the server
Nothing the software on your server writes reaches the panel. There is no log shipping, no log viewer, and no search. Your web server access logs, your game server console output, your systemd journal, and the Windows event log all stay on the machine.
Reach them the way you would on any server, over SSH or, if the network is the thing that is broken, from the console:
journalctl -u nginx -n 200 --no-pager
tail -n 200 /var/log/syslogOn Windows, use Event Viewer over Remote Desktop or from the console.