Sentry Extension sending report to incorrect DSN

Description

I have three sites on the same server setup with the Sentry extension, all with different Sentry DSN's, however, the error from each site are going to a random DSN and not the configured one.

It appears that it is selecting one of the DSN's in the configuration at random and sending the error to that DSN.

I have confirmed they all have different DSN's configured in the web admin of each for the exception log.

I am seeing errors from all three sites in all three projects in Sentry.

Environment

None

Activity

Pothys - MitrahSoft 
30 October 2024 at 12:01

, Please check this ticket with the latest version of Sentry. It works as expected for me, so I will go ahead and close the ticket.

Pothys - MitrahSoft 
22 October 2024 at 15:03

, I investigated this ticket with Lucee version 6.2.0.119-SNAPSHOT and Sentry version 5.5.2.15. I configured three sites with three different Sentry DSNs, and Sentry listed each error under the corresponding DSN. It works fine with the latest version, Could you please check it with the most recent Sentry version 5.5.2.15?

Pothys - MitrahSoft 
9 October 2024 at 10:35

, Could you please check this with the latest sentry version and report back here? This will help improve the status of this ticket.

Fixed

Details

Assignee

Reporter

Priority

Labels

New Issue warning screen

Before you create a new Issue, please post to the mailing list first https://dev.lucee.org

Once the issue has been verified, one of the Lucee team will ask you to file an issue

Affects versions

Created 13 February 2020 at 08:50
Updated 30 October 2024 at 12:01
Resolved 30 October 2024 at 12:01