For reasons irrelevant to this our storage is sometimes very slow causing the MongoDB plugin to fail after which it "hangs" and stops collecting data until the agent is restarted. Only the MongoDB plugin "hangs", so kudos on building a solid framework

Nothing else on the servers experience issues, besides it being a bit slow.

Certainly not a solution, but it'd be nice to also have configurable timeout so we can tweak it on troublesome servers.

i see two issues here.

1. Timeout is too short
2. Plugin hangs when it can't connect to MongoDB

Steps to reproduce:

1. High kernel I/O wait with long I/O service times

Result:
**

[Mongo] Cannot fetch data: read tcp 127.0.0.1:36558->127.0.0.1:27017: i/o timeout.
check 'mongodb.oplog.stats["tcp://localhost:27017","zabbix","xxxxxxxxxxxx"]' is not supported: Cannot fetch data: read tcp 127.0.0.1:36558->127.0.0.1:27017: i/o timeout.

Expected:

Well, no timeout