Connecting a server

Three ways to give Tickhound data: network probes, uploaded files and monitoring.

1. Add the server

Go to Servers → Add server. Enter the address, port, Minecraft version, software and proxy type. List the ports of any backend servers behind your proxy, and the RCON port if you use it. You must confirm that you own the server or are authorised to test it — network checks only ever run against hosts you declare.

2. Upload diagnostic information

When you run diagnostics you can paste:

server.properties
your plugin list (/plugins output, jar file names, or plugin.yml files)
the proxy configuration (config.yml or velocity.toml)
the end of logs/latest.log
your start command / JVM flags (and optionally java -version output)

Only the parsed facts are stored. The raw log is never kept, so player names and IP addresses in logs do not end up in Tickhound.

3. Get live data with the Tickhound plugin

TPS, tick time, Java heap and player counts can only be measured inside the game. The free Tickhound plugin sends them to your dashboard.

Open Monitoring in the dashboard and press Download Tickhound.jar. Your server's address and secret are already inside, so there is nothing to fill in.
Put the file in your server's plugins folder and restart. With Pterodactyl linked, Install through Pterodactyl uploads it for you.
The dashboard shows “Connected” as soon as the first data arrives (about 30 seconds after the server starts).

Works on Paper, Spigot, Purpur and Folia (Minecraft 1.18 and newer). In the game, /tickhound status shows whether it is connected and /tickhound test sends a sample right away. Downloading the plugin again creates a new secret and replaces the old one.

Monitoring is part of the Pro and Network plans. For your own tools, the same data can be sent to /api/monitoring/ingest with a token (see the Advanced section on the Monitoring page).