ASP.NET Core - be able to use Bugsnag in singleton services and static contexts

[LoremFooBar]

Description

I would like to add Bugsnag to a reverse proxy project (.NET Core 3.1). Since this is not a classic MVC/WebAPI project, there are no controllers, and most of the code runs in a static context. The Bugsnag.AspNet.Core package adds the Bugsnag client as scoped service, which makes it difficult to use in static contexts (from singleton services for example).

Describe the solution you'd like

Be able to register Bugsnag client as singleton service and use IHttpContextAccessor to access request information where needed.

Describe alternatives you've considered

1. Manually setup Bugsnag without the Bugsnag.AspNet.Core package - not great for me because I would like Bugsnag integration to be as easy as possible in all of our projects.
2. Create and publish my own package - this will probably be my temporary solution, eventually I would be happy to contribute my work back to this project.

Update - I created a package where the only change is adding Bugsnag.IClient as a singleton instead of a scoped service, and looks like everything just works.

[johnkiely1]

Hi @Lazyboy1 ,

Thanks for raising this. we will look into this when we can.
For now, it sounds like you have it working as you need it to, so by all means stick with that approach.

[maciej-januchowski]

Another similar use case would be using Bugsnag inside service registered as IHostedService. Since IHostedService is registered as singleton it is also not possible to use scoped Bugsnag inside of it.

[aycron-dev]

Is there any way to Identify the Users Automatically, on one piece of code using:

_bugsnag.BeforeNotify(report =>
{
report.Event.User = new Bugsnag.Payload.User
{
Id = "45556",
Name = "Bob Smith",
Email = "bob@example.com"
};
});

I think that the only way is to make the service Singleton

[yousif-bugsnag]

Hi @aycron-dev, You're correct, there isn't a way to do that currently since the Bugsnag client is scoped to the lifetime of a single request. We're going to look into adding support for registering Bugsnag as a singleton when priorities allow.