mausworks / pidget Goto Github PK

The sentry documentation states the following:

If an empty DSN is passed, you should treat it as valid option which signifies disabling the SDK.

Currently, the library throws for an empty DSN.

The user interface is currently not supported: https://docs.sentry.io/clientdev/interfaces/user/

0.3.0 should support:

• Attaching user data to events
• Automatically attach user data from the HttpContext in the Pidget ASP.NET Middleware.

Pidget.Client -Version 1.0.3

InnerException.InnerException.StackTrace
bei Pidget.Client.VersionNumber.Get()
bei Pidget.Client.SentryClient..cctor()
bei System.Runtime.CompilerServices.ClassConstructorRunner.EnsureClassConstructorRun(StaticClassConstructionContext* pContext) in f:\dd\ndp\fxcore\CoreRT\src\System.Private.CoreLib\src\System\Runtime\CompilerServices\ClassConstructorRunner.cs: Zeile92

One of the missing features from Sentry's list of "expected features".

In 1.0.0 the following should be handled:

• Non-success status codes (e.g. rejections) (#17 adds support)
• Soft failures when the Sentry server fails to respond in a reasonable amount of time (e.g. 3s) (#17)
• Exponential backoff when Sentry fails (don’t continue trying if the server is offline) #26 can be used to handle it.
• Failover to a standard logging module on errors. #26 adds support, but nothing pre-configured.

The project currently does not work with the new DSN format, which omits the private key.

A IndexOutOfBoundsException occurs when calling Dsn.Create(<new-key-format>)

Hi. I'm trying to use your project into my own. It is asp.net core 2.0 app. I have installed the last version from NuGet and tried last from releases. Also tried to create new asp.net core 2.0 project.

Every time I had a startup error:
Unhandled Exception: System.InvalidOperationException: Cannot resolve scoped service 'Pidget.Client.SentryClient' from root provider.

dotnet --info and Startup.cs: https://gist.github.com/offi/2461d0f8e6e10f0c2f9d97c7372312f2

I'm using Pidget on a .NET Core app in Linux. The problem is that I use nginx to proxy the requests to the application.

All my Sentry user tags are therefore ip:localhost.

• A missing feature is the "X-Forwarded-For"-header, to track the user ip.

One of the other missing features from the "expected features" list. Closely related to #12, but more elaborate.

I don't think it's a good idea to have the client manage its own "retry"-logic, as I want the client to simply be the "transfer mechanism" in the project. But retrial should be supported at least in the ASP.NET middleware.

Some objects supports using only arbitrary data such as ExtraData.

Other objects support both arbitrary data and predefined keys. Such as the contexts object and its members.

To support this, dynamic key must be allowed to get set for some objects.

0.3.0 should support:

• Adding arbitrary data to objects where allowed.

The contexts interface is currently not supported: https://docs.sentry.io/clientdev/interfaces/contexts/

0.3.0 should support:

• Attaching context data to an event

This is embarrassing, but … Pidget.AspNet does not currently work with newer versions of AspNetCore MVC … and I don't know since when.

To reproduce

Create a new MVC project and install Pidget.AspNet:

dotnet new mvc --auth None
dotnet add package Pidget.AspNet

Then, follow the instructions from the README in Pidget.AspNet, and set it up.

Then, throw an exception in HomeController / Index(), like so:

    public class HomeController : Controller
    {
        public IActionResult Index()
        {
            throw new Exception("Sorry :(");
            
            return View();
        }

        // ...

The Middleware will throw a NullReferenceException when attempting to extract FrameData, and no error is sent to sentry.

I came along from reddit comments to here and want to use your package in one of my projects.

The problem is that how I will integrate it to .net 4.6.2 project in the best way to filter and having some tags sent to sentry and also in a clever way using breadcrumbs.

At the moment I wrote a console app and can write to sentry using the pidget.client but I want to use Pidget.AspNet and capture my 4.6.2 app errors.

Right now we use nlog.
I figured out also nlogs can be sent to pidget right ?

Thanks.

erkin

Pretty much the same as #21. Useful for handling rate-limiting.

Expected functionality:

• Reject events before sending
• Add data to to the event
• See what event data is going to be sent
• Async support

The easiest way to add full support for #13, is to simply not support it, but instead allow the implementor of the library to handle "after-send" as they see fit.

Expected functionality:

• Inspect the response
• Async support