<div dir="ltr"><div>C* metrics are pushed to hawkular-metrics through a dropwizard reporter, there's no new endpoint as far as I can tell (it was mostly John's work, actually, not mine).</div><div>Of course (and except if I'm missing something) metrics wouldn't be on a per tenant basis here.</div><div><br></div><div class="gmail_extra"><br><div class="gmail_quote">On Mon, Jan 30, 2017 at 2:10 PM, Michael Burman <span dir="ltr"><<a href="mailto:miburman@redhat.com" target="_blank">miburman@redhat.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">Hi,<br>
<br>
Wouldn't it make sense in Metrics deployment to just send them to<br>
metrics? Then there's no need to create new endpoints, just fetch them<br>
as you would any other metric (from the internal admin tenant).<br>
<br>
- Micke<br>
<div class="HOEnZb"><div class="h5"><br>
<br>
On 01/30/2017 01:05 PM, Lucas Ponce wrote:<br>
>> What about alerting? More alert definitions certainly need more cpu, so<br>
>> number of alert definitions per tenant and total would be another pair.<br>
>> * does number of fired alerts also make sense?<br>
>><br>
> Certainly, it could have some sense to have these figures.<br>
><br>
> These kind of data is "low hanging fruit" in the sense that adding an endpoint to query them is straightforward.<br>
><br>
> We can add a "/count" suffix to some endpoint to get the # instead the list or a similar.<br>
><br>
> Is there a preferred way to name the endpoint for this ?<br>
><br>
><br>
>> The idea behind those is to get some usage figures of the<br>
>> shared resource "Hawkular metrics" and then to be able to<br>
>> charge them back onto individual tenants e.g. inside of<br>
>> OpenShift.<br>
>><br>
>> ______________________________<wbr>_________________<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/<wbr>mailman/listinfo/hawkular-dev</a><br>
>><br>
> ______________________________<wbr>_________________<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/<wbr>mailman/listinfo/hawkular-dev</a><br>
<br>
______________________________<wbr>_________________<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/<wbr>mailman/listinfo/hawkular-dev</a><br>
</div></div></blockquote></div><br></div></div>