----- Original Message ----- Sorry for my ignorance, is this just a special tenant that Hawkular Services uses? Is this just used for internal information that Hawkular Services? Is it really hard coded to this? or could be change it to something else which would not conflict with other tenants? eg something like '_hawkular' or '_hawkular-services'? For me, the bigger issue is around do we want to open up the HAM version we have in OpenShift to just anything? Right now we are in control of what goes in here. Its only Heapster and HOSA which can write metrics, and those are managed by an admin. This allows for the control of how often metrics and how many metrics are written. Knowing this information, an admin can factor in how much diskspace they may require. If we start to open this up to other users to write their own metrics, then I think we start to run into issues. We don't have an mechanism to only accept so many metric writes from going into Hawkular Metrics, so it might open things up to using more disk space than an admin would have originally allocated. If I am running my own OpenShift cluster, then sure, I might want to allow my own projects to reuse the internal Hawkular Metrics instance. Its my cluster here running my components. But for something like OpenShift Online, where there are separate users all running the same cluster, I think we would probably want to have checks in place to prevent users from using up too many of the resources used by the infrastructure components.