Better names for destinations

[vsevolodpoliakovdatarobot]

Hi there, great product.

Right now is hard to understand what count of metrics was sent to cluster, I mean will be more easy to read and understand with metrics like:

relay.destinations.$clustername.$host

Also will be good to have options to add fnv1a_ch key as a hostname. I mean I don't really need the ip address of a destination because it can be changed.

[grobian]

Can you give an example of what your mean with fnv1a_ch key as hostname?

To produce the metrics like you suggest, an aggregation has to be made, since the collection of metrics is currently focussed around the workers (=dispatchers).

[grobian]

I see, you want a cluster-oriented stats thing. The collector doesn't really know about topologies or anything, so it's hard to do this.

[vsevolodpoliakovdatarobot]

Yeah, but if cluster-oriented metrics is not possible, maybe will be possible to collect metrics by hash key?
I mean I have a config like:

cluster graphite1
    fnv1a_ch
        10.0.0.0=carbon0
        10.0.0.1=carbon1
    ;
cluster graphite2
    fnv1a_ch
        10.0.0.2=carbon2
        10.0.0.3=carbon3
    ;

and ip address can be changed, but key can't, so it will be much easy to read\build dashbord with metrics like:

relay.destinations.carbon[0-1].sent and relay.destinations.carbon[2-3].sent