Not that I think this is a bad idea, but it is the first I have heard about the per tenant metrics. Where is this feature request/requirement coming from? I’d just like some context.
On Jan 30, 2017, at 5:50 AM, Heiko W.Rupp <hrupp@redhat.com> wrote:

Hey,

what internal stats of the Hawkular metrics do we currently collect?
I think Joel did some work for the C* part.

What I think we need is
- number of data points stored on a per tenant basis.
Resolution could be something like "last minute" or
"last 5 minutes" I.e. not realtime updates in the table.
- Total number of data points (i.e. sum over all tenants)

  • Query stats. This is probably more complicated, as
    querying on metrics that are still in some buffer is
    cheaper than over 3 years of raw data.
    To get started I'd go with # of queries per tenant and global
    Those could perhaps be differentiated on

    • raw endpoint
    • stats endpoint

  • What about alerting? More alert definitions certainly
    need more cpu, so number of alert definitions per tenant
    and total would be another pair.

    • does number of fired alerts also make sense?

The idea behind those is to get some usage figures of the
shared resource "Hawkular metrics" and then to be able to
charge them back onto individual tenants e.g. inside of
OpenShift.

_______________________________________________
hawkular-dev mailing list
hawkular-dev@lists.jboss.org
https://lists.jboss.org/mailman/listinfo/hawkular-dev