Add BugSnag to your ASP.NET MVC applications to automatically capture and report exceptions in production.
New to BugSnag? Create an account
Looking for performance monitoring? See our web app integration
Bugsnag.AspNet.Mvc package from NuGet.Bugsnag.dll, Bugsnag.AspNet.dll, Bugsnag.AspNet.Mvc.dll and Bugsnag.ConfigurationSection.dll in your project.The latest available version of Bugsnag.AspNet.Mvc is v3.1.0.
Configure the BugSnag integration inside your Web.config file
<configuration>
<configSections>
<section name="bugsnag"
type="Bugsnag.ConfigurationSection.Configuration, Bugsnag.ConfigurationSection" />
</configSections>
<bugsnag apiKey="your-api-key-goes-here" />
</configuration>
You can find your API key in Project Settings from your BugSnag dashboard.
If you are using .NET Framework 3.5 then you also need to add the BugSnag Http module to your Web.config file in the following locations. This is done automatically if you are targeting .NET Framework 4 or greater.
<configuration>
<system.web>
<httpModules>
<add name="Bugsnag"
type="Bugsnag.AspNet.HttpModule, Bugsnag.AspNet" />
</httpModules>
</system.web>
<system.webServer>
<modules>
<remove name="Bugsnag" />
<add name="Bugsnag"
type="Bugsnag.AspNet.HttpModule, Bugsnag.AspNet" />
</modules>
</system.webServer>
</configuration>
If you are using .NET Framework 3.5 then you also need to add the Bugsnag.AspNet.Mvc.HandleErrorAttribute error filter. This is done automatically is you are targeting .NET Framework 4 or greater.
System.Web.Mvc.GlobalFilters.Filters
.Add(new Bugsnag.AspNet.Mvc.HandleErrorAttribute());
If you’d like to configure BugSnag further, check out the configuration options reference.
After completing installation and basic configuration, unhandled exceptions will be automatically reported to your BugSnag dashboard.
If you would like to send non-fatal exceptions to BugSnag, you can pass any object that inherits from System.Exception to the Notify method
try
{
throw new System.Exception("Error!");
}
catch (System.Exception ex)
{
Bugsnag.AspNet.Client.Current
.Notify(ex);
}
As well as a full stacktrace for every exception, BugSnag will automatically capture the following diagnostic data:
It can often be helpful to attach application-specific diagnostic data to exception reports. This can be accomplished as follows:
using System.Collections.Generic;
// ...
try
{
throw new System.Exception("Error!");
}
catch (System.Exception ex)
{
Bugsnag.AspNet.Client.Current.Notify(ex, (report) => {
report.Event.Metadata.Add("account", new Dictionary<string, string> {
{ "company", "Acme Co." },
{ "id", "4425" },
});
});
}
In order to correlate errors with customer reports, or to see a list of users who experienced each error, it is helpful to capture and display user information on your BugSnag dashboard.
You can set this information using a callback as follows:
Bugsnag.AspNet.Client.Current.BeforeNotify(report =>
{
report.Event.User = new Bugsnag.Payload.User
{
Id = "45556",
Name = "Bob Smith",
Email = "bob@example.com"
};
});
For more information, see Customizing error reports.
In order to understand what happened in your application before each error, it can be helpful to leave short log statements that we call breadcrumbs. The last 25 breadcrumbs are attached to an error report to help diagnose what events lead to the error. Captured breadcrumbs are shown on your BugSnag dashboard as a part of the error report.
You can leave manual breadcrumbs via the Breadcrumbs property on the client object.
Bugsnag.AspNet.Client.Current.Breadcrumbs
.Leave("Something happened!");
You can optionally attach a type and metadata to a breadcrumb for additional context into the state of the application when the breadcrumb was captured.
Bugsnag.AspNet.Client.Current.Breadcrumbs
.Leave("Something happened!", Bugsnag.BreadcrumbType.Navigation, null);
With additional diagnostic metadata:
var metadata = new Dictionary<string, string> { { "foo", "bar" } }
Bugsnag.AspNet.Client.Current.Breadcrumbs
.Leave("Something happened!", Bugsnag.BreadcrumbType.State, metadata);
BugSnag can track the number of “sessions” that happen in your application. This enables BugSnag to provide and compare stability scores between releases to help you understand the quality of your releases.
This functionality is disabled by default and can be controlled through the AutoCaptureSessions configuration value:
configuration.AutoCaptureSessions = true;
Using this option, BugSnag will report a session each time a request is received.
If you want control over what is deemed a session, rather than using the AutoCaptureSessions option, you can call the following when appropriate for your application.
Bugsnag.AspNet.Client.Current.SessionTracking.CreateSession();
Stacktraces from .NET platforms will be automatically populated with line numbers and file names for dlls that the runtime can find symbols for. This usually means that you should deploy the .pdb files alongside your dlls so that BugSnag is able to retrieve this information.
bugsnag-dotnet, the library powering this integration, on GitHub