>I would like to send results in real time to some monitoring/reporting server while the test is running, not after it's done So the backendlistener is what you are looking for - but thats an interface that you would need to implement - all the interface specifies is heres the sample result - and you can do whatever you want with that.Jmeter provides you one implementation out of the box. (There are always cheap ways of configuring JMeter to write its results to a CSV file and copy that file and process it while the test is running to give you real time stats!)
>owever, back end listener by default does not appear to have an >option to save results to file You dont need it - you always ask jmeter to write results to a file (or any listener) - they all do the same thing. >Meaning a back end listener will do whatever >processing its supposed to do in non-GUI mode just the same as GUI mode but >w/o the GUI display? Yes - without the GUI display in JMeter. On Wed, Jul 13, 2016 at 1:29 PM, David Luu <[email protected]> wrote: > Deepak, to answer your questions: > > I would like to send results in real time to some monitoring/reporting > server while the test is running, not after it's done. I'd like to do that > in non-GUI mode. In my post I mention some existing solution (no source > code though), although I'd like to expand upon it like sending stats to a > riemann server. > > Regarding listeners saving results to file if configured, I did notice > that. However, back end listener by default does not appear to have an > option to save results to file or "run" while in non GUI mode. The GUI for > that element as shown in jmeter GUI does not have any fields to specify > saving to file unlike some other listeners like the graph/report ones. So I > assume for saving to file with backend listener, one would have to put that > functionality in one's own custom back end listener implementation? I doubt > it's there in the default graphite one. And so if that assumption is > correct, does that mean there's a way to make the custom back end listener > "run" in any mode (GUI and non-GUI)? > > Or am I misinterpreting? As you've clarified, listener's GUI doesn't get > used in non-GUI mode, but so that means all it's other functionality still > runs in non-GUI mode? Meaning a back end listener will do whatever > processing its supposed to do in non-GUI mode just the same as GUI mode but > w/o the GUI display? > > Pardon all these questions, I haven't had chance to try out and get the > (default) back end listener working, even in GUI mode, to test/confirm > myself. > > > On Wed, Jul 13, 2016 at 12:11 PM, Deepak Shetty <[email protected]> wrote: > > > >Came to know listeners don't work in CLI mode (e.g. > > To clarify - non gui-mode doesnt invoke the GUI parts of the listeners - > > but it does work in the sense that if you ask it to save results to a > file > > - it will . > > Im assuming you want to see your results while the test is running in > > non-gui mode . if you only care about results after your tests have > > finished then I would think your question doesnt apply - just save your > > results and load it in the listener of your choice . > > > > On Tue, Jul 12, 2016 at 5:12 PM, David Luu <[email protected]> wrote: > > > > > I've not really used listeners beside aggregate graph/report, view > > results > > > tree, and some jmeterplugins.org ones. Came to know listeners don't > work > > > in > > > CLI mode (e.g. > > > > > > > > > https://www.blazemeter.com/blog/top-2-techniques-get-jmeter-test-results-non-gui-mode > > > ) > > > > > > I recently came across an interesting post: > > > > > > > > > http://www.testautomationguru.com/jmeter-real-time-results-influxdb-grafana > > > > > > the author apparently modified the jmeter core package's Summariser > > > component to be able to also work like the backend listener in GUI > mode. > > > Unfortunately so far, it appears he/she only released the compiled > > changes, > > > but not the source code. > > > > > > Anyone do anything similar? It would be nice to base/build upon that > for > > > other data analysis purposes other than send to influxdb. And I'd > rather > > > not have to figure things out from scratch & reinventing the wheel via > > > poking through the jmeter source code head on. > > > > > >
