These can be set as needed in the config file and use the existing settings as the defaults.
Up until this point we've been using a fork of statsd @paperlesspost that was forked VERY early on and went in a different direction for a while. We want to get back up to trunk, but without being able to alias these new timer metrics, we lose consistency between our current metrics and would have to either migrate a lot of files, or just start from scratch. This gives us (and probably other people) the best of both worlds, being able to use statsd but having our uppers called max's and etc.
Allow for aliasing the different timer metrics
These can be set as needed in the config file and use the existing
settings as the defaults
Hey thanks for the pull request! If I understand correctly, this is basically just metrics naming cosmetics presumably for Graphite? In that case it would make much more sense to have that option in the backend, since it shouldn't matter how they are called internally while processing metrics. Or am I missing something there?
Also allow aliasing count and rate for counters
@mrtazz Maybe I'm missing something, but it seems like in the current setup, process_metrics is called for any backend? In this case these are global aliases, not per-backend
right it's the function for internal metrics processing. I was just thinking about whether naming metrics should even be a concern of the processing part or if it makes more sense to have each backend decide how data should be sent. Kind of related to #155
@mrtazz OK! I guess I'll wait for that work to be merged. In the meantime we're using this in production.
Fix aliases from config