Add more logging

[tolik518]

• What we're getting (if check_posts/check_mentions is true), like Getting comments, posts, inbox
• How many comments total were returned by the api (comments.len())
• How long we sleep for (reply and polling)
• What the current ratelimit values are, like 504s till reset, 783 requests remaining
• the current last_ids values, like Last ids were t1_msu372s (comments) t3_msu42sa (posts) t1_ue14n2s (inbox)

In general, I would use debug for data useful while developing/debugging (duh), logged once a loop or reply at most. And trace could be used for stuff that happens every gotten comment, though I have no ideas, what could be useful there.

Originally posted by @Aras14HD in #167 (comment)

[Aras14HD]

Also adding the status code to the reply fail log would make sense to figure out the failures with empty body.

[Aras14HD]

And it would be nice to have color in the terminal, that is simply done with:

let style = buf.default_level_style(record.level());
writeln!(
    buf,
    "{style}{} | {} | {} | {}",

You might also want to consider using record.target() instead of env!("CARGO_PKG_NAME"), so it is clear where the record comes from (whether factorion or reqwest and which module).

Anyway, the log already looks great, better than I could have wished!

[tolik518]

Also adding the status code to the reply fail log would make sense to figure out the failures with empty body.

Agree. I also saw your attempt to summon factorion on ProgrammerHumor

Color in the terminal would be a neat addition, I don't know how we'll it integrates with my pipe which writes the logs to a text file, but I'll take a look at it.

Yeah I can add target to the logs and I think version would also make sense here.

The logs could have been better if I used ELK instead of loki/alloy, but I figured out that ELK is a bit more resource hungry and I wanted to try out something new. I'm still fiddling around with configs so logs may be not reachable now and then until I find a good configuration.

Not directly relevant, but I should start to version control the configs in my server, because I removed one of the configs today on accident and it took me a while to reconstruct it, lol

[Aras14HD]

Color should not be an issue, I think the codes are removed when piped, worst case prod needs RUST_LOG_STYLE=never.

[Aras14HD]

Would look like:

But when piping:

[tolik518]

Looks good, should be no issue then

[Aras14HD]

Including the module/crate name instead of always "factorion-bot"?

[tolik518]

With that we'll have a small issue as I currently get the service name from that position, so it would be a breaking change.

On the other hand I started gathering the service name from the log position so it should be ok, but I'll need to make some adjustments to the log aggregator in the meanwhile.

So yeah, go for it, but I'll need to make some small adjustments before that.