XMPP Service Operators - 2021-03-31

the prober update I did last night broke everything.

jonas’: is this question still relevant?

Ge0rG, well… not right now ;D

but if you could check around thet timestamp of my question it’d be great

Is there some string to easily grep for in prosody.log?

I don’t recall unfortunately

we can also postpone this until I fixed the prober again :)

jonas’: the log file has 37M lines. "Around that timestamp" is 1.3M lines. I'd happily grep for whatever you want, but I'm not going to review it manually.

hahaha

yeah, I’ll try to find something

👍

» <Ge0rG> jonas’: the log file has 37M lines. "Around that timestamp" is 1.3M lines. I'd happily grep for whatever you want, but I'm not going to review it manually. Is that amount of logging useful?

Speaking of, is it really neccecary for prosody to log by default every time it makes or recieves a successful federated connection?

Instead of just the errors

Or significant events

tom: often you only know after the fact which event was significant. Most of the logging is junk, but I don't have a mechanism to filter relevant from unrelevant

Idk

exactly.

just running debug logs and letting the disks rotate is much cheaper than doing significant work to improve the logging framework

I've never had an event where the message like: Mar 31 01:29:30 s2sin557956e4ae70 info Incoming s2s connection yax.im->conference.nuegia.net complete was actually useful in troubleshooting something

08:25:52 tom> Speaking of, is it really neccecary for prosody to log by default every time it makes or recieves a successful federated connection? Looking at my logs, I was also wondering about that. `info` on the other hand seems reasonable for that.

I don't think so. Perhaps messages like these would be better suited for the 'debug' syslog severity

» Mar 31 01:29:24 s2sin557957e68af0 info Incoming s2s stream yax.im->conference.nuegia.net closed: connection-timeout » these on the other paw ^, useful to know

but then you’d only see when the connection was closed, but not when it was opened ✏

I don't care if info or debug, as I'm debug-logging anyway

I wonder if prosody would accept a patch to change that

you could ask :)

Maybe some other time

For now I think i'm just going to enable a debug rolling buffer and only lag warns and errors to disk

have a yeen https://cdn.nuegia.net/cc0a3999-fff5-43f1-adbf-879cf43d9e9b/db3abbd947288b4c.jpg

tom: there is also mod_log_json

I don't see how that's useful

tom: it's structured logging and it can be dumped into kibana or somesuch