New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Strapi performance monitoring broken in strapi v4? #5716
Comments
Hi, @DawnMD. Thanks for reporting! To clarify:
Is the lack of headers the way in which it broke, or do you mean that it broke in some other way and also headers are missing? In any case, we appreciate you letting us know, and as you suggest, it's quite possible that a change in strapi between versions 3 and 4 is causing this. I've put it on our backlog to investigate. In the meantime, community investigation or PRs welcome! |
Hi @lobsterkatie |
Greetings @DawnMD, Is there any news on this issue? |
Hey @Boghdady |
FYI, this is on our backlog but hasn't yet been roadmapped, so I can't say for sure how soon we're going to pick it up. (Just don't want to set unrealistic expectations.) That said, can you say a little more about "the issue with how the context object is handled for strapi V4 only?" What specifically are you seeing? |
Hi @lobsterkatie PS: I downgraded the |
Any chance there has been some movement on this issue? |
It works for me on latest Strapi 4, I've created global middleware:
Both tracing and error reporting are working fine. |
@akasummer yes without strapi plugin it works flawlessly. The issue is something to do with the strapi plugin I'm guessing and also there is no workaround as of now. |
@DawnMD I think @strapi/plugin-sentry doesn't even have any implementation for tracing (performance monitoring), only error reporting. I believe this issue should be raised with Strapi team, not Sentry. |
Is there an existing issue for this?
How do you use Sentry?
Sentry Saas (sentry.io)
Which package are you using?
@sentry/node
SDK Version
7.1.2
Framework Version
Strapi 4.3.4
Link to Sentry event
No response
Steps to Reproduce
strapi@latest
@strapi/sentry
plugin@sentry/node
and@sentry/tracing
latestsrc/middlewares/sentry.js
@strapi/sentry
atconfig/middlewares.js
asglobal::sentry
config/plugins.js
asExpected Result
Sentry should trace the transactions made by the API calls during navigation strapi or doing graphql queries. The exact thing worked for strapi v3 but after upgrading to v4 it broke and in the context request there are no headers for
sentry-tracing
Actual Result
This was from strapi v3 when it was working fine
The text was updated successfully, but these errors were encountered: