On 22 Feb 2014, at 18:12, Göran Krampe <[email protected]> wrote: > Hi! > > On 02/22/2014 05:26 PM, Pharo4Stef wrote: >> Hi goran >> >> There are only two questions: >> 'Why when I load code do I have to open the transcript before to see >> the shadow and undeclared. >> and why I cannot click on an object and jump to the broken code?" >> >> Now with SimpleLogger I imagine that I cannot log compiler shadow, don’t you >> :). > > I am not quite sure what you are saying... Ah, you mean logging objects > instead of strings? Sure, I didn't say SimpleLog was BETTER, I just said you > didn't look at it and thus may be missing out on nice stuff that you can > steal :)
I’m currently :) In fact I read all the other frameworks except his ones. > - Using syslog levels, it is very standard and logging these days of clouds > do NOT stay on the local machine. > - Stealing the syslog emitter, it is just 20 lines of code. > - Stealing log file rotation perhaps? I think its in there. > - Stealing whatever else seems good. Yes I was reading the code and I will package that in extensions. Now I do not know UDP and others. > Having log objects in the image is great. > >> 100 timesRepeat: [Goran repeatAfter: me what: ‘String sucks, string are dead >> objects’] > > Well, do remember that logs in a "system world" end up getting routed through > syslog (and tons of variations on that theme) and eventually end up in event > collecting systems etc - just look at fluentd.org to understand what I mean. Indeed this is orthogonal to me. And I want to kill Transcript show > So actually, I would make sure that SimpleLogger could also easily log in > JSON, let me quote from fluentd: It is just a simple formater. Norbert is using that (if I’m correct) to collect data from his servers with SystemLogger. > > "Fluentd treats logs as JSON, a popular machine-readable format. It is > written primarily in C with a thin-Ruby wrapper that gives users flexibility. > > Fluentd’s performance has been proven in the field: its largest user > currently collects logs from 5000+ servers, 5 TB of daily data, handling > 50,000 msgs/sec at peak time." > >> I’m coding in Smalltalk and not in perl! > > In fact, now that I am looking at SimpleLog I realize we could have had an > emitter that collected objects and just let "message" be whatever - and send > asString or asJSON to it when it reaches the emitter instead. :) > Now if you want to have syslog output this is probably one method definition > in a new formatter in our nice frameworks. >> Do you have an output that shows what is needed for sysLog? because I can >> add a package for sysLog outputter. > > Its very short code. Just steal it. I attached all the code as an .st fileout > so that you can get it trivially. Its the SLSyslogSender class. Yes I will. If you want I can give you access to the repo. After I want to avoid to have dependencies to morph because the tiny core should be in the core of Pharo and all the rest pluggable. I want to use SystemLogger for Opal too. > The SLLogWatchDog is a trivial "send an email if a certain level is reached" > with some bundling etc. Yes I saw :) Nice extension. > SLLogFile has log file rotation. Yes I saw I will rewrite it to use FS. > SLLogMorph is the simple search and filter UI. Yes I will probably steal it too. > > regards, Göran > > > <SimpleLog.st>
