Log4Net integration: SentrySdk.Init() don't work about sentry-dotnet HOT 5 CLOSED

@dglasl It seems the problem is the DSN.

You need to replace that string with your actual DSN. You get one when you create a project with Sentry.

One way to do go is to sign up with sentry.io. There you get your DSN (which is a URI like https://[email protected]/more-stuff.

Add that to your sample instead of the string DSN.
After that, when a crash happens, you'll see the event in your Sentry project.

Like this example (which has my DSN):

from sentry-dotnet.

Hello and thank you very much for your answer.
I forgot to mention that in the place of DSN there is of course a real one and I only censored it.
Also, if I register the DSN in the .config file, the error logging works and I see the error in Sentry.

from sentry-dotnet.

@dglasl Sorry I misunderstood the issue.

This was indeed a bug.

The Appender, when not Initializing the SDK by itself, decided not to use the Hub at all, even if that was already enabled. Then not sending events at all.

I've pushed a fix which simply checks if the current Hub is already enabled. If it is, it'll carry on using that instead of trying to initialize a new one.

If you are currently blocked by this, please note the Release can also be set via the attributes AssemblyInformationalVersion or AssemblyVersion (which can also be set via csproj or also via environment variable SENTRY_RELESE in the session/process or machine running the code.

One last note, please make sure to hold on to the IDisposable returned by SentrySdk.Init and dispose it at the end of the application execution. This makes sure any queued up event gets flushed out to Sentry before the app terminates.

If the SDK is initialized via a Program.cs Main method, this can be done like:

using (SentrySdk.Init())
{
  // app code ..
}

from sentry-dotnet.

Thank you very much the quick answer and the fix!
I really appreciate it.

from sentry-dotnet.

@dglasl thank you for using it and reporting.

from sentry-dotnet.