Sonalyze is bad at reporting problems. I'm probably having an issue with illegal JSON data being sent from los.fox, it seems to be sent OK but sonalyze either does not see it or it drops it on the floor for unknown reasons. There's nothing in the syslog, and the -v spew is so overwhelming (7 msgs per second from Betzy alone) that it too is unhelpful. So seeing the problem is hard, and diagnosing it is hard.
One part of the equation is how to print errors, the other part is where to print them.
Relying on the syslog is not ideal - on many systems you have to be root to see it. It would be better for sonalyze to print errors to a designated error log. But for an initial cut, the syslog may be OK.
Sonalyze is bad at reporting problems. I'm probably having an issue with illegal JSON data being sent from los.fox, it seems to be sent OK but sonalyze either does not see it or it drops it on the floor for unknown reasons. There's nothing in the syslog, and the -v spew is so overwhelming (7 msgs per second from Betzy alone) that it too is unhelpful. So seeing the problem is hard, and diagnosing it is hard.
One part of the equation is how to print errors, the other part is where to print them.
Relying on the syslog is not ideal - on many systems you have to be root to see it. It would be better for sonalyze to print errors to a designated error log. But for an initial cut, the syslog may be OK.