stayallive / wp-sentry

A (unofficial) WordPress plugin reporting PHP and JavaScript errors to Sentry.
https://wordpress.org/plugins/wp-sentry-integration/
MIT License
305 stars 48 forks source link

PHP failed with Gitlab Integrated lightweight alternative to Sentry #101

Closed EHLOVader closed 2 years ago

EHLOVader commented 2 years ago

This may actually be a question about if this will or can support Gitlab's integrated alternative endpoint to sentry. But they say that you can still use the sentry SDK, which this does.

When I test Javascript with my issued DSN it says it is successful. But the PHP test returns an error that it failed but no other information.

Was there anywhere to look for logs about what was returned, or any reason explicitly that this might not support the same SDK.

Gitlab's documentation on their integrated error tracking. https://docs.gitlab.com/ee/operations/error_tracking.html#integrated-error-tracking

EHLOVader commented 2 years ago

I've tried disabling gzip compression because of this related issue with their compatibility at Gitlab but that doesn't seem to have fixed it.

I did so with this snippet

add_filter( 'wp_sentry_options', function ( \Sentry\Options $options ) {

    $options->setEnableCompression(false);

    return $options;
} );

That is the correct way to attempt that right?

stayallive commented 2 years ago

Yep, but it's possible that is too late to do that, that setting should be set before the client is initialized so I think that is why it's not working. There is currently no way to modify this behaviour earlier, #99 has requested this so it might be doable in the future.

GitLab lightweight is not supported by the Sentry PHP SDK (and I suspect never will receive proper support for obvious reasons) so I'm also not going to do anything to make it work in this plugin 😄

It also looks like they already fixed the compression issues on their side so this might all start working after the next GitLab release.

EHLOVader commented 2 years ago

Thanks for the update @stayallive. Gitlab did fix this, so it looks like it is working for me now.