| 37726 |
amit |
1 |
#Sat, 19 Sep 2026 16:08:14 +0530
|
|
|
2 |
# Sentry/GlitchTip runtime options, read off the classpath by the SDK itself
|
|
|
3 |
# (io.sentry.config.PropertiesProviderFactory) and merged over whatever the
|
|
|
4 |
# Sentry appender in log4j2.xml configures.
|
|
|
5 |
#
|
|
|
6 |
# WHY THIS FILE EXISTS
|
|
|
7 |
#
|
|
|
8 |
# The DSN lives in log4j2.xml, which ships inside every build, so ANY machine
|
|
|
9 |
# running this code reports to the live GlitchTip project -- including a
|
|
|
10 |
# developer's laptop. Worse, the Sentry SDK defaults `environment` to
|
|
|
11 |
# "production" when it is unset, so those events arrived on the production
|
|
|
12 |
# board indistinguishable from real ones. That is how errors tagged
|
|
|
13 |
# environment=production came to carry server_name=<a developer's machine> and
|
|
|
14 |
# paths like /opt/homebrew/Cellar/tomcat@8/... (GlitchTip issue #586).
|
|
|
15 |
#
|
|
|
16 |
# The committed values below are therefore the SAFE ones: reporting OFF, and
|
|
|
17 |
# labelled dev. build.gradle overwrites both at build time from -Penv=, so only
|
|
|
18 |
# a deliberate `-Penv=staging|prod` build reports anything, and it is labelled
|
|
|
19 |
# correctly. A plain local build stays silent.
|
|
|
20 |
enabled=false
|
|
|
21 |
environment=dev
|