You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@jmeter.apache.org by Philippe Mouawad <ph...@gmail.com> on 2014/01/01 22:01:35 UTC

Regarding potential vote on Graphite Listener inclusion

Do you agree on this:

-----------------------------------------------------------------------------------------------------------------------------------------------------
The JMeter team is asking for your opinion regarding the inclusion in
JMeter of a Graphite Listener.
Graphite overview can be found here:
- http://graphite.readthedocs.org/en/latest/overview.html

This listener will allow JMeter to dump summary of response time and status
every second:

1) Per second:
- min response time
- max response time
- percentile 90 for response time rolling over last 100 values
- percentile 95 for response time rolling over last 100 values
- successful requests
- failed requests
- total request

2) Listener will also send the following metrics which are not based
on a variation per second:
- ActiveThreads
- Stopped Threads
- Started Threads

More details can be found here:
- https://issues.apache.org/bugzilla/show_bug.cgi?id=55932


To give you opinion, select one of the 3 options:
[+1] I support this inclusion in JMeter core
[0] It should be available within a third-party library
[-1] I vote against any inclusion


Vote is open for 1 week.

Regards
Apache JMeter Team
-----------------------------------------------------------------------------------------------------------------------------------------------------

Regards

Re: Regarding potential vote on Graphite Listener inclusion

Posted by Philippe Mouawad <ph...@gmail.com>.
ok, let's close this thread


On Wed, Jan 1, 2014 at 10:29 PM, sebb <se...@gmail.com> wrote:

> On 1 January 2014 21:01, Philippe Mouawad <ph...@gmail.com>
> wrote:
> > Do you agree on this:
>
> No.
>
> We need to find out what the requirements are first, not vote on a
> specific solution.
>
> We have no idea how many people really need "instant" reporting.
>
> It's unlikely that a user will vote against a proposal to add
> functionality unless it impacts them directly.
> They won't generally see the developer downsides, for example that
> time spent on one feature means less time to spend on another feature
> which may be much more important to the majority.
>
> Feature creep can become very expensive in resources.
> If one is not careful, JMeter could become bloated and unwieldy.
>



-- 
Cordialement.
Philippe Mouawad.

Re: Regarding potential vote on Graphite Listener inclusion

Posted by sebb <se...@gmail.com>.
On 1 January 2014 21:01, Philippe Mouawad <ph...@gmail.com> wrote:
> Do you agree on this:

No.

We need to find out what the requirements are first, not vote on a
specific solution.

We have no idea how many people really need "instant" reporting.

It's unlikely that a user will vote against a proposal to add
functionality unless it impacts them directly.
They won't generally see the developer downsides, for example that
time spent on one feature means less time to spend on another feature
which may be much more important to the majority.

Feature creep can become very expensive in resources.
If one is not careful, JMeter could become bloated and unwieldy.