jmeter-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Philippe Mouawad <philippe.moua...@gmail.com>
Subject Re: Creating HTTP API for JMeter
Date Sat, 03 Aug 2019 13:54:23 GMT
On Saturday, August 3, 2019, Felix Schumacher <
felix.schumacher@internetallee.de> wrote:

>
> Am 03.08.19 um 15:27 schrieb Philippe Mouawad:
> > Well,
> > It would be mainly for tester in read only mode to start with.
> > When I run a test I’d like to have those statistic:
> > - transactions error rate
> > - number of trans executed
> > - percentiles of those
> > - network sent/received
> >
> >
> > Then in write mode with authentification :
> > - stop test
> > - shutdown test
> > - put on hold ( not available yet)
> > - increase load (not available yet)
>
> My question targeted the how to gather those statistics inside JMeter.
> Do we add some framework like https://metrics.dropwizard.io/4.0.0/
>
> And then as a second step, how to present those values to the outside?

yes.
Micrometer is also an option we coupd use

>
> Felix
>
> >
> > Regards
> >
> > On Saturday, August 3, 2019, Felix Schumacher <
> > felix.schumacher@internetallee.de> wrote:
> >
> >> Am 02.08.19 um 22:53 schrieb Philippe Mouawad:
> >>> Hello,
> >>> What do you think of creating an HTTP API for JMeter that could:
> >>>
> >>>    - Display what Summariser shows in browser
> >>>    - Enhance this summary with more statistics
> >>>    - get status of jmeter (test running, waiting)
> >>>    - possible health information
> >>>    - in the future some control on distributed testing
> >>>
> >>> I am looking for the lightest embeddable server  that we could use:
> >>>
> >>>    - I thought about Micronaut but it brings a lot of dependencies that
> >>>    could trigger issues for some protocols since we don't have a
> separate
> >>>    Classloader (which would be another story)
> >>>    - Undertow looks rather minimal but API development is not as fast
> as
> >>>    with Micronautd
> >> Before we think about embedding an http server (why not tomcat?), we
> >> should look at what information we want to gather and present and how
> >> that should be accomplished.
> >>
> >> And what about security concerns? To whom do we want to display those
> >> values and how are they authenticated and authorized?
> >>
> >> Felix
> >>
> >>>
> >>> Do you have other ideas ?
> >>>
> >>> Regards
> >>> Philippe
> >>>
> >
>


-- 
Cordialement.
Philippe Mouawad.

Mime
  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message