<html><head><meta http-equiv="Content-Type" content="text/html charset=windows-1252"></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space;" class="">H-Metrics is in the same situation as H-Alerts. The tenant id is really only used to partition data; however, it is not the only thing used to partition data. H-Metrics currently does not have any APIs for querying across multiple tenants. There is no technical restriction or limitation that prevents us from doing so. More fine-grained tenants won’t make querying in H-Metrics any less efficient because we are querying across multiple partitions either way. We always do those queries in parallel. More fine-grained tenants would have some implications though on how we design background jobs like computing rollups.<div class=""><br class=""><div><blockquote type="cite" class=""><div class="">On May 6, 2016, at 9:21 AM, Jay Shaughnessy <<a href="mailto:jshaughn@redhat.com" class="">jshaughn@redhat.com</a>> wrote:</div><br class="Apple-interchange-newline"><div class="">
<meta content="text/html; charset=windows-1252" http-equiv="Content-Type" class="">
<div bgcolor="#FFFFFF" text="#000000" class="">
<br class="">
<font face="Calibri" class="">I always thought tenants were more akin to
grouping associated data, like everything for datacenter-1, or
company-x, and so users would have their queries limited to their
relevant data. If every feed has a different tenantid by default,
then wouldn't it be difficult to consolidate data in a view? I
know in H Alerting that tenantId is used more in the fashion I
discussed, and multi-tenant queries are not efficient. It seems
to me we'd be better off using a single default, like
"global-tenant".</font><br class="">
<br class="">
<div class="moz-cite-prefix">On 5/6/2016 8:21 AM, John Mazzitelli
wrote:<br class="">
</div>
<blockquote cite="mid:1301359407.1789963.1462537314274.JavaMail.zimbra@redhat.com" type="cite" class="">
<blockquote type="cite" class="">
<pre wrap="" class="">Can't you just consider the tenantId the same as the feedId? Or use some
fixed word, like 'global'? Please don't use the slashes, equal symbols and
others :)
</pre>
</blockquote>
<pre wrap="" class="">That's what I was thinking of doing to avoid requiring people to set the tenantId. They can still set tenantId if they want something different, but, I think I will default to the feed ID.
</pre>
<blockquote type="cite" class="">
<pre wrap="" class="">As for the inventory, currently the tenant is auto-created with the very
first call to the rest api. There is no dedicated endpoint to create the
tenant. The tenant id is obtained from the accounts component. Probably,
this will be changed to get the tenant id from the http header. So all you
need to do is to start inserting the data with the correctly set tenant id
header.
</pre>
</blockquote>
<pre wrap="" class="">Right. I would have to add that. Right now the agent only sends tenant ID header to metrics. Looks like I will need to send it to inventory as well.
I wonder if we need to start passing tenant ID around in the websocket commands too?
Peter/Juca - with all the work you are doing in cmdgw stuff - do you know if we need to add tenant ID to all the commands?
_______________________________________________
hawkular-dev mailing list
<a class="moz-txt-link-abbreviated" href="mailto:hawkular-dev@lists.jboss.org">hawkular-dev@lists.jboss.org</a>
<a class="moz-txt-link-freetext" href="https://lists.jboss.org/mailman/listinfo/hawkular-dev">https://lists.jboss.org/mailman/listinfo/hawkular-dev</a>
</pre>
</blockquote>
<br class="">
</div>
_______________________________________________<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=""></div></body></html>