<div dir="ltr">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 :)<div><br></div><div>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.</div><div><br></div><div>jk</div></div><div class="gmail_extra"><br><div class="gmail_quote">On Fri, May 6, 2016 at 12:30 PM, John Mazzitelli <span dir="ltr"><<a href="mailto:mazz@redhat.com" target="_blank">mazz@redhat.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">Now that Accounts is getting taken out, how is the agent to determine its tenant ID?<br>
<br>
The agent needs to know its tenant ID when inserting data into Hawkular Metrics.<br>
<br>
Right now, the agent makes an explicit http call to the Accounts URL to obtain the tenant of its user. If Accounts goes away, the only thing left that I can see is to make required the agent attribute "tenantId" in standalone.xml configuraiton of the agent subsystem.<br>
<br>
Is that correct? There is no other way to get the tenant ID of a user now, I guess.<br>
<br>
(for what its worth, tenant IDs are important in the Open Shift use-case)<br>
_______________________________________________<br>
hawkular-dev mailing list<br>
<a href="mailto:hawkular-dev@lists.jboss.org">hawkular-dev@lists.jboss.org</a><br>
<a href="https://lists.jboss.org/mailman/listinfo/hawkular-dev" rel="noreferrer" target="_blank">https://lists.jboss.org/mailman/listinfo/hawkular-dev</a><br>
</blockquote></div><br></div>