Features - For developers
Answer the questions below and we'll be able to tell you which features you will benefit most from.No thanks, just show me all features.
ResultAnswer one or more questions.
Here are some basic questions that OneTrueError always answer:
- Have this exception happened before?
- What did the system look like when this exception happened (memory usage, number of threads etc)?
- What OS and version did the user run?
- In what context was the application when the exception happened (WCF, ASP.NET, WinForms/WPF)
What OneTrueError does better than log files:
- Notifies you when a new exception has been thrown.
- Does not make you backtrack a large log file to identify important information.
- Will not nag on you when the same exception is thrown several times.
- Does not loose or divide information just because the log wraps.
- Will notify you on your phone or email when a new exception has been detected.
- OneTrueError doesn't depend on a monitor configuration or fail if the data format changes.
- OneTrueError do not notify you if the same exception is repeated (unless you want it to).
Bug reports by user
If you experience an error in an application, how often do you call or email the company behind the software? If you get an error dialog, how often do you press "Submit"? No one will contact you in any case, right?
Being dependent on user reports means that you will only get a partial picture about how common an error is and how often it happen. OneTrueError removes the user dependency. Every time the exception occur we detect it and analyze it.
Support departments are great. They might however not be able to tell whether a problem is because of the user doing something wrong, or if it's an actual bug. OneTrueError tells you the facts just as they are. No need to be dependent on a user that *might* submit a bug report or on a support department that *might* pass it on.
Locally installed applications make it really hard to understand why an exception was thrown, as there is really no information available. Even if there are log files, you need to gain access to the user computer.
OneTrueError uploads all error reports to the server, no matter how many installations you have. Our library can even detect and use corporate firewalls if necessary. Thus, compared to log files you always get the information you need, no matter where it was originally located.
Reproducing errors is FUN
.. since OnTrueError gives you all the information you need to be able to reproduce it.
- For ASP.NET you get context information like HTTP Request, Query string parameters, session data
- For MVC/WebApi you also get controller information, chosen route etc.
- For WCF you get the selected service, WCF message information etc.
- In WinForms/WPF we can even deliver screen-shots of all open forms when the exception was detected.
With critical applications you need to correct errors quickly, right? OneTrueError can notify you on your phone or by email seconds after an exception was detected. And with our rich context information, you can quickly understand why the exception was thrown.