Suggestion: Logging and Monitoring Improvements

[JoelKatz]

The XRP Ledger has both statistics reporting and logging by category and severity. However, it has been neglected for some time. The statistics reporting could use a refresh to ensure that it is capturing parameters that are useful and valuable and to add monitoring of newer features that were added without such reporting. The logging needs a thorough audit to ensure that priorities are set appropriately and overly-chatty logging is disabled by default.

This post is one suggestion for an enhancement to the XRP Ledger. See this post for context:
https://www.xrpchat.com/topic/33070-suggestions-for-xrp-ledger-enhancements/

You can find all the suggestions in one place here: https://coil.com/p/xpring/Ideas-for-the-Future-of-XRP-Ledger/-OZP0FlZQ 

[mDuo13]

Personally, I'd like a health check method that summarizes the statistics into something easy to grok and take action on even in an automated fashion.

It would also certainly make server administration easier if the rippled server's log messages were less noisy. A whole bunch of the known log messages at the warning level are only concerning if they occur outside of the syncing period or recur consistently. I think a great start for cleaning up the rippled server log would be to have a (tunable) sync time parameter, such as 15 minutes, and a class of messages that aren't considered warning-level messages if they occur within that amount of time after starting up. Similarly, the server could report increasing severity messages if it still hasn't fully synced by the end of the sync period & increasing intervals thereafter.