Hi Beth,

Yes it is possible, log4net supports an smtp appended that can be used to email logged events. If you look in the log4net.config file in the root of the web you'll see information in comments about how it can be configured. Note that if you customize the log4net.config file you should keep a copy of it as log4net.backup.config so you can restore your customizations easily after upgrades.

However, that said, it will probably be very annoying receiving that many emails. I know my log is very noisy with things poking at the site and mangling url fragments together resulting in lots of page not found errors. I find it easier to just review my logs several times a day and I clear the log after each time I review it.

I'm actually working on support for logging to the database as part of my effort for web farm support.

Hope that helps,

Joe

Hi Jamie,

Sorry but I'm not increasing the scope of this right now. This is being done as a step towards web farm support. You can configure smtp today but I have no solution to reduce the noise and that is a different goal than the one I'm working on for database logging right now.

Maybe after the database logging is done it will be possible for people to implement their own custom solutions to poll the log data and send email if errors that meet a criteria of their choosing.

Best,

Joe

Hi Jamie,

It occurred to me after pondering this a bit that the best way to implement an smtp log appender with custom filtering would be to copy the code for the log4net SMTPAppender and modify it and compile it into a class library. log4net is open source and the appender code is not all that complex. Copy the code change the namespace and compile it into your own class library then configure it in the log4net.config, verify it works and then start tinkering.

The thing that makes it messy is having to process the error detail string looking for things like "pagenotfound" because there isn't some unique error code to go by and the messiness is made more difficult because environments in different languages would have different error strings. This kind of thing makes it difficult for me to think about implementing as something included in mojoPortal, but for someone implementing something for their own specific needs and language it would not be difficult.

Best,

Joe