On 2/26/2013 5:00 PM, Chris Radek wrote: > I guess I just want us to consider what problem we are solving for > the user before we decide on an architecture. I saw a lot of > "obviously syslog!" and I didn't understand why we were jumping > right to there, because it didn't seem to me that it solves any of > our primary problems. I realize we are coming at this with opposite > approaches - that's good!
Michael's original message said - all messages shall be reported through a single channel, including its reporting level, and preferrably its origin too - setting a message reporting level shall apply to all elements in a uniform way I think this is an admirable set of requirements in itself, especially but not exclusively for the more distributed systems we are imagining. It addresses channels and messages in them, not destinations. Pretty general stuff. Certainly syslog is one possible destination for messages (based on reporting level, say) but it isn't not the only one. Perhaps as important as asking "what problem does this architecture solve," Chris, it is important to ask "what usage pattern would this architecture exclude?" Regards, Kent ------------------------------------------------------------------------------ Everyone hates slow websites. So do we. Make your web apps faster with AppDynamics Download AppDynamics Lite for free today: http://p.sf.net/sfu/appdyn_d2d_feb _______________________________________________ Emc-developers mailing list Emc-developers@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/emc-developers
