Just so that you can change info, in case you move, change your credit card info, etc1 vote
The Errorception console has been extremely slow in the past few days and it is offline now. Please do something about this, as it renders the service unusable.1 vote
Attach a TZ to a project, so, when I run a report I can select dates that are valid in my TZ.1 vote
On December 19, 2017 I clicked on unsubscribe, 500 error appeared, but it appeared on the payment page that I had been unsubscribed and was at a free rate. In the same dates, I removed your code from the project and stopped using it.
Everything is exactly as it is today. I just saw that all this time you continued to withdraw money from me :-(
I'm sure you can check all this.
Could you cancel my subscription and return money from January until today back?1 vote
If I could point pingdom or nagios to a url that denotes whether I have a variance in new/existing error counts, I'd have push notification of errors and would be able to react in an hour instead of a day.1 vote
We use Errorception in a SaaS. It would be great if we'd have a way to set an identifier for a logged in user. (similar to how Mixpanel lets you identify the logged in user.)
This would give us two major benefits:
- We'll have better context to debug -- not every URL tells us which user had the error.
- We'll be able to proactively approach the user and tell them we know of the error - before the user ever contacts support (if they do that at all).1 voteAdminRakesh Pai (Founder, Errorception) responded
Thanks for the suggestion.
There’s some limited functionality available with https://errorception.com/docs/meta and this is displayed in the error report, but not much else. I’ll see how I can improve this.
We have many errors that occur once or a few times, would like to be able to filter these errors.1 vote
Some JS errors out there commonly happen for common and not-so-common reasons. For example, jQuery sometimes doesn't load, and page breaks with "$ is not defined" etc. What would be nice is that you provide a discussion forum around any error, so that I can read it up to know its possible causes.
That discussion can be public. All errorception users can comment (e.g. how I solved this one) This might turn into a good "why that JS error?" resource.1 vote
A frequency graph for each error that occurred1 vote
- Don't see your idea?