On Thu, 17 Mar 2005 10:11:33 +0100 (MET), Leo Leo <[EMAIL PROTECTED]> wrote:
> Hello!
>
> I am working with JMeter now a month or so, and I'd like to thank the
> developers for their great product. In order to provide you some
> user-feedback, I feel free to send you my personal wish list for JMeter. If
> you'd plan to develop these for JMeter, it would be fantastic
If they are not already in Bugzilla, please could you create them as
enhancement requests - much easier to keep track of items there.
[...]
> 3.) Custom logging:
[...]
> The other "problem" I have with custom logging is it's output format in
> jmeter.log. It work, but it always creates this traceback-info, that you
> know from java-exception. So if I do some logging, the jmeter.log becomes
> very large.
The log functions only generate traceback if you tell them to.
Use __log(text) - i.e. eliminate any trailing commas.
>
> What I'd like to have is a component, where you can log custom strings to
> jmeter.log (or any other logfile). It doesn't need to be a .jtl-File. Just
> think of the reverse-Function of "_StringFromFile". If it would be an extra
> component, this custom logging could be outside of samplers or listeners.
> And it would be great, if I could log that into a custom file.
>
> F.e. I would log the follwoing:
> Thread: ${__threadNum()}, User: ${login}, Menu: ${menuID} called.
>
> The output should be:
> yyyy/mm/dd hh:mm:ss Thread: 1, User: foo, Menu 3 called.
You can use variables in the sampler names, so this information can be
added to the JTL file, but I agree more options would be useful.
>
> 5.) Variable-Names do not work in filenames for listeners.
> So something like "${base_path}/testplan_errors.jtl" does not work
Known bug
[...]
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
