Wasp.io tracks errors generated by your applications, notifies your team, and provides realtime data feeds of errors and activity for all of your websites by sending the details of generated errors to Wasp API..
Error details include full stacktrace, the code surrounding the file and line where the error was generated, information on the browser, operating system, and other information relating to the visitor generating the error.
If the track users option is enabled in the Wasp settings page, ID, user name, and email of currently logged in users generating the error will also be sent to Wasp API..
After activating Wasp from 'Plugins in WordPress, you need to sign up at https wasp io for API Key..
Once you have Wasp.io account, have created project, navigate to the project settings, and your API key will be shown there...
Errors slow down, and can take down your websites, and often the notification you get is from client, or nice enough to let you know Wasp.io overrides the error handling of your WordPress sites, and sends those errors to WaspAPI for grouping, filtering, and in realtime...
Error details are sent to Wasp API for filtering, notification, and management through your account.
Since debugging is already task, Wasp sends as much information as possible including full stacktrace information, information, the code where error was generated, and email, user name, and ID of logged in users ...
If after using Wasp, if you aren't inclined to pay for subscription after the day period expires, you'll still have full access to your Wasp account and any projects you've been added to by owners of other accounts.
Browse the code, check out SVN repository, or subscribe to the development log by RSS...
Read more
Related items:
