> > 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.
Okay, I see. I always had trailing commas (but nothing in there).And it
works..
>
> >
> > 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.
Yes, that works too, and it helps me a lot, that was just the thing I
needed...
greetings, Leo
--
DSL Komplett von GMX +++ Superg�nstig und stressfrei einsteigen!
AKTION "Kein Einrichtungspreis" nutzen: http://www.gmx.net/de/go/dsl
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
