Skip to content

No events captured when compiled in --release (production environment) #502

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

Closed
Niedzwiedzw opened this issue Sep 12, 2022 · 4 comments
Closed

Comments

@Niedzwiedzw
Copy link

Environment

What version are you running? Etc.

sentry = { version = "0.27.0", features = ["backtrace", "contexts", "httpdate",  "panic", "reqwest", "reqwest_", "rustls", "sentry-backtrace", "sentry-contexts", "sentry-panic", "sentry-tracing", "tokio", "transport",], default-features=false }
sentry-tracing = "0.27.0"
tracing = "0.1"

Steps to Reproduce

cd /tmp/
git clone https://github.com/Grupa-Pieprzyk/pieprzyk-logging
export TEST_SENTRY_URL=XXX
cargo test
cargo test --release

Expected Result

In my sentry dashboard I'd expect to see errors (events in general actually) that occured in production environment

Actual Result

I only see events for development environment (compiled without --release flag)

@Niedzwiedzw
Copy link
Author

this is a library I made to have a common configuration for logging across multiple apps I'm maintaining, not sure if it's a bug in this library or it's some configuration mistake I made
link to repo: https://github.com/Grupa-Pieprzyk/pieprzyk-logging

@Niedzwiedzw
Copy link
Author

Niedzwiedzw commented Sep 12, 2022

2022-09-12T21:38:22.513654Z DEBUG sentry: Failed to send envelope: error sending request for url (https://o486718.ingest.sentry.io/api/6782153/envelope/): error trying to connect: error:14090086:SSL routines:ssl3_get_server_certificate:certificate verify failed:s3_clnt.c:1269: (certificate has expired)

I've investigated further, this wasn't an issue with my dev/prod environment, but rather ... yeah /\

I'm running my stuff inside a docker container, no idea why that would cause an issue but yeah, if anyone has any ideas how to fix this please share :D

@Swatinem
Copy link
Member

Maybe you need to update your root CA certificates in the docker container? Otherwise not sure, certificates should be up to date on our end, maybe @beezz can double check?

@lcian
Copy link
Member

lcian commented Mar 12, 2025

I'm closing this issue, as there haven't been any updates in a while.
Please open a new issue if this is still relevant.
This seems to be the same scenario as #663

@lcian lcian closed this as not planned Won't fix, can't repro, duplicate, stale Mar 12, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants