This method should be called as early as possible in the course of using the app. The best place to do it is inside the OnAfterRenderAsync method of the main layout page. However, it will also be called automatically before sending any exceptions, just in case.

Recording an error

To send an exception to Raygun call to raygunClient.RecordExceptionAsync(...)

This method accepts the following arguments:

• ex: The Exception to send back to Raygun.
• userDetails: Optional. Attach user details to exception, takes priority over IRaygunUserProvider.
• tags: Optional. User-specified tags that should be applied to the error.
• userCustomData: Optional. Any custom data that you like sent with the report to assist with troubleshooting.
• cancellationToken: Optional. A CancellationToken to allow you to cancel the current request, if necessary.

Recording a breadcrumb

Records a Breadcrumb to help you track what was going on in your application before an error occurred.

Call to raygunClient.RecordBreadcrumb(...);

This method accepts the following arguments:

• message: The message you want to record for this Breadcrumb.
• type: The BreadcrumbType for the message. Defaults to BreadcrumbType.Manual.
• category: A custom value used to arbitrarily group this Breadcrumb.
• customData: Any custom data you want to record about application state when the Breadcrumb was recorded.

Stack traces and portable debug data

Raygun for Blazor attaches both stack traces and the necessary info for portable debug data automatically.

Blazor stack traces

Exceptions originating within the Blazor environment should contain a stack trace attached. For details, check the "Raw Data" tab on the Raygun error report. The stack trace is contained inside error.stackTrace property.

For example:

This also works for exceptions originating in Blazor WebAssembly applications. For example, this exception captured on WebAssembly:

JavaScript stack traces

Exceptions happening in the JavaScript side of a Blazor application should contain a stack trace referring to the JavaScript code that caused the error.

For example:

Portable debug data (PDB)

Raygun for Blazor supports debugging reports using PDB files when running on Blazor Server and MAUI applications. The necessary image information will be attached automatically to error reports.

The debug data can be found in the error.images property:

You can learn more about Portable PDB Support on Raygun's .Net Framework documentation.

Environment details

Raygun for Blazor captures environment details differently depending on the platform where the error originated.

The availability of each environment detail properties depend on the platform itself, so some of them may not be always available.

For more information, you can check the EnvironmentDetails.cs file.

Browser environment details

When the application is running on a browser, for example when using Blazor WebAssembly, or when running MAUI Blazor Hybrid applications on mobile, the attached environment details are obtained from the browser layer on the client side.

For example:

Server environment details

When the application is running on a server machine, for example when using Blazor Server, or when running MAUI Blazor Hybrid applications on desktop, the attached environment details are obtained from the operating system of the running platform.

For example:

The client side environment details from the browser, if available, will be also attached as part of the User Custom Data under BrowserEnvironment:

Attaching user details

Raygun for Blazor provides two ways to attach user details to error reports:

1. Provide UserDetails in the RecordExceptionAsync method call.
2. Implement a IRaygunUserProvider.

User details class

The following properties can be provided as user details:

• UserId: Unique identifier for the user is the user identifier.
• IsAnonymous: Flag indicating if the user is anonymous or not.
• Email: User's email address.
• FullName: User's full name.
• FirstName: User's first name (what you would use if you were emailing them - "Hi {{firstName}}, ...")
• DeviceId: Device unique identifier. Useful if sending errors from a mobile device.

All properties are strings except isAnonymous, which is a boolean. As well, they are all optional.

User details in RecordExceptionAsync

The simplest way to attach user details to an error report, is to do it when calling to RecordExceptionAsync.

Pass a UserDetails object to the method call:

Implementing IRaygunUserProvider

Providing an instance of IRaygunUserProvider to the Raygun Blazor client allows you to attach user details also to errors reported automatically, for example, captured unhandled exceptions or exceptions from the JavaScript layer.

Implement an IRaygunUserProvider, for example:

And inject it into the Raygun Blazor client:

For a complete example on how to implement a IRaygunUserProvider with the AuthenticationStateProvider check the example project file src/Raygun.Samples.Blazor.WebAssembly/Program.cs.

Background processing

You can enable a throttled background message processor for the Raygun provider by setting the UseBackgroundQueue to true.

Background processing is disabled by default.

You can adjust the following background processor settings as well:

• BackgroundMessageQueueMax to set the maximum queue size.
• BackgroundMessageWorkerCount to set the maximum number of workers.
• BackgroundMessageWorkerBreakpoint to set a threshold on when a new worker will be added.

Check the RaygunSettings class for a complete documentation of these parameters and their default values.

Modifying or cancelling requests

The RaygunClient exposes the OnBeforeSend event listener, which allows you to modify or cancel error message requests before they are sent to Raygun.

To cancel sending a request, set the Cancel property to false inside your listener:

As well, you can modify the Request payload:

Offline storage configuration

Raygun for Blazor supports storing error reports when they can't be sent, for example, if the communication between the server and Raygun is interrupted.

You can enable offline storage support by setting the UseOfflineStore to true.

Offline storage is disabled by default.

You can adjust the following offline store settings as well:

• DirectoryName to set the folder to store crash reports, relative to the system local application data.
• MaxOfflineFiles to set the maximum number of stored reports, defaults to 50.

For example:

With this configuration, Raygun will store a maximum of 100 Raygun offline reports under C:\Users\<USER>\AppData\Local\MyApp.

Internal logger

Raygun for Blazor uses an internal logger to help facilitate the integration of the package. The default log level is "Warning". To completely disable the internal logger, set the "LogLevel" setting to "None".

For example:

For all configuration values, check the RaygunLogLevel enum under src/Raygun.Blazor/Logging/RaygunLogLevel.cs.