Net::SSH error "Agent not configured" fills the logs

[narendt2]

• I have read and understood docs/Issues.md.

Is your feature request related to a problem? Please describe.
After today's update I have tried out the new logging directive and now the log gets filled with
2025-07-16 15:57:51.469548 E [1557:Oxidized::Job 'example.com' loggable.rb:43] Net::SSH -- net.ssh.authentication.agent[3c00] -- could not connect to ssh-agent: Agent not configured
messages and 'real' errors are much harder to spot.

Describe the solution you'd like
As far as I can tell SSH connections still work properly as they have before, so here are some solutions I would like:

• Let me disable ssh-agent integration
• Demote the Error to a Warning
• Let me filter out specific errors
• Have a guide to set up ssh-agent integration properly for a standard Ubuntu installation (no Docker)

Describe alternatives you've considered
I have tried setting up a ssh-agent systemd service but could not really get it to run in a way that worked with Oxidized. As a solution I'd like this best, actually.

Additional context

oxidized 0.34.0
Ubuntu 24.04, regular installation

I set up logging per the example configuration:

logger:
  # Default level
  # level: :info
  appenders:
    - type: syslog
      level: :error
    - type: stdout
      level: :warn

This is my first Issue, please let me know if I can help with more information!

[robertcheramy]

Typical dev environment problem - I have almost everywhere an ssh-agent configured, and I oversaw the error when I tested the container (which hasn't an agent configured).
I will revert the log level of Net::SSH to the level of 0.33.0 (Fatal) and release a patch release soon.