Non-error logs are printed to stderr

[ku1ik]

As in title. This makes alerting configuration based on log severity problematic because everything seems to be an error. Most logging aggregation tools and platforms treat stderr output as level=error.

For example, "New tick of statistics from 10.9.1.100: 2497 ads blocked / 26870 total DNS queries" is not an error but it logged to stderr.

Steps for Reproduction

Run the exporter, redirect stderr to a file, observe all logs being saved there.

Expected behavior:

Informational logs are printed to stdout, and only errors are printed to stderr.

Actual behavior:

All logs, including informational, are printed to stderr.

Platforms:

Ubuntu 20.04, x86 64-bit

Versions:

0.1.1

[Galorhallen]

This should be handled with #110, which also introduce log levels

[ku1ik]

Nice!