Thanks Ralph. It was good explanation. Regards, Yuvaraj
Yuvaraj Vanarase, Lead Technology - Software Phone: +91.20.40262000 Ext 2305|Mobile: +91.9850818870 | http://www.synechron.com SYNECHRON - - Top 15 Best IT Employers for 5 consecutive years (link). - Celebrating 10 Years! -----Original Message----- From: logback-user-boun...@qos.ch [mailto:logback-user-boun...@qos.ch] On Behalf Of logback-user-requ...@qos.ch Sent: Monday, November 28, 2011 10:22 PM To: logback-user@qos.ch Subject: Logback-user Digest, Vol 2, Issue 40 Send Logback-user mailing list submissions to logback-user@qos.ch To subscribe or unsubscribe via the World Wide Web, visit http://mailman.qos.ch/mailman/listinfo/logback-user or, via email, send a message with subject or body 'help' to logback-user-requ...@qos.ch You can reach the person managing the list at logback-user-ow...@qos.ch When replying, please edit your Subject line so it is more specific than "Re: Contents of Logback-user digest..." Today's Topics: 1. EventLogger usage (Yuvaraj Vanarase) 2. Re: EventLogger usage (Ralph Goers) 3. Substituting class/method names in logback log files with original names when deploying obfuscated code (Christopher BROWN) 4. Re: Substituting class/method names in logback log files with original names when deploying obfuscated code (Chris Pratt) ---------------------------------------------------------------------- Message: 1 Date: Mon, 28 Nov 2011 06:19:23 -0600 From: Yuvaraj Vanarase <yuvaraj.vanar...@synechron.com> To: "logback-user@qos.ch" <logback-user@qos.ch> Subject: [logback-user] EventLogger usage Message-ID: <5669c1899552264ca699f54a78e534d40f948b3...@dfw1mbx18.mex07a.mlsrvr.com> Content-Type: text/plain; charset="us-ascii" Hi, Not able to understand the connection between MDC and EventLogger (slf4j). What I understood is, instead of doing separate log requests, one can populate EventData object and log the object by EventLogger. Anybody could illustrate this concept please? Regards, Yuvaraj Yuvaraj Vanarase, Lead Technology - Software Phone: +91.20.40262000 Ext 2305|Mobile: +91.9850818870 | http://www.synechron.com SYNECHRON - - Top 15 Best IT Employers for 5 consecutive years (link<http://www.synechron.com/news/news_best_employer_sep2011.htm>). - Celebrating 10 Years! -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://mailman.qos.ch/pipermail/logback-user/attachments/20111128/73be36e4/attachment-0001.html> ------------------------------ Message: 2 Date: Mon, 28 Nov 2011 06:53:40 -0800 From: Ralph Goers <rgo...@apache.org> To: logback users list <logback-user@qos.ch> Subject: Re: [logback-user] EventLogger usage Message-ID: <11dc85d2-8250-4816-8dbb-0170746d3...@apache.org> Content-Type: text/plain; charset="windows-1252" The data in the MDC will be associated with every log record you generate. We use that for the user's login id, the name of the product, the host name, etc. IOW, the things that are constant during the work that is going on. EventData is for something you want to record in a single log record in addition to the MDC data. So if the user is logging in we have a login event, if they are performing a transfer of money from one account to another then the EventData contains the amount, the transfer-to account number and the transfer-from account number. If they are performing an SSO to another system the EventData would include information about that. In other words, we use it for Audit logging. You will notice that EventLogger uses a Marker. This allows us to set up a TurboFilter to always accept those records. We then route them via the EventLogger to their own location, separate from Debug log records. Unfortunately, their are two major issues we have with this design: 1. The MarkerFilter (actually the Marker itself) is synchronized and becomes a huge bottleneck under load. 2. Logback loses events when it is reconfigured, which really isn't acceptable for audit logging. Ralph On Nov 28, 2011, at 4:19 AM, Yuvaraj Vanarase wrote: > Hi, > > Not able to understand the connection between MDC and EventLogger (slf4j). > What I understood is, instead of doing separate log requests, one can > populate EventData object and log the object by EventLogger. > > Anybody could illustrate this concept please? > > Regards, > Yuvaraj > > Yuvaraj Vanarase, > Lead Technology ? Software > Phone: +91.20.40262000 Ext 2305|Mobile: +91.9850818870 | > http://www.synechron.com > SYNECHRON - > - Top 15 Best IT Employers for 5 consecutive years (link). > - Celebrating 10 Years! > > _______________________________________________ > Logback-user mailing list > Logback-user@qos.ch > http://mailman.qos.ch/mailman/listinfo/logback-user -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://mailman.qos.ch/pipermail/logback-user/attachments/20111128/696d9702/attachment-0001.html> ------------------------------ Message: 3 Date: Mon, 28 Nov 2011 16:31:47 +0100 From: Christopher BROWN <br...@reflexe.fr> To: LogBack Users list <logback-user@qos.ch> Subject: [logback-user] Substituting class/method names in logback log files with original names when deploying obfuscated code Message-ID: <cahl_zcphjkzqs79bq8bt8w413czrhnaphq8klfaaploxzxp...@mail.gmail.com> Content-Type: text/plain; charset="utf-8" Hello, What would be the best way to handle logging with logback when deploying obfuscated code? For example, with YGuard, when the obfuscator runs, it outputs a mapping file of obfuscated code (class names, method names, etc) to unobfuscated code. When a stacktrace or just any logging trace is output, the class/method names are obviously obfuscated. As it's possible to deploy this mapping with the code, say embedded in the same ".jar", all the information I would need is available. Without too much re-writing of code (default formatting with logback), what would be the best way to dynamically replace matching class/method names? Thanks, Christopher -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://mailman.qos.ch/pipermail/logback-user/attachments/20111128/160a1696/attachment-0001.html> ------------------------------ Message: 4 Date: Mon, 28 Nov 2011 08:50:36 -0800 From: Chris Pratt <thechrispr...@gmail.com> To: logback users list <logback-user@qos.ch> Subject: Re: [logback-user] Substituting class/method names in logback log files with original names when deploying obfuscated code Message-ID: <caaldy0xyutwsz3wpee0pcin7mfnjv9xqye971kgd7rwrsod...@mail.gmail.com> Content-Type: text/plain; charset="iso-8859-1" You do realize that if you supply the mapping file to the end user, there is really no reason to obfuscale the code in the first place. They'll have everything they need to properly un-obfuscate and decompile it. (*Chris*) On Nov 28, 2011 7:32 AM, "Christopher BROWN" <br...@reflexe.fr> wrote: > Hello, > > What would be the best way to handle logging with logback when deploying > obfuscated code? > > For example, with YGuard, when the obfuscator runs, it outputs a mapping > file of obfuscated code (class names, method names, etc) to unobfuscated > code. When a stacktrace or just any logging trace is output, the > class/method names are obviously obfuscated. As it's possible to deploy > this mapping with the code, say embedded in the same ".jar", all the > information I would need is available. > > Without too much re-writing of code (default formatting with logback), > what would be the best way to dynamically replace matching class/method > names? > > Thanks, > Christopher > > _______________________________________________ > Logback-user mailing list > Logback-user@qos.ch > http://mailman.qos.ch/mailman/listinfo/logback-user > -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://mailman.qos.ch/pipermail/logback-user/attachments/20111128/c87b6209/attachment.html> ------------------------------ _______________________________________________ Logback-user mailing list Logback-user@qos.ch http://mailman.qos.ch/mailman/listinfo/logback-user End of Logback-user Digest, Vol 2, Issue 40 ******************************************* _______________________________________________ Logback-user mailing list Logback-user@qos.ch http://mailman.qos.ch/mailman/listinfo/logback-user
