Webhooks and logging?

[LeeNX]

Finally got my WatchState working or at least I think it is, but have a few questions.

The webhook for jellyfin seems to show alot of info, which I have not found a way to turn off, at least for the log level INFO.

[2025-11-18T07:38:56.474164+00:00] http.INFO: 10.89.6.8 - "POST /v1/api/webhook HTTP/1.1" 200 0 "-" "Jellyfin-Server/10.10.7" "-" [] []
[2025-11-18T07:39:11.501726+00:00] webhook.INFO: [G] Queuing 'shirleyt@jellyfin_nexus_shirleyt' untainted request for 
[2025-11-18T07:39:11.503676+00:00] http.INFO: 10.89.6.8 - "POST /v1/api/webhook HTTP/1.1" 200 0 "-" "Jellyfin-Server/10.10.7" "-" [] []
[2025-11-18T07:39:26.650669+00:00] webhook.INFO: [G] Queuing 'shirleyt@jellyfin_nexus_shirleyt' untainted request for 
[2025-11-18T07:39:26.652487+00:00] http.INFO: 10.89.6.8 - "POST /v1/api/webhook HTTP/1.1" 200 0 "-" "Jellyfin-Server/10.10.7" "-" [] []
[2025-11-18T07:39:41.472203+00:00] webhook.INFO: [G] Queuing 'shirleyt@jellyfin_nexus_shirleyt' untainted request for 
[2025-11-18T07:39:41.474186+00:00] http.INFO: 10.89.6.8 - "POST /v1/api/webhook HTTP/1.1" 200 0 "-" "Jellyfin-Server/10.10.7" "-" [] []

I did try in my compose.yaml file

    environment:
      - WS_LOGGER_FILE_LEVEL=ERROR
      - WS_WEBHOOK_DUMP_REQUEST=false

but it did not seem to change the amount of logging.

Not to worried about logs sizes, more about ssd ware and tear once things are working.

[arabcoders]

Hello,

Thanks for bring this point up, it should be possible in v1.0.2 via the new ENV variables:

• WS_WEBHOOK_LOG_ENABLED
• WS_WEBHOOK_LOG_LEVEL

[LeeNX]

Thanks, that is awesome!

[arabcoders]

Np. ref 729f5d9

[rvventuri]

I’ve run into similar webhook issues in production before. Everything showed as “completed”, but the events never reached the destination.

Using Sigryn as an intermediate layer helped a lot, since it gives real visibility into webhook delivery, attempts, and failures instead of relying only on the provider’s status.

[arabcoders]

I’ve run into similar webhook issues in production before. Everything showed as “completed”, but the events never reached the destination.

Using Sigryn as an intermediate layer helped a lot, since it gives real visibility into webhook delivery, attempts, and failures instead of relying only on the provider’s status.

This indeed a valid way to gain insight, we also do provide very deep logging of webhooks events and requests. you can enable them via ENV and per backend logging.