Khalid Bahey is well on his way to getting a patch into Drupal 6 for spitting out logging of watchdog entries so that:
1. They can be routed to a different source other than the database, from a flat file to syslog support. The watchdog table can crush many sites.
2. Actions can be taken depending on the messages. Get notification via email, IM, pager, etc. depending on the severity levels of messages in your watchdog.
This will be a fantastic feature for Drupal 6....but really, we need it today for Drupal 5 as well. I've spoken with Khalid and he's willing to backport both the patch as well as the supporting modules. The plan of attack is:
* Wait till the patch gets in to 6.x.
* Create a project on d.o for the two contrib modules syslog, and email
* Backport the modules to 5.x.
* Create a backport of the 6.x patch for 5.x, and include it with the modules's 5.x version
If you are interested in helping fund this backport, please use this chipin page or the widget below to donate. As well, please do checkout the the issue for this patch and help test for Drupal 6.
[埋込みオブジェクト:http://www.chipin.com/widget/id/fd70241e3b0ae4d4]
Comments
Great for security audits too
Among the additional benefits is the ability to log centrally to a monitoring and logging server which would allow system wide debugging and auditing.
Thanks to Khalid and Boris for pushing this forward.
Cheers,
Kieran
To seek, to strive, to find, and not to yield
New Drupal career! Drupal profile builders.
Try pre-configured and updatable profiles on CivicSpaceOnDemand
I've kicked in 150ドル
I believe we need this module, and FireBright has kicked in 150ドル. I'll kick in another 150ドル is there's interest (total 300ドル) to get us to the goal.
Jonathan
We also need this & would like to support this
How much is actually needed to make it happen?
About 1200ドル
Depending on how many of the other co-dependent modules (email notification, syslog, etc. etc.) all get backported. That number is for all the notification methods. Email me if you have any other questions or features you would like to see....
Updates made...
...to Reverse Bounty Status of Projects Needing Financing.
Please feel free to make any changes/edits as you see fit and good luck with the fundraising!
Walt Esquivel, MBA; MA; President, Wellness Corps; Captain, USMC (Veteran)
50ドル Hosting Discount Helps Projects Needing Financing
Walt Esquivel, MBA; MA; President, Wellness Corps; Captain, USMC (Veteran)
50ドル Hosting Discount Helps Projects Needing Financing
Done
IO1 Limited has sponsored this to the tune of USD576 this leaves 150ドル missing which jlambert has said they will put in. Look forward to seeing it finished.
Great for filtering
This would be ideal for filtering between the severity of watchdog messages, for example log only critical messages.
Great idea and indeed a +1 from me
BioALIEN
Buy, sell and trade with other webmasters: WebMasterTrader.com
Dee :: iScene Drupal Agency
Patch is in core now
The patch is now finalized and is in core for 6.x.
Here are resources and links to documentation.
~~
Drupal development and consulting 2bits.com
Personal Baheyeldin
Drupal performance tuning, development, customization and consulting: 2bits.com, Inc..
Personal blog: Baheyeldin.com.
Questions
OK, some questions for those who want this feature:
Do you want this to be against 5.1, or the HEAD of 5.x? (They are different, I've had patches that would not apply against 5.1 if they are written against 5.x HEAD).
This patch does changes the values of the severity column in the watchdog table to conform to the RFC standard. That is not a problem in itself, but when the time comes to upgrade from 5.x to 6.x, this will be done again and will mangle some of these values. Not sure how to avoid that.
Thoughts?
Drupal development and consulting 2bits.com
Personal Baheyeldin
Drupal performance tuning, development, customization and consulting: 2bits.com, Inc..
Personal blog: Baheyeldin.com.
Answer
Do you want this to be against 5.1, or the HEAD of 5.x? (They are different, I've had patches that would not apply against 5.1 if they are written against 5.x HEAD).
Does this mean it will stop working with the next release of 5.x?
Personally I would like to see it against the current stable release i.e. 5.1
This patch does changes the values of the severity column in the watchdog table to conform to the RFC standard. That is not a problem in itself, but when the time comes to upgrade from 5.x to 6.x, this will be done again and will mangle some of these values. Not sure how to avoid that.
Will leave this to people who have a clue (i.e. not me)
Go for it
Against 5.1 stable. If there are minor updates when 5.2 comes out, we'll want to update this...but folks that use it can help with that as well.
Watchdog tables get truncated fairly often anyway. Getting mangled values on a 6.x upgrade shouldn't be much of an issue.
Done...
Hey everybody:
Well, I said I would and a promised I did - just kicked up the last of that bounty for you. We're at 1200ドル (100%!).
A special thanks to everyone for making this happen. I'll get this patch tested and provide any feedback needed today or tomorrow.
Again, thanks!
Jonathan
No, not enough
No, you still need to chip in more.
Well, not in money, ... but please check my questions and answer what you think.
Drupal development and consulting 2bits.com
Personal Baheyeldin
Drupal performance tuning, development, customization and consulting: 2bits.com, Inc..
Personal blog: Baheyeldin.com.
5.1 patch is now here
You can get the 5.1 patch from #149341.
Drupal development and consulting 2bits.com
Personal Baheyeldin
Drupal performance tuning, development, customization and consulting: 2bits.com, Inc..
Personal blog: Baheyeldin.com.