The Bugsnag Notifier for .NET gives you instant notification of exceptions thrown from your ASP.NET MVC, WPF, WebAPI or other .NET applications. Any uncaught exceptions will trigger a notification to be sent to your Bugsnag project.
Bugsnag captures errors in real-time from your websites and mobile applications, helping you to understand and resolve them as fast as possible. Create a free account to start capturing errors from your applications.
- Install the Bugsnag package from Nuget.
- Download the latest Bugsnag.dll and reference it in your project
Bugsnag for .NET depends only on the JSON.net library and needs to be referenced, the nuget package can be found here.
Configure the Bugsnag integration inside your Web.config file
<configuration>
<configSections>
<section name="bugsnagConfig" type="Bugsnag.ConfigurationStorage.ConfigSection, Bugsnag" />
</configSections>
<bugsnagConfig apiKey="your-api-key-goes-here" />
</configuration>Note: Please see [Configuration](#Additional Configuration) for details on other configuration you can set.
Import the Bugnsnag clients namespace into your application
using Bugsnag.Clients;Inside the RegisterGlobalFilters function add the WebMVCClient error handler. Normally, this can be done in the App_Start > FilterConfig.cs file.
filters.Add(WebMVCClient.ErrorHandler());Thats it...you will be reporting on uncaught exceptions by default!
Configure the Bugsnag integration inside your Web.config file
<configuration>
<configSections>
<section name="bugsnagConfig" type="Bugsnag.ConfigurationStorage.ConfigSection, Bugsnag" />
</configSections>
<bugsnagConfig apiKey="your-api-key-goes-here" />
</configuration>Note: Please see [Configuration](#Additional Configuration) for details on other configuration you can set.
Import the Bugnsnag clients namespace into your application
using Bugsnag.Clients;Inside the RegisterWebApiFilters function add the WebAPIClient error handler. Normally, this can be done in the App_Start > FilterConfig.cs file.
filters.Add(WebAPIClient.ErrorHandler());Thats it...you will be reporting on uncaught exceptions by default!
Configure the Bugsnag integration inside your App.config file
<configuration>
<configSections>
<section name="bugsnagConfig" type="Bugsnag.ConfigurationStorage.ConfigSection, Bugsnag" />
</configSections>
<bugsnagConfig apiKey="your-api-key-goes-here" />
</configuration>Note: Please see [Configuration](#Additional Configuration) for details on other configuration you can set.
Import the Bugnsnag clients namespace into your application
using Bugsnag.Clients;Inside the OnStartup function call the WPFClient.Start() method. Normally, this can be done in the App.xaml.cs file.
WPFClient.Start();Thats it...you will be reporting on uncaught exceptions by default!
Bugsnag will also catch exceptions in standard .NET applications. To do so you can construct a Bugsnag.Clients.BaseClient (there is a Singleton convenience wrapper in Bugsnag.Clients.SingletonClient if you would like to use it.)
Firstly import the Bugsang.Clients namespace.
using Bugsnag.Clients;The client needs to be created using your API key.
var bugsnag = new BaseClient("your-api-key-goes-here");If you would like to send non-fatal exceptions to Bugsnag, you can pass any object that inherits from Exception to the Notify method:
bugsnag.Notify(new ArgumentException("Non-fatal"));Note: These methods are also available on any other static clients like the WebMVCClient.
You can also send additional meta-data to help debug with your exception:
var metadata = new Metadata();
metadata.AddToTab("Resources", "Datastore Entries", myDataStore.Count());
metadata.AddToTab("Resources", "Threads Running", threads.Count());
metadata.AddToTab("Resources", "Throttling Enabled", false);
bugsnag.Notify(new ArgumentException("Non-fatal"), metadata);You can set the severity of an error in Bugsnag by including the severity option when notifying bugsnag of the error,
bugsnag.Notify(new ArgumentException("Non-fatal"), Severity.Info)Valid severities are Severity.Error, Severity.Warning and Severity.Info.
Severity is displayed in the dashboard and can be used to filter the error list.
By default all crashes (or unhandled exceptions) are set to Severity.Error and all bugsnag.Notify() calls default to Severity.Warning.
The client can be configured with specific application settings which can be used to determine when and what information to send. Application settings can be set at any time, but are normally set immediately after the client is created.
Used to attach the version number of the application which generated the error. If the application version is set and an error is resolved in the dashboard the error will not be unresolved until a crash is seen in a newer version of the app.
bugsnag.Config.AppVersion = "5.0.1";Represents the current release stage for the application. This needs to be set manually.
bugsnag.Config.ReleaseStage = "staging";By default, the client will report on all errors regardless of the release stage. However, you can filter out errors from certain stages. To specify which stages you want to notify on, use the following method.
bugsnag.Config.SetNotifyReleaseStages("development","production");The client can be configured to provide additional information based on the current error or process that is running at the time. These settings can be set any time.
The concept of "contexts" is used to help display what was happening in your app at the time of the error
bugsnag.Config.Context = "DataAccess";The client can be configured to send the users ID, email and name with every notification. The user ID should be set to something unique to the user e.g. a generated GUID.
bugsnag.Config.SetUser("d7b4aadd", "anth.michaels@mycompany.com", "Anthony Michaels");Metadata can be set directly on the client. This metadata will be sent with every error report (in addition to any metadata added to the report itself).
bugsnag.Config.Metadata.AddToTab("Company", "Department", "Human Resources");
bugsnag.Config.Metadata.AddToTab("Company", "Location", "New York");The client can be configured to restrict or modify the notifications that are sent to Bugsnag. These settings will allow you suppress specific errors, remove unnecessary information and modify the notification before its sent.
When an exception stack trace is recorded, the file associated with each frame will be recorded, if its available. This will be the complete file path, which can lead to bloated frame entries. The paths will also reflect where the application was complied. The client can be configure to remove common file path prefixes.
bugsnag.Config.SetFilePrefix(@"C:\Projects\Production\MyApp\",
@"C:\Projects\Development\MyApp\",
@"H:\MyApp\");Note: This can help significantly when grouping similar errors.
Bugsnag will highlight stack trace frames if they are detected as being In Project. The client can be configured with project namespaces. If a stack trace frame method call originates from a class that belongs to one of these project namespaces, they will be highlighted.
bugsnag.Config.SetProjectNamespaces("MyCompany.MyApp","MyCompany.MyLibrary");Debugging information is used to provide file paths for stack frames. Normally, this information is only available for locally built projects. Therefore, in most cases, stack frames that have file information relate to calls made within the users code. We use this fact to automatically mark these frames as In Project by default. This is in addition to any project namespaces that have been manually added. This behavior can be disabled.
// Disable marking frames with file names as In Project
bugsnag.Config.AutoDetectInProject = false;If no project namespaces have been configured and auto detect has been disabled, all stack frames will be highlighted.
The client can be configured to ignore specific types of exceptions. Any errors with these types of exceptions will not be sent to Bugsnag.
bugsnag.Config.SetIgnoreClasses("ArgumentNullException", "MyConfigException");Custom call back functions can be configured to run just before an error event is sent. These callbacks have full access to the error and can modify it before its sent. They also have the opportunity to prevent the error from being sent all together. A callback should take an error Event object as a parameter and return a boolean indicating if the event should be notified (Func<Event,bool>);
Note that these callbacks will not be called if the exception class is an class being ignored via SetIgnoreClasses() or the current release stage is one that has been configured not to be notified on via SetNotifyReleaseStages().
bugsnag.Config.BeforeNotify(error =>
{
// Sets the groupingHash option
error.setGroupingHash("My Group");
// Elevate all warnings as errors
if (error.Severity == Severity.Warning)
{
error.Severity = Severity.Error;
error.addToTab("Reporting", "Elevated", true);
}
// Ignore all exceptions marked as minor
var isMinor = error.Exception.Message.Contains("[MINOR]");
return !isMinor;
});Data associated with notifications are sent via the Metadata object attached to the error. Sensitive information can be filtered before its sent to Bugsnag by setting filters. Any tab entries that have keys matching these filters will have they value replaced with the text [FILTERED]
bugsnag.Config.SetFilters("Password", "Credit Card Number");All notifications are send to the Endpoint URL. By default, this is set to http://notify.bugsnag.com, however this can be overridden.
bugsnag.Config.Endpoint = "http://myserver.bugsnag.com";When an exception occurs, the details of the exception is collated and recorded into an error Event object. This object stores all the information about the exception that will be sent to Bugsnag. By setting this object properties, you can send additional information or modify an existing object before its sent.
All event objects can be modified just before they are sent to Bugsnag using the [Before Notify Callback](#Before Notify Callback)
The available properties available
The exception the event is representing. This needs to be provided when creating an error event and can not be modified.
Exception exp = error.Exception;If an exception occurs that has resulted in the application crashing out (runtime ended), this flag will be true.
bool hasCrashed = error.IsRuntimeEnding;Sets the grouping hash used by Bugsnag.com to manually override the default grouping technique. This option is not recommended, and should only be manually set with care.
Any errors that are sent to Bugsnag, that have the same grouping hash will be grouped as one.
error.GroupingHash = "d41d8cd98f00b204e9800998ecf8427e";The severity can be set directly on the event. Valid severities are Severity.Error, Severity.Warning and Severity.Info.
error.Severity = Severity.Info;Additional information that you want to include with an error event is done using the Metadata property. The metadata represents tabs and tab entries that can be visualized from the Bugsnag dashboard. Each tab entry consists of a entry key and an entry value. The entry key is string, but the entry value can be any object that can serialized in JSON e.g. dictionaries, arrays, complex objects etc.
Each event object will start with a blank metadata object ready to be added to. However you can create your own metadata object and set the property directly. The metadata object has methods to help you add your own data.
This is the main way to add data to a Metadata object. Specify the tab, tab entry key and tab entry value you want to add. If the entry key already exists in the tab your trying to add to, the value will be overwritten with the new value. If no tab is specified, the data will be added to the "Custom Data" tab.
// Adds company details under the "Company Details" tab
error.Metadata.AddToTab("Company Details", "Name", "My Company");
error.Metadata.AddToTab("Company Details", "Phone", "01123456789012");
error.Metadata.AddToTab("Company Details", "Email", "admin@mycompany.com");
// Adds a list of developers under a single entry
var devs = new string[]{"Bob Adams", "James Richards", "Lucy Patrick"};
error.Metadata.AddToTab("Team", "Developers", devs);
// Adds some app data to the custom data tab
error.Metadata.AddToTab("Full Test Suite", true);Removes a tab that exists in the metadata.
// Removes the Dev Only tab
error.Metadata.RemoveTab("Dev Only");Removes a tab entry that exists in the metadata.
// Removes the unit test result entry
error.Metadata.RemoveTabEntry("Build Results", "Test Results");