<div dir="ltr">Just a precision because I'm not sure if I was clear on that: the idea is to mix series based on a list of ids, or tags. Not *everything*</div><div class="gmail_extra"><br><div class="gmail_quote">On Tue, Aug 30, 2016 at 5:39 PM, Joel Takvorian <span dir="ltr"><<a href="mailto:jtakvori@redhat.com" target="_blank">jtakvori@redhat.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div dir="ltr"><div>I agree that you won't want to mix everything, but you can still adopt some groupings that are meaningful, for instance group all front-end servers into a front-end availability series, and all back-ends into another series.</div><div><br></div><div>Moreover, once you get all the availability as ratio, it's easy to map to a binary availability if it's what you're looking for. The REST api will provide the data, then it's up to you to display what is the most relevant. I think ratio datapoints is an easy-to-use, yet complete, information.</div><span class="HOEnZb"><font color="#888888"><div><br></div><div>Joel</div></font></span></div><div class="HOEnZb"><div class="h5"><div class="gmail_extra"><br><div class="gmail_quote">On Tue, Aug 30, 2016 at 5:16 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>
So if I have 8 MySQLs, 4 primaries, 4 replicas. One primary is down and the replica of that set is down as well. I request Availability of my datastore and I get 80% UP. If I had two replicas down instead, I would get 80% UP. There's a huge difference in these scenarios.<br>
<br>
I'm not a fan of percents for that simple reason. Is my service up? Yes, it's 99% up, only all the front-end servers are down.. ugh.<br>
<br>
- Micke<br>
<div><div><br>
----- Original Message -----<br>
From: "John Sanda" <<a href="mailto:jsanda@redhat.com" target="_blank">jsanda@redhat.com</a>><br>
To: "Discussions around Hawkular development" <<a href="mailto:hawkular-dev@lists.jboss.org" target="_blank">hawkular-dev@lists.jboss.org</a>><br>
Sent: Tuesday, August 30, 2016 4:11:07 PM<br>
Subject: Re: [Hawkular-dev] Availability metrics: aggregate stats series<br>
<br>
I like the idea of aggregated availabilities, but I don’t know that it can easily be simplified to up/down. Let’s say we have 3 Cassandra nodes deployed with replication_factor = 1. If one node goes down we are at 66% availability.<br>
<br>
> On Aug 29, 2016, at 3:24 AM, Joel Takvorian <<a href="mailto:jtakvori@redhat.com" target="_blank">jtakvori@redhat.com</a>> wrote:<br>
><br>
> Hello all,<br>
><br>
> I'm still aiming to add some features to the grafana plugin. I've started to integrate availabilities, but now I'm facing a problem when it comes to show aggregated availabilities ; for example think about an OpenShift pod that is scaled up to several instances.<br>
><br>
> Since availability is basically "up" or "down" (or, to simplify with the other states such as "unknown", say it's either "up" or "non-up"), I propose to add this new feature: availability stats with aggregation. The call would be parameterized with an aggregation method, which would be either "all of" or "any of": with "all of" we consider that the aggregated series is UP when all its parts are UP.<br>
><br>
> It would require a new endpoint since the AvailabilityHandler currently only expose stats queries with metric id as query parameter - not suitable for multiple metrics.<br>
><br>
> Any objection or remark for this feature?<br>
><br>
> Joel<br>
> ______________________________<wbr>_________________<br>
> hawkular-dev mailing list<br>
> <a href="mailto:hawkular-dev@lists.jboss.org" target="_blank">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/mailma<wbr>n/listinfo/hawkular-dev</a><br>
<br>
<br>
______________________________<wbr>_________________<br>
hawkular-dev mailing list<br>
<a href="mailto:hawkular-dev@lists.jboss.org" target="_blank">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/mailma<wbr>n/listinfo/hawkular-dev</a><br>
<br>
______________________________<wbr>_________________<br>
hawkular-dev mailing list<br>
<a href="mailto:hawkular-dev@lists.jboss.org" target="_blank">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/mailma<wbr>n/listinfo/hawkular-dev</a><br>
</div></div></blockquote></div><br></div>
</div></div></blockquote></div><br></div>