6:04 p.m.
I am using hawkular-services 0.11 (metrics 0.19). When i call: GET
/hawkular/metrics/strings/{id}/raw i get different responses depending on
whether i set the limit or not.
- limit not set = get data
- limit set to 5 = get no data
I would of expected to get back the same data, since i only have one data
point, so never hit my upper limit of 5. Is this how it works? or have i
misunderstood "limit"
Gist logs:
- https://gist.github.com/garethahealy/a53d260ad51eef44b7df39fb450cf5b0
Cheers.
9:52 p.m.
Hello Gareth,
I am was able to create a test and reproduce the problem. So it is bug that
looks related to using ascending order with a limit. I created a JIRA
ticket to track the issue: https://issues.jboss.org/browse/HWKMETRICS-474
. We will most likely push the fix to 0.19.0 branch.
Thanks for reporting the problem!
Thank you,
Stefan Negrea
On Wed, Sep 7, 2016 at 11:04 AM, Gareth Healy <garethahealy(a)gmail.com>
wrote:
I am using hawkular-services 0.11 (metrics 0.19). When i call: GET
/hawkular/metrics/strings/{id}/raw i get different responses depending on
whether i set the limit or not.
- limit not set = get data
- limit set to 5 = get no data
I would of expected to get back the same data, since i only have one data
point, so never hit my upper limit of 5. Is this how it works? or have i
misunderstood "limit"
Gist logs:
- https://gist.github.com/garethahealy/a53d260ad51eef44b7df39fb450cf5b0
Cheers.
_______________________________________________
hawkular-dev mailing list
hawkular-dev(a)lists.jboss.org
https://lists.jboss.org/mailman/listinfo/hawkular-dev
1:01 a.m.
Hello Gareth,
I was able to find the problem; the fix is already merged in master and
0.19.x release branch.
Also, I just released Hawkular Metrics 0.19.1.Final with the fix. The build
should be picked up in the next Hawkular Services release. If you do not
want to wait that long you could get the binaries for Hawkular Metrics
0.19.1.Final and manually update the Hawkular Services distribution.
Here is where you can find the binary distros for Metrics:
http://origin-repository.jboss.org/nexus/content/repositories/public/org/...
Thank you,
Stefan Negrea
On Wed, Sep 7, 2016 at 2:52 PM, Stefan Negrea <snegrea(a)redhat.com> wrote:
Hello Gareth,
I am was able to create a test and reproduce the problem. So it is bug
that looks related to using ascending order with a limit. I created a JIRA
ticket to track the issue: https://issues.jboss.org/browse/HWKMETRICS-474
. We will most likely push the fix to 0.19.0 branch.
Thanks for reporting the problem!
Thank you,
Stefan Negrea
On Wed, Sep 7, 2016 at 11:04 AM, Gareth Healy <garethahealy(a)gmail.com>
wrote:
> I am using hawkular-services 0.11 (metrics 0.19). When i call: GET
> /hawkular/metrics/strings/{id}/raw i get different responses depending
> on whether i set the limit or not.
>
> - limit not set = get data
> - limit set to 5 = get no data
>
> I would of expected to get back the same data, since i only have one data
> point, so never hit my upper limit of 5. Is this how it works? or have i
> misunderstood "limit"
>
> Gist logs:
>
> - https://gist.github.com/garethahealy/a53d260ad51eef44b7df39f
> b450cf5b0
>
> Cheers.
>
> _______________________________________________
> hawkular-dev mailing list
> hawkular-dev(a)lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/hawkular-dev
>
>
10:38 a.m.
On 09/08/2016 01:01 AM, Stefan Negrea wrote:
Also, I just released Hawkular Metrics 0.19.1.Final with the fix.
The
build should be picked up in the next Hawkular Services release. If you
do not want to wait that long you could get the binaries for Hawkular
Metrics 0.19.1.Final and manually update the Hawkular Services distribution.
We might have a Hawkular Services release today, as Lucas mentioned
yesterday that he needs to expedite a fix for Alerts.
- Juca.
2795
days inactive
2796
days old
3 comments
3 participants
participants (3)
-
Gareth Healy -
Juraci Paixão Kröhling -
Stefan Negrea