Closed thomaseyde closed 11 months ago
Sadly I've just gone through this exact same process. Not a great onboarding experience.
@thomaseyde @basecde hear you, we'll look at getting those updated and I'll follow up. Appreciate voicing your concerns so thoughtfully and helpfully 🙏🏽
I've the same problem on 5.2.0.
@rollbar-bborsits can you follow up with status please, seems like the thread is lacking our progress. Thanks @dan-luk-labx
@dan-luk-labx Thanks for the additional info. We'll look into this and try to assist you.
Hey @thomaseyde, You were right. Using the RollbackLoggerConfig
would be best to configure the integration properly. I'm sorry for the confusion, the fix is on its way to be released. As the logger works async, the application might close before the SDK sends the payload Rollbar.
The following example logs synchronously:
RollbarInfrastructure.Instance.Init(new RollbarInfrastructureConfig(TOKEN));
RollbarLocator.RollbarInstance.AsBlockingLogger(TimeSpan.FromSeconds(10)).Info("Rollbar is configured properly.");
This should be more suitable for testing Rollbar.
Let me know if this works for you.
It has been a while since I've heard from you, so I'm closing this issue. Don't hesitate to reopen if you need any more help.
The code examples given during the onboarding process is incorrect.
To Reproduce
RollbackConfig
and the code will not compileRollbackConfig
withRollbackLoggerConfig
, code compiles4.0.3
RollbackLoggerConfig
withRollbackConfig
Expected behavior Code example should match latest NuGet package version. No compilation errors. Latest version should send message to Rollbar.
Rollbar Client - Rollbar.NET Hosting Environment (please complete the following information):