Jun 13

Fine-tune JavaScript Monitoring with Proxino Notifiers

When debugging browser exception logs, not all information is useful information. Proxino’s notifier and whitelist system gives you control over exactly what JavaScript exceptions will appear on your dashboard, and when Proxino will tell you about them.

Now let’s have a look at the interface:

Here we create a notifier to tell us about Stripe exceptions (potential use case: loading their JavaScript to do payment processing). We set the url to “stripe.com,” which restricts our matching exception set to that domain, and we leave match blank to include every such exception (you use match to set a restriction on the exception body, for instance: “TypeError”). Finally we set trigger to 5, which tells Proxino to email us when exactly 5 errors of this type have occurred.

Between the trigger, match, and url parameters, you have a great deal of control over email notifications. But what about whitelists?

In this example we create a whitelist item for Olark. It tells Proxino to ignore exceptions which come from olark.com, if those exceptions contain the word “console.”

Whitelists are useful for filtering out classes of exceptions which you don’t care about and have no intention (or means) of fixing. These sort of exceptions tend to be rather common, and there’s no need to have them cluttering up your dashboard.

If you like these features and want to monitor your JavaScript exceptions, perhaps you should give Proxino a try.


Aug 9

Duplicity in the Double Vowel: From Taazr to Proxino

What’s in a company name? There is much debate on the question. At Taazr, we liked to think that the name captured our company’s essence, distilling it into some rich amalgam of mission and function. The metaphors were myriad and easy: taze bugs, fast as an electric spark, powerful as a tsar, and so on. We thought it a Good name. After all, it was unique, meaningful (we supposed), and short. But we were wrong.

We got some inkling of this wrongness once we began speaking to potential customers. One mention of “Taazr,” and the conversation would invariably take an aggravating and pedantic turn:

Joe: So, what are you working on these days?

Me: Taazr. We notify you about javascript exceptions…

Joe: Oh, awesome! I’ll give it a try. Is that t-a-z-e-r?

Me: No, it’s t-a-a-z-r.

Joe: Oh, I see. A funny look. Let me get my computer.

Me: Sure, happy to help you set up.

Joe: Your site isn’t loading.

Me: What! Ah, you typed in t-a-z-z-r.

Joe: How do you spell it again?

And so on. As a name, Taazr may have had its virtues, but memorability was not among them. In retrospect, I think the issue was in the double-a. It refused remembrance, being so unnatural to the English language. But spelling was not the only problem.

Pronunciation also proved ambiguous and confusing. We chose T-AH-ZER as the “correct” form, but this would not stick, even among people who should know better. We have an advisor of sorts, someone we go to for bits of advice. And despite repeated correction, he would say T-AY-ZER. He was not the only one, as many of our customers did likewise.

Given all this, our obstinacy has recently and finally met its limits. We’ve decided to change the name to Proxino. This new name is both pronounceable and meaningful. We like it. And hopefully, spelling will be less of an issue.