Jeremy Zawodny wrote: > Hmm. > > Having better logging in drizzle would help this a lot. Not having > syslog in mysql has been a pain in various a$$es for years. But being > able to do something like Apache to files or syslogs which can then be > collected by tools that drizzle ships with would be most useful, both > for the end user's deployment and in a phone-home context. > > I'd be maybe able and willing to help with such a beast. Are there > better logging plans afoot?
Mark Atwood is working on pluggable logging as we speak, actually... > On Mon, Dec 22, 2008 at 10:35 PM, Matthew Sacks <[email protected] > <mailto:[email protected]>> wrote: > > I think this would be a valuable feature if we also included automated > bug reporting functionality. > I was also going to suggest (if it isn't already present) a monitoring > infrastructure. Since we are talking about potentially thousands of > drizzled's distributed across networks, it would be valuable to tie > them together using a management layer. Similar to jconsole + JMX with > Java. Some kind of remote monitoring plugin. > > I am not sure what impact such features would have on performance, but > they could be optional and turned > > Again, information gathering, bug reporting, monitoring. Perhaps three > independent frameworks should be built in for quality of service and > application monitoring features. > > [M) > > On Mon, Dec 22, 2008 at 3:51 PM, Andy Lester <[email protected] > <mailto:[email protected]>> wrote: > > > > On Dec 22, 2008, at 12:34 PM, Jeremy Zawodny wrote: > > > >> I think this could be valuable information that'd help make decisions > >> about Drizzle usage in the Real World. In fact, if it is aged > properly, > >> you'd get a nice window into how folks are deploying it as time > marches on > >> and hardware evolves. That'd give us a bit better idea about > what matters > >> and what doesn't. > > > > > > I agree with the general principle of "could be valuable", but by my > > thinking, if you don't have specific questions that you want to have > > answered, then you don't know what data to collect. > > > > I'm just trying to push for more forethought in what to dig into, > rather > > than just "let's collect some data," ESPECIALLY with something as > > potentially inflammatory as phoning home. > > > > For example: Do we collect what compiler they're building with? > Why or why > > not? > > > > -- > > Andy Lester => [email protected] <mailto:[email protected]> => > www.petdance.com <http://www.petdance.com> => AIM:petdance > > > > > > > > > > _______________________________________________ > > Mailing list: https://launchpad.net/~drizzle-discuss > <https://launchpad.net/%7Edrizzle-discuss> > > Post to : [email protected] > <mailto:[email protected]> > > Unsubscribe : https://launchpad.net/~drizzle-discuss > <https://launchpad.net/%7Edrizzle-discuss> > > More help : https://help.launchpad.net/ListHelp > > > > _______________________________________________ > Mailing list: https://launchpad.net/~drizzle-discuss > <https://launchpad.net/%7Edrizzle-discuss> > Post to : [email protected] > <mailto:[email protected]> > Unsubscribe : https://launchpad.net/~drizzle-discuss > <https://launchpad.net/%7Edrizzle-discuss> > More help : https://help.launchpad.net/ListHelp > > > > ------------------------------------------------------------------------ > > _______________________________________________ > Mailing list: https://launchpad.net/~drizzle-discuss > Post to : [email protected] > Unsubscribe : https://launchpad.net/~drizzle-discuss > More help : https://help.launchpad.net/ListHelp _______________________________________________ Mailing list: https://launchpad.net/~drizzle-discuss Post to : [email protected] Unsubscribe : https://launchpad.net/~drizzle-discuss More help : https://help.launchpad.net/ListHelp
