Re: [Hawkular-dev] availability and metric endpoints
I think the "metrics" should actually be dropped instead of
"numeric".
Hawk metrics will never deal with anything else than some kind of metric, so
way have it in the path? On the other hand having the type of the metric in
the path is IMHO more useful.
It is the context root of the metrics rest web app that should be called
"metrics", IMHO.
So the paths in metrics would look like:
/{tenantId}/numeric/data
/{tenantId}/availability/data
and the REST API user would reach those on the URLs like:
http://asdf.com/hawkular/metrics/tenant1/numeric/{id}/data
conversely, inventory could be reached on the same host like:
http://asdf.com/hawkular/inventory/tenant1/production/resources/{id}
On Friday, March 20, 2015 11:00:22 John Sanda wrote:
There has been some good discussion around availability lately. I
want to
add one more to the mix, but hopefully this one is not as in-depth as some
of the other topics. Right in metrics we have endpoints like,
POST /metrics/numeric/data
GET /metrics/numeric/{id}/data
POST /metrics/availability/data
GET /metrics/availability/{id}/data
I would like to change these to,
POST /metrics/data
GET /metrics/{id}/data
POST /availability/data
GET /availability/{id}/data
I think the “metrics” prefix is awkward and unnecessary. I think that it is
intuitive enough that metrics on its own refers to numeric data. Thoughts?
- John
_______________________________________________
hawkular-dev mailing list
hawkular-dev(a)lists.jboss.org
https://lists.jboss.org/mailman/listinfo/hawkular-dev