Adding info about debug.logerrors

Details on the 5 classes of Errors backtrace captures. Details up to Best Practices.

Author: jasoncdavis0

README.md

@@ -1,7 +1,7 @@
 
 # Backtrace Unity support
 
-[Backtrace](http://backtrace.io/)'s integration with Unity allows developers to capture and report handled and unhandled Unity exceptions and crashes to their Backtrace instance, instantly offering the ability to prioritize and debug software errors.
+[Backtrace](http://backtrace.io/)'s integration with Unity allows developers to capture and report log errors, handled and unhandled Unity exceptions, and native crashes to their Backtrace instance, instantly offering the ability to prioritize and debug software errors.
 
 [![openupm](https://img.shields.io/npm/v/io.backtrace.unity?label=openupm&registry_uri=https://package.openupm.com)](https://openupm.com/packages/io.backtrace.unity/)
 
@@ -37,8 +37,8 @@ catch(Exception exception){
 
 # Feature Summary <a name="features-summary"></a>
 
-- Lightweight library that quickly submits handled and unhandled exceptions and crashes to Backtrace 
-  - Supports wide range of Unity versions (2017.4+) and deployments (iOS, Android, Windows, Mac, WebGL, PS4, Xbox, Switch, Stadia)
+- Lightweight library that quickly submits log errors, handled and unhandled exceptions, and native crashes to Backtrace 
+  - Supports wide range of Unity versions (2017.4+) and deployments (iOS, Android, Windows, Mac, WebGL, PS4/5 Xbox One/S/X, Nintendo Switch, Stadia)
   - Install via Universal Package Manager
 - Collect detailed context 
   - Callstacks, including function names and line numbers where possible
@@ -48,8 +48,9 @@ catch(Exception exception){
   - Android NDK Crashes; iOS Native Crashes, Windows Native Crashes
 - Client-side features
   - Deduplication options and custom client side fingerprinting
+  - Client side filters and sampling controls
   - Offline crash capture/storage for future collection
-  - Customizable event handlers and base classes, Client side filters
+  - Customizable event handlers and base classes
   - Performance statistics collection option for timing observability
 - Unity IDE integration to configure Backtrace behaviors in your game.
 
@@ -66,7 +67,7 @@ PC - Windows, Mac
 Web - WebGL
 Game Consoles - PlayStation4, Xbox One, Nintendo Switch
 There are some differences in capabilities that backtrace-unity provides based on the platform. Major capabilities are summarized as follows:
-* All Platforms - Unhandled Exceptions, Handled Exceptions, Custom Indexable Metadata, File Attachments*, Last N Log Lines, Automatic attachment of Screenshots, Client Side Deduplication Rules*, Client Side Submission Filtering, Client Side Submission Limits, Performance Diagnostics, Offline Database*(Except Nintendo Switch)
+* All Platforms - Errors, Unhandled Exceptions, Handled Exceptions, Custom Indexable Metadata, File Attachments*, Last N Log Lines, Automatic attachment of Screenshots, Client Side Deduplication Rules*, Client Side Submission Filtering, Client Side Submission Limits, Performance Diagnostics, Offline Database*(Except Nintendo Switch)
 * Android -Identified by attribute uname.sysname = Android; ANRs (Hangs), Native Process and Memory Information, Java Exception Handler (Plugins, Exported Game in Android Studio), NDK crashes.
 * iOS - Identified by attribute uname.sysname = IOS; Native Engine and Plugin Crashes.
 * WebGL - Identified by attribute uname.sysname = WebGL. The attribute device.model is currently used to share the browser information. Note that stacktraces for WebGL errors are only available if you choose to enable them in the Publishing Settings / Enable Exceptions drop down. More details in https://docs.unity3d.com/Manual/webgl-building.html 
@@ -125,7 +126,16 @@ If you need to use more advanced configuration, `Initialize` method accepts a `B
 
 ## Plugin best practices
 
-Plugin allows you to define maximum depth of game objects. By default its disabled (Game object depth is equal to -1). If you will use 0 as maximum depth of game object we will use default game object limit - 16. If you would like to specify game object depth size to n, please insert n in Backtrace configuration text box. If you require game obejct depth to be above 30, please contact support.
+The plugin will report on 5 'classes' or errors:
+1) Log Errors - Programmers use Debug.LogError(https://docs.unity3d.com/ScriptReference/Debug.LogError.html), a variant of Debug.Log, to log error messages to the console.
+2) Unhandled Exceptions - Unhandled Exceptions are exceptions in a game that occur outside of an explicit try / catch statement. 
+3) Handled Exceptions - Exceptions that are explicitly caught and handled.
+4) Crashes - An end to the game play experience. The game crashes or restarts. 
+5) Hangs - A game is non responsive. Some platforms will tell the user “This app has stopped responding
+
+The plugin provide 2 controls for manaing what the client will report. [SkipReports](#filtering_a_report) allows you to tell the client to only report on specific classes of these errors, and and LogSampling will allow you to tell the client to sample the Debug Log errors so programmers don't 'shoot themselves in the foot' by releasing the plugin to a many users and report on hundreds of low priority and recoerable errors that they may not be intending to capture. 
+
+The plugin allows you to collect game objects if you like by specifying a depth of hierarchy to inspect to for game objects. By default its disabled (Game object depth is equal to -1). If you will use 0 as maximum depth of game object we will use default game object limit - 16. If you would like to specify game object depth size to n, please insert n in Backtrace configuration text box. If you require game obejct depth to be above 30, please contact support.
 
 ## Backtrace Client and Offline Database Settings