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?
Certainly, it could have some sense to have these figures.
These kind of data is "low hanging fruit" in the sense that adding an endpoint
to query them is straightforward.
We can add a "/count" suffix to some endpoint to get the # instead the list or a
similar.
Is there a preferred way to name the endpoint for this ?
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(a)lists.jboss.org
https://lists.jboss.org/mailman/listinfo/hawkular-dev