Extend and standardise haproxy_exporter.

Here's the changes I brought up on the mailing list.


Add frontend stats.
Add additional backend stats.

Use haproxy terminology of backend/server rather than services/frontend.
Prefix metrics with frontend/backend/server to make it clear where they come from.
This should reduce confusion.

Add haproxy_up, similar to 'up', and remove exporter_scrape_failures.
This makes it easier to tell if haproxy is resonding.

Use 'type' field rather than 'svname' to determine if a csv row
is a frontend/backend/server. This will be more resilient if anyone
has listeners.
Ah, now I see what's going on with that. Fixed.

On 2 October 2014 21:31, Tobias Schmidt <notifications@github.com> wrote:

> In haproxy_exporter_test.go:
>
> > @@ -48,14 +48,14 @@ func TestInvalidConfig(t *testing.T) {
> >  		e.Collect(ch)
> >  	}()
> >
> > +	if expect, got := 0., readCounter((<-ch).(prometheus.Counter)); expect != got {
>
> Hmm, isn't that the opposite of what we expect? If I understand your
> change, up should always be 1?
>
> —
> Reply to this email directly or view it on GitHub
> <https://github.com/prometheus/haproxy_exporter/pull/8/files#r18365380>.
>