9:34 a.m.
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.
On May 6, 2016, at 9:21 AM, Jay Shaughnessy
<jshaughn(a)redhat.com> wrote:
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".
On 5/6/2016 8:21 AM, John Mazzitelli wrote:
>> 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 :)
> 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.
>
>> 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.
> 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
> hawkular-dev(a)lists.jboss.org <mailto:hawkular-dev@lists.jboss.org>
> https://lists.jboss.org/mailman/listinfo/hawkular-dev
<https://lists.jboss.org/mailman/listinfo/hawkular-dev>
>
_______________________________________________
hawkular-dev mailing list
hawkular-dev(a)lists.jboss.org
https://lists.jboss.org/mailman/listinfo/hawkular-dev