SentryError: An event processor returned null, will not send event #3939
Comments
|
Looking at similar issues: #3047, this maybe because of the Dedupe integration. Are you receiving these errors in Sentry, or just in the debug console? If it's just in the debug console, this is expected behaviour, |
|
I'm seeing a similar issue in a React app. It is being reported to sentry, not just logged to the console. I don't have anything setting Sentry.init({
dsn: SENTRY_DSN,
environment: hostname,
allowUrls: [/.+\.example\.com/],
ignoreErrors: [
/NetworkError when attempting to fetch resource/,
/The operation is not supported/,
/The request is not allowed by the user agent or the platform in the current context/,
],
beforeSend(event) {
// exclude all events that have no stack trace
if (event.stacktrace?.frames?.length) {
return event
} else {
return null
}
},
})
Sentry.addGlobalEventProcessor(event => {
const fullstorySessionUrl = window.FS?.getCurrentSessionURL?.(true)
event.contexts = {
...(event.contexts || {}),
fullstory: fullstorySessionUrl,
}
event.extra = {
...(event.extra || {}),
fullstorySessionUrl,
}
return event
}) |
|
Could you provide your |
|
@AbhiPrasad was just updating my comment to add the init as you commented. Here's a link to the error in sentry: |
|
Would you mind trying to update the SDK to the latest version? In |
|
I'm not sure if this is the exact issue you're having or if this error and warning are a result of something different but I've been seeing the following all morning and had no idea why as it was fine yesterday. I hadn't changed anything since I was last working so I spent quite some time going through all the typical things to find the problem. Eventually I switched VPN (NordVPN) off, which I'd been using today, and the errors were gone. I tried on and off multiple times, rebuilding the app each time, and every time VPN was on, I had the issues. The rest of the time it was fine. |
|
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 "A weed is but an unloved flower." ― Ella Wheeler Wilcox 🥀 |
|
Thanks for the great library! Based on my observation, this thing will show up when you capture an exception using Unfortunately, Sentry just show the console.error of (which is kind of uninformative): without telling what kind of exception it is or any hint about that. Hope this can be improved later. CMIIW |
|
Hi, @endruuu. I'll bring this up with the team so we can discuss what we might be able to improve here. In the meantime, I'll reopen the issue so we don't lose track of it. |
lobsterkatie
added
Meta: Help Wanted
Package: core
Status: Backlog
Type: Improvement
and removed
Package: vue
Status: Stale
labels
|
@lobsterkatie Are there any updates on this? We upgraded to 6.18.1 and turned on logErrors and debug and started seeing this error in the console. We can't seem to get any errors to move to the dashboard with or without these flags turned on. |
|
We are likely to improve the logging here at some point, but I get that unfortunately that's not really your problem, it would just help you solve your problem. If you can repro this locally, I'd suggest starting by turning off all integrations (which are what add the event processors which drop events), and then adding them back in one by one until you see things being dropped. (Docs here.) Then once you know what's dropping the event, we can debug why it's getting dropped. |
|
Sentry Logger [Error]: SentryError: An event processor returned null, will not send event. |
|
@govind-v-natex I'd offer the same suggestion - try turning off integrations and adding them back in. The ones to try first would be I'm happy to help debug, but it's tough without more information or a repro. |
|
@lobsterkatie Hopefully this helps... we were also experiencing the same issue. After removing integrations and adding them back in, we found that |
|
@alexrdz - Interesting. And you're not seeing the actual reason logged? The function which does the filtering should tell you why it's dropping something: sentry-javascript/packages/core/src/integrations/inboundfilters.ts Lines 65 to 97 in 72aed62 |
|
Oh. I might get it. @alexrdz, how do you load sentry? CDN? npm package? |
|
Same issue here on browser 6.18.2. Loaded from npm, compiled via Webpack as a script we inject into our page. We throw an error like Interesting: If we disable the |
|
@lobsterkatie We are loading it via npm package in a Vue app. The only message or log we were receiving was |
|
I am also facing this error in a react native app. The only other message that looks realted is: |
|
@hossein - Ah, okay. If it's a script error, that explains why it's getting dropped. Could there be a CORS issue here? @alexrdz - Any chance this might apply to you as well? As for how you all are loading the package, I was really hoping you were going to say "from the CDN," because for a while there we were logging inconsistently in the bundles. But if you're using npm, it's a moot point, unfortunately. If you eliminate CORS as the issue, at that point I think in order to get any farther I'd need a minimal repro to poke at. Is that something either of you might be able to provide? |
|
Chiming in on this thread, since we just started seeing this as well, which seems to go away if you disable the Dedupe integration. That said, we're only seeing this in our terminal/console and not on Sentry itself, which, according to:
is expected behavior? Throwing it as an explicit error seems like the wrong level though, because if it is indeed expected shouldn't it be a warning or info level? Edit: This does also seem to go away if you set |
|
I'm seeing a slightly different version of this error in an Electron app using the I'm doing a vanilla init with just: Since I already have a Thereafter I am seeing the following in the console: However, the error still seems to show up in the Sentry web app, so not a showstopper. Through disabling default integrations one-by-one, I found that the error message was caused by the integration "EventToMain". The following init makes the error go away: Hope that helps. |
@johnnywang - That's a fair point, and something I've actually noticed and wanted to fix as well. I'll shove this into my mental backlog (it's already on our team backlog), and take a look at it if I get a chance. In the meantime, though, PRs on that score quite welcome! |
|
@erikjalevik - Thanks for that. Would you mind please just copying and pasting your comment as a new issue in https://github.com/getsentry/sentry-electron, and reference this issue? That way it will be seen by the electron team. |
|
State - closing |
|
State - closing |
|
I'm still running into this problem and the workaround doesn't help. |
|
@chirva-ivan the newest version should print information on which event processor dropped the event if you turn on |
|
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 "A weed is but an unloved flower." ― Ella Wheeler Wilcox 🥀 |
|
Hi I'm still seeing this on newest version |
|
@Shawnxkwang could you create a new issue and give your SDK version + a reproduction we can take a look at? |
Hello, in our web application based on vue 2.6.12 and @sentry/vue 6.10.0 client SDK (we tried even with 6.11.0) we facing with the following error:
Sentry Logger [Error]: SentryError: An event processor returned null, will not send event.Debugging a little bit the application i extracted the sentry event object that cause the error:
Hope this help to understand the problem. If you need more detail let me know.
The text was updated successfully, but these errors were encountered: