We'd love to integrate Errorception support into Meldium so that companies can quickly add their new employees and contractors to their Errorception accounts. Can you expose your list / invite / remove user methods over your API? Thanks!

When working with a group of devs (or even one dev dealing with a lot of errors), it would be useful to be able to annotate specific errors--something as simple as a comments box would do, probably. It would be nice to have a place where we could capture information such as what Jira ticket a certain error corresponds to, or whether somebody has started working on resolving the error's cause already.

Pivotal Tracker Integration so that we can more easily prioritize and track bugs alongside our features and other server side bugs.

Airbrake does this pretty well.

Thanks,
Jon

Hello,
It seems like if I have errors I want to fix them right away. Getting a daily digest at the end of the day is far from ideal. There should be an option to receive error emails as they come in.

One error causes different messages in different browsers. It would be very useful to group those errors.

Maybe errorception could even use the grouping to learn which errors are essentially the same.

I have a Chrome error "Uncaught Error: Attempting to use a disconnected port object" filling up 80% of my daily quota.

It seems to come from a 3-rd party extention. Is it possible to ignore it, so I don't have to pay for it?

currently i have to select each checkbox individually before closing/ignoring. it's standard to have a "select all" or "deselect all" in UI's like this. (see gmail as an example)

Just so that you can change info, in case you move, change your credit card info, etc

Being able to enable errorception on a site by checking a box in cloud flare would be super handy, and save a lot of time. It's also great exposure, I've signed up for several services I've found on their App page.

I don't like that emails about billing come from 2checkout.com and I am redirected there to change payment settings. I would feel more secure if this happened on errorception.com

Would be convenient to wildcard subomdains. e.g. *.mydomain.com

This would be helpful for 'important' pages such as signup, or key app pages. If a new browser comes out and breaks a certain page, it may take a bit of time before we check error-ception.

Sometimes there are edge cases in code that don't trigger an exception, but you'd like to log as a warning with console.warn. It'd be nice to be able to see this in errorception.

e.g. after a deploy, i want to start fresh to make sure i see all errors coming up from the new release.

also i realy hate an unorganized list :P

I have French and English users, primarily. the same error in these different languages is reported as two different errors.

I'm seeing quite a few errors logged from chrome:// URLs, obviously from a user's browser extension and not something I actually control. I'd like to only log http:// and https:// URLs. (If anyone *wants* to see the chrome:// errors I suppose this should be an option, though I have a hard time thinking of a use case where someone would want that.)

We have a lot of errors that occur sporadically / due to ad server code. It would be interesting and useful to see how many times / the ratio of times the page loaded with said error.

http://yourdomain.com/somepage (71% of page loads)