Didn't get one of our notification emails today?

Dear Raygun, We get a lot of emails from your service - one of the main ways we use it is to monitor the level of throttling we're experiencing via our DB provider so we can reprovision our tables if needed.

That said, it's obvious why the the most critical email we get is this one: "Error: The level of configured provisioned throughput for the table was exceeded."

However, for some reason, we didn't receive that email today. We got a few others, but not this one - the most critical one of all.

This is a business critical application for us, so we're quite concerned. The chance that we wouldn't get one of these notifications significantly degrades the value of your service to us :(.

Can you take a look and/or explain why we wouldn't receive a certain email notification?

Thanks in advance.

---

Hi Tory,

Raygun generally only emails you about new errors, resolved errors that have reoccured and errors that are occurring lots of time per minute. Do you resolve the exception each time it occurs? If not, you may not get notified about it if it occurs again.

If you are resolving the exceptions something else isn't quite right - I'll dig in and have a look if so!

Hope this clears things up

Regards,

Daniel

---

Hi Daniel - This isn't an error that we "resolve" in the way you're referencing, unfortunately. It's what I'd call a "managed risk", if you will.

As for actually marking it as resolved in Raygun, we've never needed to do that. It's possible that it's because when it occurs, it occurs at a frequency that's above the threshold to trigger another email?

Also, I'm not sure that marking it as "resolved" is the right action for us in this case, since we're not "resolving" it per se. We're making adjustments in our settings that should fix it, but it's entirely possible that we'll receive another spike of traffic and it'll reoccur.

Would appreciate your guidance here. Perhaps we're not understanding your concept of "resolved" properly?

---

Hey Tory,

I'd say that you're correct - enough errors were thrown previously to trigger another email. And that this time there weren't enough exceptions coming through.

Resolved is generally when you've fixed the error, but I understand the issue in doing so here. You could possibly mark it as resolved each time you make changes at your end, but that's still not quite the 'resolved' concept.

We have a flag we can set on your account that will send through an email anytime on an error sighting outside of a 'still occurring' window. Would you like me to turn this on?

Cheers,

Daniel

---

Thanks for the info Daniel.

Regarding the setting you suggested above - the one that allows us to receive an email if the error is seen outside of a configured window - I actually believe we already receive that one. The window is currently 30 minutes. Can that be configured on a per-error basis?

Here's why I ask: for this error, we need all the notifications we can get. Any instance of this requires immediate action on our part.

I'm not thrilled at the idea that Raygun might "decide" not to send us notifications if there's some unknown/non configurable threshold that has not been surpassed - I'd really like to understand that behavior better as well, as well if there's anything we can do to manage it.

Thanks again.

---