Server Logs

Server Logs (System in the navigation, admins only) shows the TeamSpeak server's own log — what the server wrote about itself — not this app's. It is the place to confirm what the server actually saw: whether an action the manager sent was accepted, why a client left, what happened at a certain time. For this app's own logs (the backend, the bot engine, the music bots) use the container logs instead, as described under Troubleshooting.

Reading it

Which log: This server is the log of the selected virtual server; Instance log is the master log of the whole TeamSpeak installation rather than of one virtual server.
How much: 25, 50 or 100 lines at a time, newest first. Older and Newer below the list page through it; the footer says how many lines are shown and how many were skipped.
Level: every line gets an ERROR, WARNING, INFO or DEBUG tag, recognised from the level in the line itself (a line without one is shown as INFO). The level menu hides the others.
Filter: the text field keeps only the lines that contain what you type, ignoring capitalisation.

The level menu and the text filter work on the lines that are loaded — the 25, 50 or 100 currently on screen. If what you look for is further back, page to the older lines or raise the line count, then filter again.

Refresh loads the log again. The page does not update by itself.
Export saves what is shown (after the filters) as a plain text file or a simple HTML page. It is made in your browser.

Adding your own entry

Add Entry writes a line of your own into the server's log at a level you choose (error, warning, debug or info). Use it to mark a point in time before you reproduce something, so you can find the spot again afterwards.

What shows up from this app

A command from the Query Console that changes something leaves a line [TS6 Manager] <user>: <command> here. Commands that only read leave none.
Which events TeamSpeak writes into the log at all is set per virtual server under Advanced Settings → Moderation & Logging → Event Logging (Virtual Servers and Instance): clients, ServerQuery clients, channels, permissions, server changes and file transfers. With Clients off the log shows no connects and disconnects, and with ServerQuery Clients off none of the query connections. The Connection Journal does not depend on these switches.

Permissions

TeamSpeak lets an account read the log of a virtual server with b_virtualserver_log_view and the instance log with b_serverinstance_log_view. The account the manager connects with needs the one that fits; without it TeamSpeak refuses and the page shows its message.

v0.1, last edited 09.10.2026