Thanks to all contributors

Features

• Rework of the metrics tab. The alerts tab in the in browser widget is now based on the metric 2.0 format which means in practice, that for example the request name can be rendered as GET / instead of GET_|.
• Rework of the alerting feature. The alerting feature is now also based on MetricName which supports tags and values instead of dot.separated.metric.names. As a consequence, creating checks is much more user friendly as it features better auto completion. See also #182
  
• Introduce MetricNameTemplate which essentially is a cache for MetricNames. Most metric names like the timer name for the request response time consist of a static part like name=response_time_server and a dynamic part like request_name=Search Products. Previously, the MetricName had to be recreated each time Search Products was invoked. The MetricNameTemplate now caches the MetricName for each distinct request name. This should improve the performance as less objects have to be created and reduces the amount of thrash stagemonitor creates. The garbage collector will thank you for updating to the latest version. See commit 945ef64 for more information. Example usage:

MetricName.MetricNameTemplate timerMetricNameTemplate = name("response_time_server")
        .templateFor("request_name");
MetricName metricName = timerMetricNameTemplate.build("Search Products");

Breaking Changes

• All in browser metric tab plugins have to be updated to the new metric name format
• You will have to recreate all alerting checks as the format of the metric name has changed
• The semantics of the alerting thresholds are inverted. See #182 for more information.