Skip to Content
txAdminMonitoring
Open in ChatGPTOpen in Claude

txAdmin Monitoring

txAdmin includes useful live server management and observability features. It is not a complete monitoring/alerting stack, so distinguish documented features from those provided by additional services.

What txAdmin can show

According to the upstream txAdmin feature list , supported capabilities include:

  • Server and player status, with controls for starting/stopping/restarting.
  • CPU and RAM usage, server thread-performance charts and player counts.
  • Live Console, including search, history and server output.
  • Server Activity Log, including connections/disconnections and selected player or game events.
  • Automatic FXServer recovery after a crash or hang, when configured.
  • Scheduled restarts, warning announcements and relevant custom events.

Read the first meaningful error in the Live Console before restarting a resource; repeated automatic restarts can conceal a persistent failure.

What needs another monitoring system

Do not assume txAdmin has built-in rules for automatic restart at a chosen memory threshold, arbitrary player-count threshold alerts, failure emails/SMS, or a general-purpose custom alert dashboard. These were previously presented here as standard txAdmin settings without reliable support.

For production monitoring, add an independent service for:

  • Game-endpoint or join-health checks (not merely whether the web panel responds).
  • Process uptime and host disk/memory availability.
  • Database availability, backup status and recovery failures.
  • Alert delivery to your chosen on-call channel.

Keep admin tokens and monitoring endpoints private. Periodically test notification delivery and configure alerts to avoid repeated false positives.

Day-to-day checklist

  1. Check the txAdmin dashboard and confirm the expected server build, uptime and player count.
  2. Review new console errors and resource-start failures.
  3. Watch server-thread performance as player load changes.
  4. Check the separate host/database monitoring and latest successful backup.
  5. Test one real client join and spawn after significant maintenance.

Troubleshooting

ObservationFirst investigation
FXServer restarts repeatedlyFirst crash/log entry, failing resource, artifact compatibility
CPU usage rises during eventsAffected resources, resmon/profiler and concurrent players
Game is unreachable but txAdmin loadsServer process, resource startup and 30120 TCP/UDP
Web panel unreachabletxAdmin port/address, private access or tunnel
Missing monitoring alertsConfiguration of the external monitoring service

See Performance Monitoring, Server Logging, txAdmin Troubleshooting, and txAdmin’s official feature list .