Better server logging?

  • The FTB Forum is now read-only, and is here as an archive. To participate in our community discussions, please join our Discord! https://ftb.team/discord

Rebirth Gaming

New Member
Jul 29, 2019
360
0
0
Hello,

We host our server using Galaxy Node, who uses Multicraft. Our server owners then have access to the files via FTP.

One thing I have come to hate about Multicraft is how 'plain' the console is.
There is no distinction between errors, warnings, and info. No color coding, no filtering. It also likes to skip lines - if it detects there are too many messages being logged, it'll 'collapse' a bunch and simpyl print out "Skipped xxxx lines"

Of course, everything is still actually being recorded to the server.log in our root directory. This file can be viewed at any time without having to download it (unless, of course, it reaches a certain size, but that's just up to us to make sure to delete the server.log time to time)

I'm curious what methods you all use to stay sane when viewing your server log. What options are there that can better filter such logs to quickly pinpoint things like errors among the ocean of messages?
 

Circuitbomb

New Member
Jul 29, 2019
51
0
0
Use an editors find/search feature or use cat + grep on your server.log; string matching [ERROR]/[SEVERE]/[WARNING]/Exception and piping it into individual logfiles.