Different sinks for front and backend

  • Resolved maven1129

    (@maven1129)


    5 months, 2 weeks ago

    first, thank you for making this. Really good software.

    second, I am new, and have been through the docs only a limited count of times yet. Do you have a quick suggestion for adding tags for backend vs front end errors (both php and js would be helpful). I know I can filter the text by user / logged in, which helps, but I imagine when building this for yourself that you had some ideas about isolating or understanding backend problems (admin area, builders, block editor) from front end generated issues affecting users rather than admins. Any tips?

Viewing 3 replies - 1 through 3 (of 3 total)
  • Plugin Author stayallive

    (@stayallive)

    I think your best bet might be filtering based on the URL, for example doing url:"*wp-* (you can paste this in the Sentry search).

    This difficulty is that the line between back-end front-end is a bit blurred with the usage of AJAX requests and the WordPress JSON API.

    In theory we can of course add a tag based on is_admin() but not sure if that is actually useful… it is something you can do yourself pretty easily if you want to see if that would solve your question.

    Thread Starter maven1129

    (@maven1129)

    I see what you mean. Is_admin is a tag id have to add to detect that the php errors occurred on the backend?

    Plugin Author stayallive

    (@stayallive)

    I meant that you could add a tag called “is_admin” with the value of whatever the is_admin() WordPress helper returns which you then can use to filter on inside the Sentry UI. You can apply tags for both the PHP and JS side of the integration.

Viewing 3 replies - 1 through 3 (of 3 total)
  • You must be logged in to reply to this topic.