Skip to content
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

Missing messages despite debug logs showing responses #679

Open
mrhockeymonkey opened this issue Aug 12, 2024 · 1 comment
Open

Missing messages despite debug logs showing responses #679

mrhockeymonkey opened this issue Aug 12, 2024 · 1 comment

Comments

@mrhockeymonkey
Copy link

Environment

server: sentry on-prem 21.8.0
crate: sentry = "0.34.0"

Steps to Reproduce

I have a small application tailing logs and forwarding errors to sentry.

    if matches!(sentry_level, sentry::Level::Warning | sentry::Level::Error | sentry::Level::Fatal) {
        sentry::capture_message(&log.message(), sentry_level);
    }

This works fine if using sentry.io but messages do not appear on our on-prem sentry server.

Enabling debug in config only yields these messages

[sentry] Get response: `{"id":"c234eb164ff441d4810167b70dc29eab"}`
[sentry] Get response: `{"id":"b95c6f72d0114fca9c95a348ae4ce5fd"}`

Full code here: https://github.com/mrhockeymonkey/consul-beat/tree/main/consulbeat

Expected Result

Log message should appear in the UI as they do when using sentry.io.

Actual Result

No activity is seen in the UI

Is there anything else I can debug in this scenario? The readme says "should work with on-prem Sentry versions 20.6 and later", I hope that's still the case or was there some breaking change added?

@lcian
Copy link
Member

lcian commented Mar 6, 2025

Hi @mrhockeymonkey, sorry for the long turnaround here.
Unfortunately, we're only testing against the latest Sentry SaaS, and we're not planning to test against specific older versions.
In this case, I would advise you to enable debug logging for your Kafka consumers and check there.

If you found out that the SDK is really incompatible with that version, it would be great if you could confirm it and report any additional information you found here, so that we can reflect it in the README.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants