Skip the `jobExecutor: Job errored` log line if `ErrorHandler.HandleError()` is implemented about river

[dhermes]

Sounds good! I need to implement a zerolog wrapper anyway. I'll avoid logging in my handler and just handle the Sentry parts there.

Cheers!

[brandur]

Hmm, I'm a little hesitant to make the behavior subtle to that degree, which may make it hard to understand/explain. I'd also suspect that there may be some users out there who would want the error logging even though they implemented ErrorHandler, and I don't think we'd want to add a specific configuration option to indicate whether you want one or the other.

@dhermes Have you considered either (1) redirecting the built-in slog logging to another target, or (2) disabling it in favor of your own logging? You can suppress it completely with something like:

Logger: slog.New(&slogutil.SlogMessageOnlyHandler{Level: 9}),

(This works because 9 > slog's error level.)

If you wanted logging on job completion etc, you could add a subscription where that happens.