<html><head><meta http-equiv="Content-Type" content="text/html charset=utf-8"></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space;" class=""><br class=""><div><blockquote type="cite" class=""><div class="">On Mar 20, 2015, at 12:23 PM, Lukas Krejci <<a href="mailto:lkrejci@redhat.com" class="">lkrejci@redhat.com</a>> wrote:</div><br class="Apple-interchange-newline"><div class="">On Friday, March 20, 2015 09:03:19 mike thompson wrote:<br class=""><blockquote type="cite" class=""><blockquote type="cite" class="">On 20 Mar 2015, at 08:19, Lukas Krejci <<a href="mailto:lkrejci@redhat.com" class="">lkrejci@redhat.com</a>> wrote:<br class=""><br class="">I think the "metrics" should actually be dropped instead of "numeric”.<br class=""></blockquote><br class="">The only thing about ‘numeric’ is that it is not very specific. Numeric just<br class="">means number — every metric is a number so its really not adding anything.<br class="">Even availability data is numeric.<br class=""></blockquote><br class="">Isn't metrics going to store "events" eventually, too? Those would be textual, <br class="">wouldn't they?<br class=""><br class="">Also, IMHO, even config could be stored in metrics. Even though that is a bit <br class="">of a stretch, configuration is after all a time series of structured data...<br class=""><br class="">You're right that at the moment numeric doesn't add much information. So maybe <br class="">instead of that, the type would specify what should be done with the metric?<br class=""><br class="">Something along the lines of dropwizard-metrics' distinction between a meter, <br class="">counter, gauge, histogram, etc?<br class=""><br class="">So like:<br class=""><br class=""><a href="http://asdf.com/hawkular/metrics/tenant1/histogram/{id}" class="">http://asdf.com/hawkular/metrics/tenant1/histogram/{id}</a><br class="">http://asdf.com/hawkular/metrics/tenant1/counter/{id}<br class=""><br class=""></div></blockquote><div><br class=""></div><div>My aggregate metrics design doc[1] talks about formally introducing gauges and counters. The question I have about endpoints like this is what about pushing a batch of metrics? Do we need to make a separate request for each type? That seems cumbersome and inefficient.</div><div><br class=""></div><div>[1] <a href="http://bit.ly/1BAfF8d" class="">http://bit.ly/1BAfF8d</a></div><div><br class=""></div><br class=""><blockquote type="cite" class=""><div class=""><blockquote type="cite" class=""><blockquote type="cite" class="">Hawk metrics will never deal with anything else than some kind of metric,<br class="">so way have it in the path? On the other hand having the type of the<br class="">metric in the path is IMHO more useful.<br class=""><br class="">It is the context root of the metrics rest web app that should be called<br class="">"metrics", IMHO.<br class=""><br class="">So the paths in metrics would look like:<br class=""><br class="">/{tenantId}/numeric/data<br class="">/{tenantId}/availability/data<br class=""><br class="">and the REST API user would reach those on the URLs like:<br class=""><br class=""><a href="http://asdf.com/hawkular/metrics/tenant1/numeric/{id}/data" class="">http://asdf.com/hawkular/metrics/tenant1/numeric/{id}/data</a><br class=""><br class="">conversely, inventory could be reached on the same host like:<br class=""><br class="">http://asdf.com/hawkular/inventory/tenant1/production/resources/{id}<br class=""><br class="">On Friday, March 20, 2015 11:00:22 John Sanda wrote:<br class=""><blockquote type="cite" class="">There has been some good discussion around availability lately. I want to<br class="">add one more to the mix, but hopefully this one is not as in-depth as<br class="">some<br class="">of the other topics. Right in metrics we have endpoints like,<br class=""><br class="">POST /metrics/numeric/data<br class="">GET /metrics/numeric/{id}/data<br class="">POST /metrics/availability/data<br class="">GET /metrics/availability/{id}/data<br class=""><br class="">I would like to change these to,<br class=""><br class="">POST /metrics/data<br class="">GET /metrics/{id}/data<br class="">POST /availability/data<br class="">GET /availability/{id}/data<br class=""><br class="">I think the “metrics” prefix is awkward and unnecessary. I think that it<br class="">is<br class="">intuitive enough that metrics on its own refers to numeric data.<br class="">Thoughts?<br class=""><br class=""><br class="">- John<br class="">_______________________________________________<br class="">hawkular-dev mailing list<br class="">hawkular-dev@lists.jboss.org<br class="">https://lists.jboss.org/mailman/listinfo/hawkular-dev<br class=""></blockquote><br class="">_______________________________________________<br class="">hawkular-dev mailing list<br class="">hawkular-dev@lists.jboss.org<br class="">https://lists.jboss.org/mailman/listinfo/hawkular-dev<br class=""></blockquote></blockquote><br class=""><br class="">_______________________________________________<br class="">hawkular-dev mailing list<br class=""><a href="mailto:hawkular-dev@lists.jboss.org" class="">hawkular-dev@lists.jboss.org</a><br class="">https://lists.jboss.org/mailman/listinfo/hawkular-dev<br class=""></div></blockquote></div><br class=""></body></html>