Springboot/AWS Project doesn't show any Sentry logs depending on Java Version/AWS usage

[ReneGreen27]

Environment

SaaS (https://sentry.io/)

Steps to Reproduce

Customer reports that they are not able to view Sentry logs in prod. Using AWS Elastic Beanstalk and buildspec.yaml And the buidspc.yaml defines Java phases: install: runtime-versions: java: corretto17

Found this in their logs: INFO a.a.u.LogMessageUtil. [ ] SENTRY-SENDING-EXCEPTION-TO-SENTRY: enabled: false, healthy: true

verified DSN is correct and that Sentry is not explicitly disabled

Customer reported to have tried the following versions, marked "WORKING" or "NOT WORKING" dependent on if logs were viewable:

Tested four different versions of JDK on my LOCAL Machine. LOCAL MACHINE (M1 Macbook Pro MAX) First: - WORKING openjdk version "17.0.7" 2023-04-18 LTS OpenJDK Runtime Environment Corretto-17.0.7.7.1 (build 17.0.7+7-LTS)

Second: WORKING openjdk version "17.0.11" 2024-04-16 LTS OpenJDK Runtime Environment Corretto-17.0.11.9.1 (build 17.0.11+9-LTS)

Third: NOT WORKING openjdk version "17.0.12" 2024-07-16 LTS OpenJDK Runtime Environment Corretto-17.0.12.7.1 (build 17.0.12+7-LTS)

Fourth: WORKING openjdk version "21.0.3" 2024-04-16 LTS OpenJDK Runtime Environment Corretto-21.0.3.9.1 (build 21.0.3+9-LTS)

..

AWS EC2 DEV: NOT WORKING openjdk version "21.0.4" 2024-07-16 LTS OpenJDK Runtime Environment Corretto-21.0.4.7.1 (build 21.0.4+7-LTS) OpenJDK 64-Bit Server VM Corretto-21.0.4.7.1 (build 21.0.4+7-LTS, mixed mode, sharing)

PROD: NOT WORKING openjdk version "17.0.12" 2024-07-16 LTS OpenJDK Runtime Environment Corretto-17.0.12.7.1 (build 17.0.12+7-LTS) OpenJDK 64-Bit Server VM Corretto-17.0.12.7.1 (build 17.0.12+7-LTS, mixed mode, sharing)

Internal ticket reference number is #128628

--

Expected Result

To be able to view Sentry logs

Actual Result

No Sentry logs are viewable depending on if AWS is used and Java version

Product Area

Unknown

Link

No response

DSN

No response

Version

No response

[getsantry[bot]]

Auto-routing to @getsentry/product-owners-issues for triage ⏲️

[mrduncan]

Can you clarify what you mean by "logs"?

This sounds like a potential SDK issue but just confirming before transferring to getsentry/sentry-java.

[yanggun7201]

Can you clarify what you mean by "logs"?

This sounds like a potential SDK issue but just confirming before transferring to getsentry/sentry-java.

That is the Sentry logs in Sentry issues page.

[mrduncan]

Can you share a link to one of the working and non-working events?

Feel free to email them to me if you don't want to share your organization name publicly: [email protected]

[yanggun7201]

Can you share a link to one of the working and non-working events?

Feel free to email them to me if you don't want to share your organization name publicly: [email protected]

It is not about events... it is about java version with sentry. Even though I configured debug=true, there was no debug logs and no sentry events at all with some java versions both in local and AWS EC2.

[adinauer]

We'll do some testing and update here once we know more. Can't give an ETA yet.

[lcian]

Tested the "NOT WORKING" versions both locally (ARM Mac) and in EC2 (Ubuntu Server 24 x64, ami-07eef52105e8a2059) with version 7.20.0 of the SDK. Events are captured correctly.

The log line

 INFO a.a.u.LogMessageUtil. [ ] SENTRY-SENDING-EXCEPTION-TO-SENTRY: enabled: false, healthy: true

makes me think that the customer is enabling/disabling sending events to Sentry based on some configuration of their app. The SDK never logs or stores anything of the form SENTRY-SENDING-EXCEPTION-TO-SENTRY (can be easily checked also by grepping through this repo).

I'm closing this for now. @yanggun7201 feel free to reopen the issue or add more information if this is still relevant.