oliver006 / redis_exporter / 308

84%

master: 85%

Pull #890

drone.io

Add password key option

The Redis does not support auth by username and password until
version 6.0. So in legacy version instances, administrator can
only set one password.

The current version of redis_exporter support read password from
the path specified by the password-file option according to the
URI of redis connection to collect metrics from multiple targets.

But this design requires the administrator list all target URIs
into the password file. Every time new instance created, the
password file has to be updated. Besides, having many different
instances dose not necessarily require all of them use different
passwords. They may be separated into several groups, and instances
of the same group may use identical password.

In this scenario, it will be more convenient to introduce the
concept of password key. When the collecting job fetch the probe
API, it can transport one additional key for password:

```
http://10.0.0.1:9121/scrape?target=foo:6379&passkey=dev
http://10.0.0.1:9121/scrape?target=bar:6379&passkey=dev
```

Both the instances of foo:6379 and bar:6379 could use the same
password, and we can only add one line into the password file:

```
dev:dev-pass
```

5 of 10 new or added lines in 4 files covered. (50.0%)

1973 of 2347 relevant lines covered (84.06%)

11491.94 hits per line