Increase default connection timeout

[End-rey]

Closes #147.

As I understand it, there is only a connection to the server and the value has increased significantly. Maybe put 15 seconds?

[codecov]

Codecov Report

Attention: Patch coverage is 0% with 2 lines in your changes missing coverage. Please review.

Project coverage is 3.03%. Comparing base (3f84a08) to head (34afd00).
Report is 7 commits behind head on master.

Files with missing lines	Patch %	Lines
cmd/neo-exporter/config.go	0.00%	2 Missing ⚠️

Additional details and impacted files

@@          Coverage Diff           @@
##           master    #152   +/-   ##
======================================
  Coverage    3.03%   3.03%           
======================================
  Files          18      18           
  Lines         987     987           
======================================
  Hits           30      30           
  Misses        955     955           
  Partials        2       2           

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

[roman-khimov]

I think there is an imbalance now between chain.dial_timeout and metrics.interval which can lead to resource leak. In general, dial_timeout can't be less than the interval since new scraping attempt shouldn't be performed before the old one has finished. Either it's handled by exported internally (skip the interval tick if still collecting), or we shouldn't have this 60/15s relation in the config.
@532910, @smallhive?

[smallhive]

This PR is for timeout changes, let's add one more commit and change this to 15*time.Second.
The example YAML config contains 15s and I doubt 15 minutes is a good interval between metric gathering for default value 😅

[smallhive]

I think there is an imbalance now between chain.dial_timeout and metrics.interval which can lead to resource leak. In general, dial_timeout can't be less than the interval since new scraping attempt shouldn't be performed before the old one has finished. Either it's handled by exported internally (skip the interval tick if still collecting), or we shouldn't have this 60/15s relation in the config. @532910, @smallhive?

The collection ticks executes after interval, but only if the previous execution is done. It works because we do it inside one for.

[roman-khimov]

only if the previous execution is done

OK then.