Best coding scheme for emailing error message

[Cervisiae Amatorem]

This is a dot net web app, where on a minor error it emails the team. It's not fatal or halting, just interesting. But I'm getting hundreds of emails a day and I need to fix that. It coded several different ways elsewhere in the code that all look clunky and kludgy, and I can't remember the "right" way to do it.

Here's what I need to do:

Code: Select all

                ' check for LastWebsiteStatusUnknown session variable
                ' if not present, send email, set LastWebsiteStatusUnknown session variable = Date.Now
                ' if LastWebsiteStatusUnknown > 1 day ago, send email, set LastWebsiteStatusUnknown session variable = Date.Now


What's the best practice for this?

[Cervisiae Amatorem]

Anyone?

[Xanthir]

I'm not sure what you're actually asking for?

[DaveInsurgent]

I think the technique you're looking for is usually called a 'debounce' - basically, you have something that you want done when something happens, but only once every so often. Then, there's usually a leading or trailing debounce, so for example you might want to prevent double accidental clicks with a leading-edge debounce of 800ms. So the second the first click happens, it triggers the button, but a quick follow up click does nothing.

So you're looking to debounce your alert emails by 1 day. However, most systems for this kind of info would resort to a 'digest' where it aggregates the events and sends them. The kind of code you posted seems like it would drop information.