Closed joerndyherrn closed 1 year ago
cleptric
commented
1 year ago @joerndyherrn I was talking to the devs of Api Platform during SymfonyCon, and we believe that this should just work out of the box. Can you maybe share your sentry.yaml here?
github-actions[bot]
commented
1 year ago This issue has gone three weeks without activity. In another week, I will close it.
But! If you comment or otherwise update it, I will reset the clock, and if you label it Status: Backlog or Status: In Progress, I will leave it alone ... forever!
"A weed is but an unloved flower." ― Ella Wheeler Wilcox 🥀
joerndyherrn
commented
1 year ago @cleptric Within the php project this is the configuration file:
sentry:
dsn: // removed it but the dsn for the backend project
tracing:
enabled: true
dbal:
enabled: true
cache:
enabled: true
twig:
enabled: true
options:
environment: '%kernel.environment%'
traces_sample_rate: 1.0
sample_rate: 1
error_types: 'E_ERROR'
before_send: 'sentry.callback.before_send'
services:
sentry.callback.before_send:
class: 'App\Service\Sentry'
factory: [ '@App\Service\Sentry', 'getBeforeSend' ]The before send function only checks for a custom exception which we want to ignore
In the frontend (react) project we got the following configuration:
Sentry.init({
dsn: // the dsn for the frontend project
integrations: [
new Integrations.BrowserTracing({
tracingOrigins: [
'https://example.com/', // originally we got absolute urls of the backend here
/^\//, // makes sure that all requests are traced
],
}),
],
environment: Environment.getEnvironment(),
release: Environment.getVersion(),
tracesSampleRate: getTracesSampleRate(),
});```
Environment
Steps to Reproduce
Expected Result
A trace for the api call should be created in sentry and if the call is made from a well configured frontend it should be within the same trace.
Actual Result
No trace is created and if an exception occurs the trace from this exception isn't related with the frontends issues/traces