Returning Usable Errors to OSLineToken Fetchlet

Question

My Java Programs that are called via OSLineToken Fetchlet need some exception handling work. Today, they simply throw an exception if something goes wrong. This results in a rather ugly Metric's Collection error with a full stack trace.
My goal is to:
- Write a "simple" error to the user
- Write a full stack trace to the emagent.trc file
It seems like System.err goes to emagent.trc but System.out does not and the only flag I can use is to indicate whether System.out should go to the metric collection error or ONLY System.err.
So, if I were to do something like:
System.err.println("Something horrible happened");
System.exit(1)
The Metric Collection Error would have the single line. But the emagent.trc file would only have the println.
If I did this:
exception.printStackTrace(System.err);
System.err.println("Something horrible happened");
System.exit(1)
Then my Metric Collection Error would get super busy when shown to the user, but emagent.trc would have my details.
Should I be using a separate logging framework and if I do, specify an alternate file for my logging and have my stack traces separated from the emagent.trc logging?
Thanks,
Paul

Answer 1

This approach basically works, but since the logger also forks to the console, the stack trace appears to get put into the message that is displayed in the GC console as well.
Still, this appears to be the direction to go.
Paul