WORKERS AHEAD!

You are viewing the development documentation for the Apereo CAS server. The functionality presented here is not officially released yet. This is a work in progress and will be continually updated as development moves forward. You are most encouraged to test the changes presented.

Overview

Sentry allows you to track logs and error in real time. It provides insight into production deployments and information to reproduce and fix crashes.

The integration here supports error handling and reporting to Sentry, performance monitoring via spans and transactions as well as Sentry logging support.

Configuration

Support is enabled by including the following dependency in the WAR overlay:

<dependency>
    <groupId>org.apereo.cas</groupId>
    <artifactId>cas-server-support-sentry</artifactId>
    <version>${cas.version}</version>
</dependency>

implementation "org.apereo.cas:cas-server-support-sentry:${project.'cas.version'}"

dependencyManagement {
    imports {
        mavenBom "org.apereo.cas:cas-server-support-bom:${project.'cas.version'}"
    }
}

dependencies {
    implementation "org.apereo.cas:cas-server-support-sentry"
}

dependencies {
    /*
        The following platform references should be included automatically and are listed here for reference only.

        implementation enforcedPlatform("org.apereo.cas:cas-server-support-bom:${project.'cas.version'}")
        implementation platform(org.springframework.boot.gradle.plugin.SpringBootPlugin.BOM_COORDINATES)
        
    */
    implementation "org.apereo.cas:cas-server-support-sentry"
}

The Logging configuration file must be adjusted to match the following:

<?xml version="1.0" encoding="UTF-8"?>
<Configuration status="warn" packages="org.apache.logging.log4j.core,io.sentry.log4j2">
    <Appenders>
        <Console name="Console" target="SYSTEM_OUT">
            <PatternLayout pattern="%d{HH:mm:ss.SSS} [%t] %-5level %logger{36} - %msg%n"/>
        </Console>
        <!-- Setting minimumBreadcrumbLevel modifies the default minimum level to add breadcrumbs from INFO to DEBUG  -->
        <!-- Setting minimumEventLevel the default minimum level to capture an event from ERROR to WARN  -->
        <Sentry name="Sentry" 
                minimumBreadcrumbLevel="DEBUG"
                minimumEventLevel="WARN"
                dsn="..." />
    </Appenders>
    <Loggers>
        <Root level="INFO">
            <AppenderRef ref="Sentry"/>
            <AppenderRef ref="casConsole"/>
        </Root>
    </Loggers>
</Configuration>

The following settings and properties are available from the CAS configuration catalog:

_{The configuration settings listed below are tagged as Required in the CAS configuration metadata. This flag indicates that the presence of the setting may be needed to activate or affect the behavior of the CAS feature and generally should be reviewed, possibly owned and adjusted. If the setting is assigned a default value, you do not need to strictly put the setting in your copy of the configuration, but should review it nonetheless to make sure it matches your deployment expectations.}

_{The configuration settings listed below are tagged as Optional in the CAS configuration metadata. This
flag indicates that the presence of the setting
is not immediately necessary in the end-user CAS configuration, because a default value is assigned or
the activation of the feature is not conditionally controlled by the setting value. In other words, you should only include this field in your
configuration if you need to modify the default value or if you need to turn on the feature controlled by the setting.}

_{The configuration settings listed below are tagged as Third Party in the CAS configuration metadata. This flag indicates that the configuration setting is not controlled, owned or managed by the CAS ecosystem, and affects functionality that is offered by a third-party library, such as Spring Boot or Spring Cloud to CAS. For additional info, you might have to visit the third-party source to find more details.}

sentry.attach-server-name=

io.sentry.spring.boot.jakarta.SentryProperties.

_{How can I configure this property?}

Configuration properties can be included and activated using the following strategies.

Note

When possible, properties should be stored in lower-case kebab format, such as cas.property-name=value. The only possible exception to this rule is when naming actuator endpoints; The name of the actuator endpoints (i.e. ssoSessions) MUST remain in camelCase mode.

CAS properties can be specified using the Java configuration property syntax in any and all .properties files:

sentry.attach-server-name=...

This is the most common form of property configuration that is recognized by CAS, regardless of the actual property source, which might in fact be managed separately outside the CAS environment, by another system or cloud framework.

CAS properties can be specified using the YAML syntax:

sentry: 
  attach-server-name: "..."

Note that YAML is very specific about structure and indentation. Be sure to verify the correctness of the final result with your YAML validator of choice.

CAS properties can be passed to the CAS web application as system properties, when the application is launched:

java -Dsentry.attach-server-name="..." -jar build/libs/cas.war

The above example assumes that the CAS web application is packaged as cas.war with an embedded server container and can be found in the build/libs directory. Note the placement of the system property which must be specified before the CAS web application is launched.

CAS properties can specified as system environment variables before the CAS web application is launched:

export SENTRY_ATTACH_SERVER_NAME="..."

java -jar build/libs/cas.war

The above example assumes that the CAS web application is packaged as cas.war with an embedded server container and can be found in the build/libs directory.

CAS properties can be passed to the CAS web application as command-line arguments, when the application is launched:

java -jar build/libs/cas.war --sentry.attach-server-name="..."

The above example assumes that the CAS web application is packaged as cas.war with an embedded server container and can be found in the build/libs directory.

sentry.attach-stacktrace=

io.sentry.spring.boot.jakarta.SentryProperties.

_{How can I configure this property?}

Configuration properties can be included and activated using the following strategies.

Note

CAS properties can be specified using the Java configuration property syntax in any and all .properties files:

sentry.attach-stacktrace=...

CAS properties can be specified using the YAML syntax:

sentry: 
  attach-stacktrace: "..."

Note that YAML is very specific about structure and indentation. Be sure to verify the correctness of the final result with your YAML validator of choice.

CAS properties can be passed to the CAS web application as system properties, when the application is launched:

java -Dsentry.attach-stacktrace="..." -jar build/libs/cas.war

CAS properties can specified as system environment variables before the CAS web application is launched:

export SENTRY_ATTACH_STACKTRACE="..."

java -jar build/libs/cas.war

The above example assumes that the CAS web application is packaged as cas.war with an embedded server container and can be found in the build/libs directory.

CAS properties can be passed to the CAS web application as command-line arguments, when the application is launched:

java -jar build/libs/cas.war --sentry.attach-stacktrace="..."

The above example assumes that the CAS web application is packaged as cas.war with an embedded server container and can be found in the build/libs directory.

sentry.attach-threads=

io.sentry.spring.boot.jakarta.SentryProperties.

_{How can I configure this property?}

Configuration properties can be included and activated using the following strategies.

Note

CAS properties can be specified using the Java configuration property syntax in any and all .properties files:

sentry.attach-threads=...

CAS properties can be specified using the YAML syntax:

sentry: 
  attach-threads: "..."

Note that YAML is very specific about structure and indentation. Be sure to verify the correctness of the final result with your YAML validator of choice.

CAS properties can be passed to the CAS web application as system properties, when the application is launched:

java -Dsentry.attach-threads="..." -jar build/libs/cas.war

CAS properties can specified as system environment variables before the CAS web application is launched:

export SENTRY_ATTACH_THREADS="..."

java -jar build/libs/cas.war

The above example assumes that the CAS web application is packaged as cas.war with an embedded server container and can be found in the build/libs directory.

CAS properties can be passed to the CAS web application as command-line arguments, when the application is launched:

java -jar build/libs/cas.war --sentry.attach-threads="..."

The above example assumes that the CAS web application is packaged as cas.war with an embedded server container and can be found in the build/libs directory.

sentry.backpressure-monitor=

io.sentry.spring.boot.jakarta.SentryProperties.

_{How can I configure this property?}

Configuration properties can be included and activated using the following strategies.

Note

CAS properties can be specified using the Java configuration property syntax in any and all .properties files:

sentry.backpressure-monitor=...

CAS properties can be specified using the YAML syntax:

sentry: 
  backpressure-monitor: "..."

Note that YAML is very specific about structure and indentation. Be sure to verify the correctness of the final result with your YAML validator of choice.

CAS properties can be passed to the CAS web application as system properties, when the application is launched:

java -Dsentry.backpressure-monitor="..." -jar build/libs/cas.war

CAS properties can specified as system environment variables before the CAS web application is launched:

export SENTRY_BACKPRESSURE_MONITOR="..."

java -jar build/libs/cas.war

The above example assumes that the CAS web application is packaged as cas.war with an embedded server container and can be found in the build/libs directory.

CAS properties can be passed to the CAS web application as command-line arguments, when the application is launched:

java -jar build/libs/cas.war --sentry.backpressure-monitor="..."

The above example assumes that the CAS web application is packaged as cas.war with an embedded server container and can be found in the build/libs directory.

sentry.bundle-ids=

io.sentry.spring.boot.jakarta.SentryProperties.

_{How can I configure this property?}

Configuration properties can be included and activated using the following strategies.

Note

CAS properties can be specified using the Java configuration property syntax in any and all .properties files:

sentry.bundle-ids=...

CAS properties can be specified using the YAML syntax:

sentry: 
  bundle-ids: "..."

Note that YAML is very specific about structure and indentation. Be sure to verify the correctness of the final result with your YAML validator of choice.

CAS properties can be passed to the CAS web application as system properties, when the application is launched:

java -Dsentry.bundle-ids="..." -jar build/libs/cas.war

CAS properties can specified as system environment variables before the CAS web application is launched:

export SENTRY_BUNDLE_IDS="..."

java -jar build/libs/cas.war

The above example assumes that the CAS web application is packaged as cas.war with an embedded server container and can be found in the build/libs directory.

CAS properties can be passed to the CAS web application as command-line arguments, when the application is launched:

java -jar build/libs/cas.war --sentry.bundle-ids="..."

The above example assumes that the CAS web application is packaged as cas.war with an embedded server container and can be found in the build/libs directory.

sentry.cache-dir-path=

io.sentry.spring.boot.jakarta.SentryProperties.

_{How can I configure this property?}

Configuration properties can be included and activated using the following strategies.

Note

CAS properties can be specified using the Java configuration property syntax in any and all .properties files:

sentry.cache-dir-path=...

CAS properties can be specified using the YAML syntax:

sentry: 
  cache-dir-path: "..."

Note that YAML is very specific about structure and indentation. Be sure to verify the correctness of the final result with your YAML validator of choice.

CAS properties can be passed to the CAS web application as system properties, when the application is launched:

java -Dsentry.cache-dir-path="..." -jar build/libs/cas.war

CAS properties can specified as system environment variables before the CAS web application is launched:

export SENTRY_CACHE_DIR_PATH="..."

java -jar build/libs/cas.war

The above example assumes that the CAS web application is packaged as cas.war with an embedded server container and can be found in the build/libs directory.

CAS properties can be passed to the CAS web application as command-line arguments, when the application is launched:

java -jar build/libs/cas.war --sentry.cache-dir-path="..."

The above example assumes that the CAS web application is packaged as cas.war with an embedded server container and can be found in the build/libs directory.

sentry.connection-status-provider=

io.sentry.spring.boot.jakarta.SentryProperties.

_{How can I configure this property?}

Configuration properties can be included and activated using the following strategies.

Note

CAS properties can be specified using the Java configuration property syntax in any and all .properties files:

sentry.connection-status-provider=...

CAS properties can be specified using the YAML syntax:

sentry: 
  connection-status-provider: "..."

Note that YAML is very specific about structure and indentation. Be sure to verify the correctness of the final result with your YAML validator of choice.

CAS properties can be passed to the CAS web application as system properties, when the application is launched:

java -Dsentry.connection-status-provider="..." -jar build/libs/cas.war

CAS properties can specified as system environment variables before the CAS web application is launched:

export SENTRY_CONNECTION_STATUS_PROVIDER="..."

java -jar build/libs/cas.war

The above example assumes that the CAS web application is packaged as cas.war with an embedded server container and can be found in the build/libs directory.

CAS properties can be passed to the CAS web application as command-line arguments, when the application is launched:

java -jar build/libs/cas.war --sentry.connection-status-provider="..."

The above example assumes that the CAS web application is packaged as cas.war with an embedded server container and can be found in the build/libs directory.

sentry.connection-timeout-millis=

io.sentry.spring.boot.jakarta.SentryProperties.

_{How can I configure this property?}

Configuration properties can be included and activated using the following strategies.

Note

CAS properties can be specified using the Java configuration property syntax in any and all .properties files:

sentry.connection-timeout-millis=...

CAS properties can be specified using the YAML syntax:

sentry: 
  connection-timeout-millis: "..."

Note that YAML is very specific about structure and indentation. Be sure to verify the correctness of the final result with your YAML validator of choice.

CAS properties can be passed to the CAS web application as system properties, when the application is launched:

java -Dsentry.connection-timeout-millis="..." -jar build/libs/cas.war

CAS properties can specified as system environment variables before the CAS web application is launched:

export SENTRY_CONNECTION_TIMEOUT_MILLIS="..."

java -jar build/libs/cas.war

The above example assumes that the CAS web application is packaged as cas.war with an embedded server container and can be found in the build/libs directory.

CAS properties can be passed to the CAS web application as command-line arguments, when the application is launched:

java -jar build/libs/cas.war --sentry.connection-timeout-millis="..."

The above example assumes that the CAS web application is packaged as cas.war with an embedded server container and can be found in the build/libs directory.

sentry.context-tags=

io.sentry.spring.boot.jakarta.SentryProperties.

_{How can I configure this property?}

Configuration properties can be included and activated using the following strategies.

Note

CAS properties can be specified using the Java configuration property syntax in any and all .properties files:

sentry.context-tags=...

CAS properties can be specified using the YAML syntax:

sentry: 
  context-tags: "..."

Note that YAML is very specific about structure and indentation. Be sure to verify the correctness of the final result with your YAML validator of choice.

CAS properties can be passed to the CAS web application as system properties, when the application is launched:

java -Dsentry.context-tags="..." -jar build/libs/cas.war

CAS properties can specified as system environment variables before the CAS web application is launched:

export SENTRY_CONTEXT_TAGS="..."

java -jar build/libs/cas.war

The above example assumes that the CAS web application is packaged as cas.war with an embedded server container and can be found in the build/libs directory.

CAS properties can be passed to the CAS web application as command-line arguments, when the application is launched:

java -jar build/libs/cas.war --sentry.context-tags="..."

The above example assumes that the CAS web application is packaged as cas.war with an embedded server container and can be found in the build/libs directory.

sentry.cron.default-checkin-margin=

io.sentry.SentryOptions$Cron.

_{How can I configure this property?}

Configuration properties can be included and activated using the following strategies.

Note

CAS properties can be specified using the Java configuration property syntax in any and all .properties files:

sentry.cron.default-checkin-margin=...

CAS properties can be specified using the YAML syntax:

sentry: 
  cron: 
    default-checkin-margin: "..."

Note that YAML is very specific about structure and indentation. Be sure to verify the correctness of the final result with your YAML validator of choice.

CAS properties can be passed to the CAS web application as system properties, when the application is launched:

java -Dsentry.cron.default-checkin-margin="..." -jar build/libs/cas.war

CAS properties can specified as system environment variables before the CAS web application is launched:

export SENTRY_CRON_DEFAULT_CHECKIN_MARGIN="..."

java -jar build/libs/cas.war

The above example assumes that the CAS web application is packaged as cas.war with an embedded server container and can be found in the build/libs directory.

CAS properties can be passed to the CAS web application as command-line arguments, when the application is launched:

java -jar build/libs/cas.war --sentry.cron.default-checkin-margin="..."

The above example assumes that the CAS web application is packaged as cas.war with an embedded server container and can be found in the build/libs directory.

sentry.cron.default-failure-issue-threshold=

io.sentry.SentryOptions$Cron.

_{How can I configure this property?}

Configuration properties can be included and activated using the following strategies.

Note

CAS properties can be specified using the Java configuration property syntax in any and all .properties files:

sentry.cron.default-failure-issue-threshold=...

CAS properties can be specified using the YAML syntax:

sentry: 
  cron: 
    default-failure-issue-threshold: "..."

Note that YAML is very specific about structure and indentation. Be sure to verify the correctness of the final result with your YAML validator of choice.

CAS properties can be passed to the CAS web application as system properties, when the application is launched:

java -Dsentry.cron.default-failure-issue-threshold="..." -jar build/libs/cas.war

CAS properties can specified as system environment variables before the CAS web application is launched:

export SENTRY_CRON_DEFAULT_FAILURE_ISSUE_THRESHOLD="..."

java -jar build/libs/cas.war

The above example assumes that the CAS web application is packaged as cas.war with an embedded server container and can be found in the build/libs directory.

CAS properties can be passed to the CAS web application as command-line arguments, when the application is launched:

java -jar build/libs/cas.war --sentry.cron.default-failure-issue-threshold="..."

The above example assumes that the CAS web application is packaged as cas.war with an embedded server container and can be found in the build/libs directory.

sentry.cron.default-max-runtime=

io.sentry.SentryOptions$Cron.

_{How can I configure this property?}

Configuration properties can be included and activated using the following strategies.

Note

CAS properties can be specified using the Java configuration property syntax in any and all .properties files:

sentry.cron.default-max-runtime=...

CAS properties can be specified using the YAML syntax:

sentry: 
  cron: 
    default-max-runtime: "..."

Note that YAML is very specific about structure and indentation. Be sure to verify the correctness of the final result with your YAML validator of choice.

CAS properties can be passed to the CAS web application as system properties, when the application is launched:

java -Dsentry.cron.default-max-runtime="..." -jar build/libs/cas.war

CAS properties can specified as system environment variables before the CAS web application is launched:

export SENTRY_CRON_DEFAULT_MAX_RUNTIME="..."

java -jar build/libs/cas.war

The above example assumes that the CAS web application is packaged as cas.war with an embedded server container and can be found in the build/libs directory.

CAS properties can be passed to the CAS web application as command-line arguments, when the application is launched:

java -jar build/libs/cas.war --sentry.cron.default-max-runtime="..."

The above example assumes that the CAS web application is packaged as cas.war with an embedded server container and can be found in the build/libs directory.

sentry.cron.default-recovery-threshold=

io.sentry.SentryOptions$Cron.

_{How can I configure this property?}

Configuration properties can be included and activated using the following strategies.

Note

CAS properties can be specified using the Java configuration property syntax in any and all .properties files:

sentry.cron.default-recovery-threshold=...

CAS properties can be specified using the YAML syntax:

sentry: 
  cron: 
    default-recovery-threshold: "..."

Note that YAML is very specific about structure and indentation. Be sure to verify the correctness of the final result with your YAML validator of choice.

CAS properties can be passed to the CAS web application as system properties, when the application is launched:

java -Dsentry.cron.default-recovery-threshold="..." -jar build/libs/cas.war

CAS properties can specified as system environment variables before the CAS web application is launched:

export SENTRY_CRON_DEFAULT_RECOVERY_THRESHOLD="..."

java -jar build/libs/cas.war

The above example assumes that the CAS web application is packaged as cas.war with an embedded server container and can be found in the build/libs directory.

CAS properties can be passed to the CAS web application as command-line arguments, when the application is launched:

java -jar build/libs/cas.war --sentry.cron.default-recovery-threshold="..."

The above example assumes that the CAS web application is packaged as cas.war with an embedded server container and can be found in the build/libs directory.

sentry.cron.default-timezone=

io.sentry.SentryOptions$Cron.

_{How can I configure this property?}

Configuration properties can be included and activated using the following strategies.

Note

CAS properties can be specified using the Java configuration property syntax in any and all .properties files:

sentry.cron.default-timezone=...

CAS properties can be specified using the YAML syntax:

sentry: 
  cron: 
    default-timezone: "..."

Note that YAML is very specific about structure and indentation. Be sure to verify the correctness of the final result with your YAML validator of choice.

CAS properties can be passed to the CAS web application as system properties, when the application is launched:

java -Dsentry.cron.default-timezone="..." -jar build/libs/cas.war

CAS properties can specified as system environment variables before the CAS web application is launched:

export SENTRY_CRON_DEFAULT_TIMEZONE="..."

java -jar build/libs/cas.war

The above example assumes that the CAS web application is packaged as cas.war with an embedded server container and can be found in the build/libs directory.

CAS properties can be passed to the CAS web application as command-line arguments, when the application is launched:

java -jar build/libs/cas.war --sentry.cron.default-timezone="..."

The above example assumes that the CAS web application is packaged as cas.war with an embedded server container and can be found in the build/libs directory.

sentry.date-provider=

io.sentry.spring.boot.jakarta.SentryProperties.

_{How can I configure this property?}

Configuration properties can be included and activated using the following strategies.

Note

CAS properties can be specified using the Java configuration property syntax in any and all .properties files:

sentry.date-provider=...

CAS properties can be specified using the YAML syntax:

sentry: 
  date-provider: "..."

Note that YAML is very specific about structure and indentation. Be sure to verify the correctness of the final result with your YAML validator of choice.

CAS properties can be passed to the CAS web application as system properties, when the application is launched:

java -Dsentry.date-provider="..." -jar build/libs/cas.war

CAS properties can specified as system environment variables before the CAS web application is launched:

export SENTRY_DATE_PROVIDER="..."

java -jar build/libs/cas.war

The above example assumes that the CAS web application is packaged as cas.war with an embedded server container and can be found in the build/libs directory.

CAS properties can be passed to the CAS web application as command-line arguments, when the application is launched:

java -jar build/libs/cas.war --sentry.date-provider="..."

The above example assumes that the CAS web application is packaged as cas.war with an embedded server container and can be found in the build/libs directory.

sentry.debug=

io.sentry.spring.boot.jakarta.SentryProperties.

_{How can I configure this property?}

Configuration properties can be included and activated using the following strategies.

Note

CAS properties can be specified using the Java configuration property syntax in any and all .properties files:

sentry.debug=...

CAS properties can be specified using the YAML syntax:

sentry: 
  debug: "..."

Note that YAML is very specific about structure and indentation. Be sure to verify the correctness of the final result with your YAML validator of choice.

CAS properties can be passed to the CAS web application as system properties, when the application is launched:

java -Dsentry.debug="..." -jar build/libs/cas.war

CAS properties can specified as system environment variables before the CAS web application is launched:

export SENTRY_DEBUG="..."

java -jar build/libs/cas.war

The above example assumes that the CAS web application is packaged as cas.war with an embedded server container and can be found in the build/libs directory.

CAS properties can be passed to the CAS web application as command-line arguments, when the application is launched:

java -jar build/libs/cas.war --sentry.debug="..."

The above example assumes that the CAS web application is packaged as cas.war with an embedded server container and can be found in the build/libs directory.

sentry.debug-meta-loader=

io.sentry.spring.boot.jakarta.SentryProperties.

_{How can I configure this property?}

Configuration properties can be included and activated using the following strategies.

Note

CAS properties can be specified using the Java configuration property syntax in any and all .properties files:

sentry.debug-meta-loader=...

CAS properties can be specified using the YAML syntax:

sentry: 
  debug-meta-loader: "..."

Note that YAML is very specific about structure and indentation. Be sure to verify the correctness of the final result with your YAML validator of choice.

CAS properties can be passed to the CAS web application as system properties, when the application is launched:

java -Dsentry.debug-meta-loader="..." -jar build/libs/cas.war

CAS properties can specified as system environment variables before the CAS web application is launched:

export SENTRY_DEBUG_META_LOADER="..."

java -jar build/libs/cas.war

The above example assumes that the CAS web application is packaged as cas.war with an embedded server container and can be found in the build/libs directory.

CAS properties can be passed to the CAS web application as command-line arguments, when the application is launched:

java -jar build/libs/cas.war --sentry.debug-meta-loader="..."

The above example assumes that the CAS web application is packaged as cas.war with an embedded server container and can be found in the build/libs directory.

sentry.diagnostic-level=

io.sentry.spring.boot.jakarta.SentryProperties.

_{How can I configure this property?}

Configuration properties can be included and activated using the following strategies.

Note

CAS properties can be specified using the Java configuration property syntax in any and all .properties files:

sentry.diagnostic-level=...

CAS properties can be specified using the YAML syntax:

sentry: 
  diagnostic-level: "..."

Note that YAML is very specific about structure and indentation. Be sure to verify the correctness of the final result with your YAML validator of choice.

CAS properties can be passed to the CAS web application as system properties, when the application is launched:

java -Dsentry.diagnostic-level="..." -jar build/libs/cas.war

CAS properties can specified as system environment variables before the CAS web application is launched:

export SENTRY_DIAGNOSTIC_LEVEL="..."

java -jar build/libs/cas.war

The above example assumes that the CAS web application is packaged as cas.war with an embedded server container and can be found in the build/libs directory.

CAS properties can be passed to the CAS web application as command-line arguments, when the application is launched:

java -jar build/libs/cas.war --sentry.diagnostic-level="..."

The above example assumes that the CAS web application is packaged as cas.war with an embedded server container and can be found in the build/libs directory.

sentry.dist=

io.sentry.spring.boot.jakarta.SentryProperties.

_{How can I configure this property?}

Configuration properties can be included and activated using the following strategies.

Note

CAS properties can be specified using the Java configuration property syntax in any and all .properties files:

sentry.dist=...

CAS properties can be specified using the YAML syntax:

sentry: 
  dist: "..."

Note that YAML is very specific about structure and indentation. Be sure to verify the correctness of the final result with your YAML validator of choice.

CAS properties can be passed to the CAS web application as system properties, when the application is launched:

java -Dsentry.dist="..." -jar build/libs/cas.war

CAS properties can specified as system environment variables before the CAS web application is launched:

export SENTRY_DIST="..."

java -jar build/libs/cas.war

The above example assumes that the CAS web application is packaged as cas.war with an embedded server container and can be found in the build/libs directory.

CAS properties can be passed to the CAS web application as command-line arguments, when the application is launched:

java -jar build/libs/cas.war --sentry.dist="..."

The above example assumes that the CAS web application is packaged as cas.war with an embedded server container and can be found in the build/libs directory.

sentry.distinct-id=

io.sentry.spring.boot.jakarta.SentryProperties.

_{How can I configure this property?}

Configuration properties can be included and activated using the following strategies.

Note

CAS properties can be specified using the Java configuration property syntax in any and all .properties files:

sentry.distinct-id=...

CAS properties can be specified using the YAML syntax:

sentry: 
  distinct-id: "..."

Note that YAML is very specific about structure and indentation. Be sure to verify the correctness of the final result with your YAML validator of choice.

CAS properties can be passed to the CAS web application as system properties, when the application is launched:

java -Dsentry.distinct-id="..." -jar build/libs/cas.war

CAS properties can specified as system environment variables before the CAS web application is launched:

export SENTRY_DISTINCT_ID="..."

java -jar build/libs/cas.war

The above example assumes that the CAS web application is packaged as cas.war with an embedded server container and can be found in the build/libs directory.

CAS properties can be passed to the CAS web application as command-line arguments, when the application is launched:

java -jar build/libs/cas.war --sentry.distinct-id="..."

The above example assumes that the CAS web application is packaged as cas.war with an embedded server container and can be found in the build/libs directory.

sentry.dsn=

io.sentry.spring.boot.jakarta.SentryProperties.

_{How can I configure this property?}

Configuration properties can be included and activated using the following strategies.

Note

CAS properties can be specified using the Java configuration property syntax in any and all .properties files:

sentry.dsn=...

CAS properties can be specified using the YAML syntax:

sentry: 
  dsn: "..."

Note that YAML is very specific about structure and indentation. Be sure to verify the correctness of the final result with your YAML validator of choice.

CAS properties can be passed to the CAS web application as system properties, when the application is launched:

java -Dsentry.dsn="..." -jar build/libs/cas.war

CAS properties can specified as system environment variables before the CAS web application is launched:

export SENTRY_DSN="..."

java -jar build/libs/cas.war

The above example assumes that the CAS web application is packaged as cas.war with an embedded server container and can be found in the build/libs directory.

CAS properties can be passed to the CAS web application as command-line arguments, when the application is launched:

java -jar build/libs/cas.war --sentry.dsn="..."

The above example assumes that the CAS web application is packaged as cas.war with an embedded server container and can be found in the build/libs directory.

sentry.enable-aot-compatibility=false

If set to true, this flag disables all AOP related features (e.g. io.sentry.spring.jakarta.tracing.SentryTransaction, io.sentry.spring.jakarta.tracing.SentrySpan) to successfully compile to GraalVM

io.sentry.spring.boot.jakarta.SentryProperties.

_{How can I configure this property?}

Configuration properties can be included and activated using the following strategies.

Note

CAS properties can be specified using the Java configuration property syntax in any and all .properties files:

sentry.enable-aot-compatibility=...

CAS properties can be specified using the YAML syntax:

sentry: 
  enable-aot-compatibility: "..."

Note that YAML is very specific about structure and indentation. Be sure to verify the correctness of the final result with your YAML validator of choice.

CAS properties can be passed to the CAS web application as system properties, when the application is launched:

java -Dsentry.enable-aot-compatibility="..." -jar build/libs/cas.war

CAS properties can specified as system environment variables before the CAS web application is launched:

export SENTRY_ENABLE_AOT_COMPATIBILITY="..."

java -jar build/libs/cas.war

The above example assumes that the CAS web application is packaged as cas.war with an embedded server container and can be found in the build/libs directory.

CAS properties can be passed to the CAS web application as command-line arguments, when the application is launched:

java -jar build/libs/cas.war --sentry.enable-aot-compatibility="..."

The above example assumes that the CAS web application is packaged as cas.war with an embedded server container and can be found in the build/libs directory.

sentry.enable-app-start-profiling=

io.sentry.spring.boot.jakarta.SentryProperties.

_{How can I configure this property?}

Configuration properties can be included and activated using the following strategies.

Note

CAS properties can be specified using the Java configuration property syntax in any and all .properties files:

sentry.enable-app-start-profiling=...

CAS properties can be specified using the YAML syntax:

sentry: 
  enable-app-start-profiling: "..."

Note that YAML is very specific about structure and indentation. Be sure to verify the correctness of the final result with your YAML validator of choice.

CAS properties can be passed to the CAS web application as system properties, when the application is launched:

java -Dsentry.enable-app-start-profiling="..." -jar build/libs/cas.war

CAS properties can specified as system environment variables before the CAS web application is launched:

export SENTRY_ENABLE_APP_START_PROFILING="..."

java -jar build/libs/cas.war

The above example assumes that the CAS web application is packaged as cas.war with an embedded server container and can be found in the build/libs directory.

CAS properties can be passed to the CAS web application as command-line arguments, when the application is launched:

java -jar build/libs/cas.war --sentry.enable-app-start-profiling="..."

The above example assumes that the CAS web application is packaged as cas.war with an embedded server container and can be found in the build/libs directory.

sentry.enable-auto-session-tracking=

io.sentry.spring.boot.jakarta.SentryProperties.

_{How can I configure this property?}

Configuration properties can be included and activated using the following strategies.

Note

CAS properties can be specified using the Java configuration property syntax in any and all .properties files:

sentry.enable-auto-session-tracking=...

CAS properties can be specified using the YAML syntax:

sentry: 
  enable-auto-session-tracking: "..."

Note that YAML is very specific about structure and indentation. Be sure to verify the correctness of the final result with your YAML validator of choice.

CAS properties can be passed to the CAS web application as system properties, when the application is launched:

java -Dsentry.enable-auto-session-tracking="..." -jar build/libs/cas.war

CAS properties can specified as system environment variables before the CAS web application is launched:

export SENTRY_ENABLE_AUTO_SESSION_TRACKING="..."

java -jar build/libs/cas.war

The above example assumes that the CAS web application is packaged as cas.war with an embedded server container and can be found in the build/libs directory.

CAS properties can be passed to the CAS web application as command-line arguments, when the application is launched:

java -jar build/libs/cas.war --sentry.enable-auto-session-tracking="..."

The above example assumes that the CAS web application is packaged as cas.war with an embedded server container and can be found in the build/libs directory.

sentry.enable-backpressure-handling=

io.sentry.spring.boot.jakarta.SentryProperties.

_{How can I configure this property?}

Configuration properties can be included and activated using the following strategies.

Note

CAS properties can be specified using the Java configuration property syntax in any and all .properties files:

sentry.enable-backpressure-handling=...

CAS properties can be specified using the YAML syntax:

sentry: 
  enable-backpressure-handling: "..."

Note that YAML is very specific about structure and indentation. Be sure to verify the correctness of the final result with your YAML validator of choice.

CAS properties can be passed to the CAS web application as system properties, when the application is launched:

java -Dsentry.enable-backpressure-handling="..." -jar build/libs/cas.war

CAS properties can specified as system environment variables before the CAS web application is launched:

export SENTRY_ENABLE_BACKPRESSURE_HANDLING="..."

java -jar build/libs/cas.war

The above example assumes that the CAS web application is packaged as cas.war with an embedded server container and can be found in the build/libs directory.

CAS properties can be passed to the CAS web application as command-line arguments, when the application is launched:

java -jar build/libs/cas.war --sentry.enable-backpressure-handling="..."

The above example assumes that the CAS web application is packaged as cas.war with an embedded server container and can be found in the build/libs directory.

sentry.enable-deduplication=

io.sentry.spring.boot.jakarta.SentryProperties.

_{How can I configure this property?}

Configuration properties can be included and activated using the following strategies.

Note

CAS properties can be specified using the Java configuration property syntax in any and all .properties files:

sentry.enable-deduplication=...

CAS properties can be specified using the YAML syntax:

sentry: 
  enable-deduplication: "..."

Note that YAML is very specific about structure and indentation. Be sure to verify the correctness of the final result with your YAML validator of choice.

CAS properties can be passed to the CAS web application as system properties, when the application is launched:

java -Dsentry.enable-deduplication="..." -jar build/libs/cas.war

CAS properties can specified as system environment variables before the CAS web application is launched:

export SENTRY_ENABLE_DEDUPLICATION="..."

java -jar build/libs/cas.war

The above example assumes that the CAS web application is packaged as cas.war with an embedded server container and can be found in the build/libs directory.

CAS properties can be passed to the CAS web application as command-line arguments, when the application is launched:

java -jar build/libs/cas.war --sentry.enable-deduplication="..."

The above example assumes that the CAS web application is packaged as cas.war with an embedded server container and can be found in the build/libs directory.

sentry.enable-default-tags-for-metrics=

io.sentry.spring.boot.jakarta.SentryProperties.

_{How can I configure this property?}

Configuration properties can be included and activated using the following strategies.

Note

CAS properties can be specified using the Java configuration property syntax in any and all .properties files:

sentry.enable-default-tags-for-metrics=...

CAS properties can be specified using the YAML syntax:

sentry: 
  enable-default-tags-for-metrics: "..."

Note that YAML is very specific about structure and indentation. Be sure to verify the correctness of the final result with your YAML validator of choice.

CAS properties can be passed to the CAS web application as system properties, when the application is launched:

java -Dsentry.enable-default-tags-for-metrics="..." -jar build/libs/cas.war

CAS properties can specified as system environment variables before the CAS web application is launched:

export SENTRY_ENABLE_DEFAULT_TAGS_FOR_METRICS="..."

java -jar build/libs/cas.war

The above example assumes that the CAS web application is packaged as cas.war with an embedded server container and can be found in the build/libs directory.

CAS properties can be passed to the CAS web application as command-line arguments, when the application is launched:

java -jar build/libs/cas.war --sentry.enable-default-tags-for-metrics="..."

The above example assumes that the CAS web application is packaged as cas.war with an embedded server container and can be found in the build/libs directory.

sentry.enable-external-configuration=

io.sentry.spring.boot.jakarta.SentryProperties.

_{How can I configure this property?}

Configuration properties can be included and activated using the following strategies.

Note

CAS properties can be specified using the Java configuration property syntax in any and all .properties files:

sentry.enable-external-configuration=...

CAS properties can be specified using the YAML syntax:

sentry: 
  enable-external-configuration: "..."

Note that YAML is very specific about structure and indentation. Be sure to verify the correctness of the final result with your YAML validator of choice.

CAS properties can be passed to the CAS web application as system properties, when the application is launched:

java -Dsentry.enable-external-configuration="..." -jar build/libs/cas.war

CAS properties can specified as system environment variables before the CAS web application is launched:

export SENTRY_ENABLE_EXTERNAL_CONFIGURATION="..."

java -jar build/libs/cas.war

The above example assumes that the CAS web application is packaged as cas.war with an embedded server container and can be found in the build/libs directory.

CAS properties can be passed to the CAS web application as command-line arguments, when the application is launched:

java -jar build/libs/cas.war --sentry.enable-external-configuration="..."

The above example assumes that the CAS web application is packaged as cas.war with an embedded server container and can be found in the build/libs directory.

sentry.enable-metrics=

io.sentry.spring.boot.jakarta.SentryProperties.

_{How can I configure this property?}

Configuration properties can be included and activated using the following strategies.

Note

CAS properties can be specified using the Java configuration property syntax in any and all .properties files:

sentry.enable-metrics=...

CAS properties can be specified using the YAML syntax:

sentry: 
  enable-metrics: "..."

Note that YAML is very specific about structure and indentation. Be sure to verify the correctness of the final result with your YAML validator of choice.

CAS properties can be passed to the CAS web application as system properties, when the application is launched:

java -Dsentry.enable-metrics="..." -jar build/libs/cas.war

CAS properties can specified as system environment variables before the CAS web application is launched:

export SENTRY_ENABLE_METRICS="..."

java -jar build/libs/cas.war

The above example assumes that the CAS web application is packaged as cas.war with an embedded server container and can be found in the build/libs directory.

CAS properties can be passed to the CAS web application as command-line arguments, when the application is launched:

java -jar build/libs/cas.war --sentry.enable-metrics="..."

The above example assumes that the CAS web application is packaged as cas.war with an embedded server container and can be found in the build/libs directory.

sentry.enable-pretty-serialization-output=

io.sentry.spring.boot.jakarta.SentryProperties.

_{How can I configure this property?}

Configuration properties can be included and activated using the following strategies.

Note

CAS properties can be specified using the Java configuration property syntax in any and all .properties files:

sentry.enable-pretty-serialization-output=...

CAS properties can be specified using the YAML syntax:

sentry: 
  enable-pretty-serialization-output: "..."

Note that YAML is very specific about structure and indentation. Be sure to verify the correctness of the final result with your YAML validator of choice.

CAS properties can be passed to the CAS web application as system properties, when the application is launched:

java -Dsentry.enable-pretty-serialization-output="..." -jar build/libs/cas.war

CAS properties can specified as system environment variables before the CAS web application is launched:

export SENTRY_ENABLE_PRETTY_SERIALIZATION_OUTPUT="..."

java -jar build/libs/cas.war

The above example assumes that the CAS web application is packaged as cas.war with an embedded server container and can be found in the build/libs directory.

CAS properties can be passed to the CAS web application as command-line arguments, when the application is launched:

java -jar build/libs/cas.war --sentry.enable-pretty-serialization-output="..."

The above example assumes that the CAS web application is packaged as cas.war with an embedded server container and can be found in the build/libs directory.

sentry.enable-scope-persistence=

io.sentry.spring.boot.jakarta.SentryProperties.

_{How can I configure this property?}

Configuration properties can be included and activated using the following strategies.

Note

CAS properties can be specified using the Java configuration property syntax in any and all .properties files:

sentry.enable-scope-persistence=...

CAS properties can be specified using the YAML syntax:

sentry: 
  enable-scope-persistence: "..."

Note that YAML is very specific about structure and indentation. Be sure to verify the correctness of the final result with your YAML validator of choice.

CAS properties can be passed to the CAS web application as system properties, when the application is launched:

java -Dsentry.enable-scope-persistence="..." -jar build/libs/cas.war

CAS properties can specified as system environment variables before the CAS web application is launched:

export SENTRY_ENABLE_SCOPE_PERSISTENCE="..."

java -jar build/libs/cas.war

The above example assumes that the CAS web application is packaged as cas.war with an embedded server container and can be found in the build/libs directory.

CAS properties can be passed to the CAS web application as command-line arguments, when the application is launched:

java -jar build/libs/cas.war --sentry.enable-scope-persistence="..."

The above example assumes that the CAS web application is packaged as cas.war with an embedded server container and can be found in the build/libs directory.

sentry.enable-screen-tracking=

io.sentry.spring.boot.jakarta.SentryProperties.

_{How can I configure this property?}

Configuration properties can be included and activated using the following strategies.

Note

CAS properties can be specified using the Java configuration property syntax in any and all .properties files:

sentry.enable-screen-tracking=...

CAS properties can be specified using the YAML syntax:

sentry: 
  enable-screen-tracking: "..."

Note that YAML is very specific about structure and indentation. Be sure to verify the correctness of the final result with your YAML validator of choice.

CAS properties can be passed to the CAS web application as system properties, when the application is launched:

java -Dsentry.enable-screen-tracking="..." -jar build/libs/cas.war

CAS properties can specified as system environment variables before the CAS web application is launched:

export SENTRY_ENABLE_SCREEN_TRACKING="..."

java -jar build/libs/cas.war

The above example assumes that the CAS web application is packaged as cas.war with an embedded server container and can be found in the build/libs directory.

CAS properties can be passed to the CAS web application as command-line arguments, when the application is launched:

java -jar build/libs/cas.war --sentry.enable-screen-tracking="..."

The above example assumes that the CAS web application is packaged as cas.war with an embedded server container and can be found in the build/libs directory.

sentry.enable-shutdown-hook=

io.sentry.spring.boot.jakarta.SentryProperties.

_{How can I configure this property?}

Configuration properties can be included and activated using the following strategies.

Note

CAS properties can be specified using the Java configuration property syntax in any and all .properties files:

sentry.enable-shutdown-hook=...

CAS properties can be specified using the YAML syntax:

sentry: 
  enable-shutdown-hook: "..."

Note that YAML is very specific about structure and indentation. Be sure to verify the correctness of the final result with your YAML validator of choice.

CAS properties can be passed to the CAS web application as system properties, when the application is launched:

java -Dsentry.enable-shutdown-hook="..." -jar build/libs/cas.war

CAS properties can specified as system environment variables before the CAS web application is launched:

export SENTRY_ENABLE_SHUTDOWN_HOOK="..."

java -jar build/libs/cas.war

The above example assumes that the CAS web application is packaged as cas.war with an embedded server container and can be found in the build/libs directory.

CAS properties can be passed to the CAS web application as command-line arguments, when the application is launched:

java -jar build/libs/cas.war --sentry.enable-shutdown-hook="..."

The above example assumes that the CAS web application is packaged as cas.war with an embedded server container and can be found in the build/libs directory.

sentry.enable-span-local-metric-aggregation=

io.sentry.spring.boot.jakarta.SentryProperties.

_{How can I configure this property?}

Configuration properties can be included and activated using the following strategies.

Note

CAS properties can be specified using the Java configuration property syntax in any and all .properties files:

sentry.enable-span-local-metric-aggregation=...

CAS properties can be specified using the YAML syntax:

sentry: 
  enable-span-local-metric-aggregation: "..."

Note that YAML is very specific about structure and indentation. Be sure to verify the correctness of the final result with your YAML validator of choice.

CAS properties can be passed to the CAS web application as system properties, when the application is launched:

java -Dsentry.enable-span-local-metric-aggregation="..." -jar build/libs/cas.war

CAS properties can specified as system environment variables before the CAS web application is launched:

export SENTRY_ENABLE_SPAN_LOCAL_METRIC_AGGREGATION="..."

java -jar build/libs/cas.war

The above example assumes that the CAS web application is packaged as cas.war with an embedded server container and can be found in the build/libs directory.

CAS properties can be passed to the CAS web application as command-line arguments, when the application is launched:

java -jar build/libs/cas.war --sentry.enable-span-local-metric-aggregation="..."

The above example assumes that the CAS web application is packaged as cas.war with an embedded server container and can be found in the build/libs directory.

sentry.enable-spotlight=

io.sentry.spring.boot.jakarta.SentryProperties.

_{How can I configure this property?}

Configuration properties can be included and activated using the following strategies.

Note

CAS properties can be specified using the Java configuration property syntax in any and all .properties files:

sentry.enable-spotlight=...

CAS properties can be specified using the YAML syntax:

sentry: 
  enable-spotlight: "..."

Note that YAML is very specific about structure and indentation. Be sure to verify the correctness of the final result with your YAML validator of choice.

CAS properties can be passed to the CAS web application as system properties, when the application is launched:

java -Dsentry.enable-spotlight="..." -jar build/libs/cas.war

CAS properties can specified as system environment variables before the CAS web application is launched:

export SENTRY_ENABLE_SPOTLIGHT="..."

java -jar build/libs/cas.war

The above example assumes that the CAS web application is packaged as cas.war with an embedded server container and can be found in the build/libs directory.

CAS properties can be passed to the CAS web application as command-line arguments, when the application is launched:

java -jar build/libs/cas.war --sentry.enable-spotlight="..."

The above example assumes that the CAS web application is packaged as cas.war with an embedded server container and can be found in the build/libs directory.

sentry.enable-time-to-full-display-tracing=

io.sentry.spring.boot.jakarta.SentryProperties.

_{How can I configure this property?}

Configuration properties can be included and activated using the following strategies.

Note

CAS properties can be specified using the Java configuration property syntax in any and all .properties files:

sentry.enable-time-to-full-display-tracing=...

CAS properties can be specified using the YAML syntax:

sentry: 
  enable-time-to-full-display-tracing: "..."

Note that YAML is very specific about structure and indentation. Be sure to verify the correctness of the final result with your YAML validator of choice.

CAS properties can be passed to the CAS web application as system properties, when the application is launched:

java -Dsentry.enable-time-to-full-display-tracing="..." -jar build/libs/cas.war

CAS properties can specified as system environment variables before the CAS web application is launched:

export SENTRY_ENABLE_TIME_TO_FULL_DISPLAY_TRACING="..."

java -jar build/libs/cas.war

The above example assumes that the CAS web application is packaged as cas.war with an embedded server container and can be found in the build/libs directory.

CAS properties can be passed to the CAS web application as command-line arguments, when the application is launched:

java -jar build/libs/cas.war --sentry.enable-time-to-full-display-tracing="..."

The above example assumes that the CAS web application is packaged as cas.war with an embedded server container and can be found in the build/libs directory.

sentry.enable-tracing=

io.sentry.spring.boot.jakarta.SentryProperties.

_{How can I configure this property?}

Configuration properties can be included and activated using the following strategies.

Note

CAS properties can be specified using the Java configuration property syntax in any and all .properties files:

sentry.enable-tracing=...

CAS properties can be specified using the YAML syntax:

sentry: 
  enable-tracing: "..."

Note that YAML is very specific about structure and indentation. Be sure to verify the correctness of the final result with your YAML validator of choice.

CAS properties can be passed to the CAS web application as system properties, when the application is launched:

java -Dsentry.enable-tracing="..." -jar build/libs/cas.war

CAS properties can specified as system environment variables before the CAS web application is launched:

export SENTRY_ENABLE_TRACING="..."

java -jar build/libs/cas.war

The above example assumes that the CAS web application is packaged as cas.war with an embedded server container and can be found in the build/libs directory.

CAS properties can be passed to the CAS web application as command-line arguments, when the application is launched:

java -jar build/libs/cas.war --sentry.enable-tracing="..."

The above example assumes that the CAS web application is packaged as cas.war with an embedded server container and can be found in the build/libs directory.

Deprecation status is WARNINGwithout a replacement setting.

sentry.enable-uncaught-exception-handler=

io.sentry.spring.boot.jakarta.SentryProperties.

_{How can I configure this property?}

Configuration properties can be included and activated using the following strategies.

Note

CAS properties can be specified using the Java configuration property syntax in any and all .properties files:

sentry.enable-uncaught-exception-handler=...

CAS properties can be specified using the YAML syntax:

sentry: 
  enable-uncaught-exception-handler: "..."

Note that YAML is very specific about structure and indentation. Be sure to verify the correctness of the final result with your YAML validator of choice.

CAS properties can be passed to the CAS web application as system properties, when the application is launched:

java -Dsentry.enable-uncaught-exception-handler="..." -jar build/libs/cas.war

CAS properties can specified as system environment variables before the CAS web application is launched:

export SENTRY_ENABLE_UNCAUGHT_EXCEPTION_HANDLER="..."

java -jar build/libs/cas.war

The above example assumes that the CAS web application is packaged as cas.war with an embedded server container and can be found in the build/libs directory.

CAS properties can be passed to the CAS web application as command-line arguments, when the application is launched:

java -jar build/libs/cas.war --sentry.enable-uncaught-exception-handler="..."

The above example assumes that the CAS web application is packaged as cas.war with an embedded server container and can be found in the build/libs directory.

sentry.enable-user-interaction-breadcrumbs=

io.sentry.spring.boot.jakarta.SentryProperties.

_{How can I configure this property?}

Configuration properties can be included and activated using the following strategies.

Note

CAS properties can be specified using the Java configuration property syntax in any and all .properties files:

sentry.enable-user-interaction-breadcrumbs=...

CAS properties can be specified using the YAML syntax:

sentry: 
  enable-user-interaction-breadcrumbs: "..."

Note that YAML is very specific about structure and indentation. Be sure to verify the correctness of the final result with your YAML validator of choice.

CAS properties can be passed to the CAS web application as system properties, when the application is launched:

java -Dsentry.enable-user-interaction-breadcrumbs="..." -jar build/libs/cas.war

CAS properties can specified as system environment variables before the CAS web application is launched:

export SENTRY_ENABLE_USER_INTERACTION_BREADCRUMBS="..."

java -jar build/libs/cas.war

The above example assumes that the CAS web application is packaged as cas.war with an embedded server container and can be found in the build/libs directory.

CAS properties can be passed to the CAS web application as command-line arguments, when the application is launched:

java -jar build/libs/cas.war --sentry.enable-user-interaction-breadcrumbs="..."

The above example assumes that the CAS web application is packaged as cas.war with an embedded server container and can be found in the build/libs directory.

sentry.enable-user-interaction-tracing=

io.sentry.spring.boot.jakarta.SentryProperties.

_{How can I configure this property?}

Configuration properties can be included and activated using the following strategies.

Note

CAS properties can be specified using the Java configuration property syntax in any and all .properties files:

sentry.enable-user-interaction-tracing=...

CAS properties can be specified using the YAML syntax:

sentry: 
  enable-user-interaction-tracing: "..."

Note that YAML is very specific about structure and indentation. Be sure to verify the correctness of the final result with your YAML validator of choice.

CAS properties can be passed to the CAS web application as system properties, when the application is launched:

java -Dsentry.enable-user-interaction-tracing="..." -jar build/libs/cas.war

CAS properties can specified as system environment variables before the CAS web application is launched:

export SENTRY_ENABLE_USER_INTERACTION_TRACING="..."

java -jar build/libs/cas.war

The above example assumes that the CAS web application is packaged as cas.war with an embedded server container and can be found in the build/libs directory.

CAS properties can be passed to the CAS web application as command-line arguments, when the application is launched:

java -jar build/libs/cas.war --sentry.enable-user-interaction-tracing="..."

The above example assumes that the CAS web application is packaged as cas.war with an embedded server container and can be found in the build/libs directory.

sentry.enabled=

io.sentry.spring.boot.jakarta.SentryProperties.

_{How can I configure this property?}

Configuration properties can be included and activated using the following strategies.

Note

CAS properties can be specified using the Java configuration property syntax in any and all .properties files:

sentry.enabled=...

CAS properties can be specified using the YAML syntax:

sentry: 
  enabled: "..."

Note that YAML is very specific about structure and indentation. Be sure to verify the correctness of the final result with your YAML validator of choice.

CAS properties can be passed to the CAS web application as system properties, when the application is launched:

java -Dsentry.enabled="..." -jar build/libs/cas.war

CAS properties can specified as system environment variables before the CAS web application is launched:

export SENTRY_ENABLED="..."

java -jar build/libs/cas.war

The above example assumes that the CAS web application is packaged as cas.war with an embedded server container and can be found in the build/libs directory.

CAS properties can be passed to the CAS web application as command-line arguments, when the application is launched:

java -jar build/libs/cas.war --sentry.enabled="..."

The above example assumes that the CAS web application is packaged as cas.war with an embedded server container and can be found in the build/libs directory.

sentry.envelope-disk-cache=

io.sentry.spring.boot.jakarta.SentryProperties.

_{How can I configure this property?}

Configuration properties can be included and activated using the following strategies.

Note

CAS properties can be specified using the Java configuration property syntax in any and all .properties files:

sentry.envelope-disk-cache=...

CAS properties can be specified using the YAML syntax:

sentry: 
  envelope-disk-cache: "..."

Note that YAML is very specific about structure and indentation. Be sure to verify the correctness of the final result with your YAML validator of choice.

CAS properties can be passed to the CAS web application as system properties, when the application is launched:

java -Dsentry.envelope-disk-cache="..." -jar build/libs/cas.war

CAS properties can specified as system environment variables before the CAS web application is launched:

export SENTRY_ENVELOPE_DISK_CACHE="..."

java -jar build/libs/cas.war

The above example assumes that the CAS web application is packaged as cas.war with an embedded server container and can be found in the build/libs directory.

CAS properties can be passed to the CAS web application as command-line arguments, when the application is launched:

java -jar build/libs/cas.war --sentry.envelope-disk-cache="..."

The above example assumes that the CAS web application is packaged as cas.war with an embedded server container and can be found in the build/libs directory.

sentry.envelope-reader=

io.sentry.spring.boot.jakarta.SentryProperties.

_{How can I configure this property?}

Configuration properties can be included and activated using the following strategies.

Note

CAS properties can be specified using the Java configuration property syntax in any and all .properties files:

sentry.envelope-reader=...

CAS properties can be specified using the YAML syntax:

sentry: 
  envelope-reader: "..."

Note that YAML is very specific about structure and indentation. Be sure to verify the correctness of the final result with your YAML validator of choice.

CAS properties can be passed to the CAS web application as system properties, when the application is launched:

java -Dsentry.envelope-reader="..." -jar build/libs/cas.war

CAS properties can specified as system environment variables before the CAS web application is launched:

export SENTRY_ENVELOPE_READER="..."

java -jar build/libs/cas.war

The above example assumes that the CAS web application is packaged as cas.war with an embedded server container and can be found in the build/libs directory.

CAS properties can be passed to the CAS web application as command-line arguments, when the application is launched:

java -jar build/libs/cas.war --sentry.envelope-reader="..."

The above example assumes that the CAS web application is packaged as cas.war with an embedded server container and can be found in the build/libs directory.

sentry.environment=

io.sentry.spring.boot.jakarta.SentryProperties.

_{How can I configure this property?}

Configuration properties can be included and activated using the following strategies.

Note

CAS properties can be specified using the Java configuration property syntax in any and all .properties files:

sentry.environment=...

CAS properties can be specified using the YAML syntax:

sentry: 
  environment: "..."

Note that YAML is very specific about structure and indentation. Be sure to verify the correctness of the final result with your YAML validator of choice.

CAS properties can be passed to the CAS web application as system properties, when the application is launched:

java -Dsentry.environment="..." -jar build/libs/cas.war

CAS properties can specified as system environment variables before the CAS web application is launched:

export SENTRY_ENVIRONMENT="..."

java -jar build/libs/cas.war

The above example assumes that the CAS web application is packaged as cas.war with an embedded server container and can be found in the build/libs directory.

CAS properties can be passed to the CAS web application as command-line arguments, when the application is launched:

java -jar build/libs/cas.war --sentry.environment="..."

The above example assumes that the CAS web application is packaged as cas.war with an embedded server container and can be found in the build/libs directory.

sentry.event-processors=

io.sentry.spring.boot.jakarta.SentryProperties.

_{How can I configure this property?}

Configuration properties can be included and activated using the following strategies.

Note

CAS properties can be specified using the Java configuration property syntax in any and all .properties files:

sentry.event-processors=...

CAS properties can be specified using the YAML syntax:

sentry: 
  event-processors: "..."

Note that YAML is very specific about structure and indentation. Be sure to verify the correctness of the final result with your YAML validator of choice.

CAS properties can be passed to the CAS web application as system properties, when the application is launched:

java -Dsentry.event-processors="..." -jar build/libs/cas.war

CAS properties can specified as system environment variables before the CAS web application is launched:

export SENTRY_EVENT_PROCESSORS="..."

java -jar build/libs/cas.war

The above example assumes that the CAS web application is packaged as cas.war with an embedded server container and can be found in the build/libs directory.

CAS properties can be passed to the CAS web application as command-line arguments, when the application is launched:

java -jar build/libs/cas.war --sentry.event-processors="..."

The above example assumes that the CAS web application is packaged as cas.war with an embedded server container and can be found in the build/libs directory.

sentry.exception-resolver-order=1

Report all or only uncaught web exceptions.

io.sentry.spring.boot.jakarta.SentryProperties.

_{How can I configure this property?}

Configuration properties can be included and activated using the following strategies.

Note

CAS properties can be specified using the Java configuration property syntax in any and all .properties files:

sentry.exception-resolver-order=1

CAS properties can be specified using the YAML syntax:

sentry: 
  exception-resolver-order: "1"

Note that YAML is very specific about structure and indentation. Be sure to verify the correctness of the final result with your YAML validator of choice.

CAS properties can be passed to the CAS web application as system properties, when the application is launched:

java -Dsentry.exception-resolver-order="1" -jar build/libs/cas.war

CAS properties can specified as system environment variables before the CAS web application is launched:

export SENTRY_EXCEPTION_RESOLVER_ORDER="1"

java -jar build/libs/cas.war

The above example assumes that the CAS web application is packaged as cas.war with an embedded server container and can be found in the build/libs directory.

CAS properties can be passed to the CAS web application as command-line arguments, when the application is launched:

java -jar build/libs/cas.war --sentry.exception-resolver-order="1"

The above example assumes that the CAS web application is packaged as cas.war with an embedded server container and can be found in the build/libs directory.

sentry.executor-service=

io.sentry.spring.boot.jakarta.SentryProperties.

_{How can I configure this property?}

Configuration properties can be included and activated using the following strategies.

Note

CAS properties can be specified using the Java configuration property syntax in any and all .properties files:

sentry.executor-service=...

CAS properties can be specified using the YAML syntax:

sentry: 
  executor-service: "..."

Note that YAML is very specific about structure and indentation. Be sure to verify the correctness of the final result with your YAML validator of choice.

CAS properties can be passed to the CAS web application as system properties, when the application is launched:

java -Dsentry.executor-service="..." -jar build/libs/cas.war

CAS properties can specified as system environment variables before the CAS web application is launched:

export SENTRY_EXECUTOR_SERVICE="..."

java -jar build/libs/cas.war

The above example assumes that the CAS web application is packaged as cas.war with an embedded server container and can be found in the build/libs directory.

CAS properties can be passed to the CAS web application as command-line arguments, when the application is launched:

java -jar build/libs/cas.war --sentry.executor-service="..."

The above example assumes that the CAS web application is packaged as cas.war with an embedded server container and can be found in the build/libs directory.

sentry.flush-timeout-millis=

io.sentry.spring.boot.jakarta.SentryProperties.

_{How can I configure this property?}

Configuration properties can be included and activated using the following strategies.

Note

CAS properties can be specified using the Java configuration property syntax in any and all .properties files:

sentry.flush-timeout-millis=...

CAS properties can be specified using the YAML syntax:

sentry: 
  flush-timeout-millis: "..."

Note that YAML is very specific about structure and indentation. Be sure to verify the correctness of the final result with your YAML validator of choice.

CAS properties can be passed to the CAS web application as system properties, when the application is launched:

java -Dsentry.flush-timeout-millis="..." -jar build/libs/cas.war

CAS properties can specified as system environment variables before the CAS web application is launched:

export SENTRY_FLUSH_TIMEOUT_MILLIS="..."

java -jar build/libs/cas.war

The above example assumes that the CAS web application is packaged as cas.war with an embedded server container and can be found in the build/libs directory.

CAS properties can be passed to the CAS web application as command-line arguments, when the application is launched:

java -jar build/libs/cas.war --sentry.flush-timeout-millis="..."

The above example assumes that the CAS web application is packaged as cas.war with an embedded server container and can be found in the build/libs directory.

sentry.fully-displayed-reporter=

io.sentry.spring.boot.jakarta.SentryProperties.

_{How can I configure this property?}

Configuration properties can be included and activated using the following strategies.

Note

CAS properties can be specified using the Java configuration property syntax in any and all .properties files:

sentry.fully-displayed-reporter=...

CAS properties can be specified using the YAML syntax:

sentry: 
  fully-displayed-reporter: "..."

Note that YAML is very specific about structure and indentation. Be sure to verify the correctness of the final result with your YAML validator of choice.

CAS properties can be passed to the CAS web application as system properties, when the application is launched:

java -Dsentry.fully-displayed-reporter="..." -jar build/libs/cas.war

CAS properties can specified as system environment variables before the CAS web application is launched:

export SENTRY_FULLY_DISPLAYED_REPORTER="..."

java -jar build/libs/cas.war

The above example assumes that the CAS web application is packaged as cas.war with an embedded server container and can be found in the build/libs directory.

CAS properties can be passed to the CAS web application as command-line arguments, when the application is launched:

java -jar build/libs/cas.war --sentry.fully-displayed-reporter="..."

The above example assumes that the CAS web application is packaged as cas.war with an embedded server container and can be found in the build/libs directory.

sentry.gesture-target-locators=

io.sentry.spring.boot.jakarta.SentryProperties.

_{How can I configure this property?}

Configuration properties can be included and activated using the following strategies.

Note

CAS properties can be specified using the Java configuration property syntax in any and all .properties files:

sentry.gesture-target-locators=...

CAS properties can be specified using the YAML syntax:

sentry: 
  gesture-target-locators: "..."

Note that YAML is very specific about structure and indentation. Be sure to verify the correctness of the final result with your YAML validator of choice.

CAS properties can be passed to the CAS web application as system properties, when the application is launched:

java -Dsentry.gesture-target-locators="..." -jar build/libs/cas.war

CAS properties can specified as system environment variables before the CAS web application is launched:

export SENTRY_GESTURE_TARGET_LOCATORS="..."

java -jar build/libs/cas.war

The above example assumes that the CAS web application is packaged as cas.war with an embedded server container and can be found in the build/libs directory.

CAS properties can be passed to the CAS web application as command-line arguments, when the application is launched:

java -jar build/libs/cas.war --sentry.gesture-target-locators="..."

The above example assumes that the CAS web application is packaged as cas.war with an embedded server container and can be found in the build/libs directory.

sentry.graphql.ignored-error-types=

List of error types the Sentry Graphql integration should ignore.

io.sentry.spring.boot.jakarta.SentryProperties$Graphql.

_{How can I configure this property?}

Configuration properties can be included and activated using the following strategies.

Note

CAS properties can be specified using the Java configuration property syntax in any and all .properties files:

sentry.graphql.ignored-error-types=...

CAS properties can be specified using the YAML syntax:

sentry: 
  graphql: 
    ignored-error-types: "..."

Note that YAML is very specific about structure and indentation. Be sure to verify the correctness of the final result with your YAML validator of choice.

CAS properties can be passed to the CAS web application as system properties, when the application is launched:

java -Dsentry.graphql.ignored-error-types="..." -jar build/libs/cas.war

CAS properties can specified as system environment variables before the CAS web application is launched:

export SENTRY_GRAPHQL_IGNORED_ERROR_TYPES="..."

java -jar build/libs/cas.war

The above example assumes that the CAS web application is packaged as cas.war with an embedded server container and can be found in the build/libs directory.

CAS properties can be passed to the CAS web application as command-line arguments, when the application is launched:

java -jar build/libs/cas.war --sentry.graphql.ignored-error-types="..."

The above example assumes that the CAS web application is packaged as cas.war with an embedded server container and can be found in the build/libs directory.

sentry.idle-timeout=

io.sentry.spring.boot.jakarta.SentryProperties.

_{How can I configure this property?}

Configuration properties can be included and activated using the following strategies.

Note

CAS properties can be specified using the Java configuration property syntax in any and all .properties files:

sentry.idle-timeout=...

CAS properties can be specified using the YAML syntax:

sentry: 
  idle-timeout: "..."

Note that YAML is very specific about structure and indentation. Be sure to verify the correctness of the final result with your YAML validator of choice.

CAS properties can be passed to the CAS web application as system properties, when the application is launched:

java -Dsentry.idle-timeout="..." -jar build/libs/cas.war

CAS properties can specified as system environment variables before the CAS web application is launched:

export SENTRY_IDLE_TIMEOUT="..."

java -jar build/libs/cas.war

The above example assumes that the CAS web application is packaged as cas.war with an embedded server container and can be found in the build/libs directory.

CAS properties can be passed to the CAS web application as command-line arguments, when the application is launched:

java -jar build/libs/cas.war --sentry.idle-timeout="..."

The above example assumes that the CAS web application is packaged as cas.war with an embedded server container and can be found in the build/libs directory.

sentry.ignored-check-ins=

io.sentry.spring.boot.jakarta.SentryProperties.

_{How can I configure this property?}

Configuration properties can be included and activated using the following strategies.

Note

CAS properties can be specified using the Java configuration property syntax in any and all .properties files:

sentry.ignored-check-ins=...

CAS properties can be specified using the YAML syntax:

sentry: 
  ignored-check-ins: "..."

Note that YAML is very specific about structure and indentation. Be sure to verify the correctness of the final result with your YAML validator of choice.

CAS properties can be passed to the CAS web application as system properties, when the application is launched:

java -Dsentry.ignored-check-ins="..." -jar build/libs/cas.war

CAS properties can specified as system environment variables before the CAS web application is launched:

export SENTRY_IGNORED_CHECK_INS="..."

java -jar build/libs/cas.war

The above example assumes that the CAS web application is packaged as cas.war with an embedded server container and can be found in the build/libs directory.

CAS properties can be passed to the CAS web application as command-line arguments, when the application is launched:

java -jar build/libs/cas.war --sentry.ignored-check-ins="..."

The above example assumes that the CAS web application is packaged as cas.war with an embedded server container and can be found in the build/libs directory.

sentry.ignored-exceptions-for-type=

io.sentry.spring.boot.jakarta.SentryProperties.

_{How can I configure this property?}

Configuration properties can be included and activated using the following strategies.

Note

CAS properties can be specified using the Java configuration property syntax in any and all .properties files:

sentry.ignored-exceptions-for-type=...

CAS properties can be specified using the YAML syntax:

sentry: 
  ignored-exceptions-for-type: "..."

Note that YAML is very specific about structure and indentation. Be sure to verify the correctness of the final result with your YAML validator of choice.

CAS properties can be passed to the CAS web application as system properties, when the application is launched:

java -Dsentry.ignored-exceptions-for-type="..." -jar build/libs/cas.war

CAS properties can specified as system environment variables before the CAS web application is launched:

export SENTRY_IGNORED_EXCEPTIONS_FOR_TYPE="..."

java -jar build/libs/cas.war

The above example assumes that the CAS web application is packaged as cas.war with an embedded server container and can be found in the build/libs directory.

CAS properties can be passed to the CAS web application as command-line arguments, when the application is launched:

java -jar build/libs/cas.war --sentry.ignored-exceptions-for-type="..."

The above example assumes that the CAS web application is packaged as cas.war with an embedded server container and can be found in the build/libs directory.

sentry.in-app-excludes=

io.sentry.spring.boot.jakarta.SentryProperties.

_{How can I configure this property?}

Configuration properties can be included and activated using the following strategies.

Note

CAS properties can be specified using the Java configuration property syntax in any and all .properties files:

sentry.in-app-excludes=...

CAS properties can be specified using the YAML syntax:

sentry: 
  in-app-excludes: "..."

Note that YAML is very specific about structure and indentation. Be sure to verify the correctness of the final result with your YAML validator of choice.

CAS properties can be passed to the CAS web application as system properties, when the application is launched:

java -Dsentry.in-app-excludes="..." -jar build/libs/cas.war

CAS properties can specified as system environment variables before the CAS web application is launched:

export SENTRY_IN_APP_EXCLUDES="..."

java -jar build/libs/cas.war

The above example assumes that the CAS web application is packaged as cas.war with an embedded server container and can be found in the build/libs directory.

CAS properties can be passed to the CAS web application as command-line arguments, when the application is launched:

java -jar build/libs/cas.war --sentry.in-app-excludes="..."

The above example assumes that the CAS web application is packaged as cas.war with an embedded server container and can be found in the build/libs directory.

sentry.in-app-includes=

io.sentry.spring.boot.jakarta.SentryProperties.

_{How can I configure this property?}

Configuration properties can be included and activated using the following strategies.

Note

CAS properties can be specified using the Java configuration property syntax in any and all .properties files:

sentry.in-app-includes=...

CAS properties can be specified using the YAML syntax:

sentry: 
  in-app-includes: "..."

Note that YAML is very specific about structure and indentation. Be sure to verify the correctness of the final result with your YAML validator of choice.

CAS properties can be passed to the CAS web application as system properties, when the application is launched:

java -Dsentry.in-app-includes="..." -jar build/libs/cas.war

CAS properties can specified as system environment variables before the CAS web application is launched:

export SENTRY_IN_APP_INCLUDES="..."

java -jar build/libs/cas.war

The above example assumes that the CAS web application is packaged as cas.war with an embedded server container and can be found in the build/libs directory.

CAS properties can be passed to the CAS web application as command-line arguments, when the application is launched:

java -jar build/libs/cas.war --sentry.in-app-includes="..."

The above example assumes that the CAS web application is packaged as cas.war with an embedded server container and can be found in the build/libs directory.

sentry.instrumenter=

io.sentry.spring.boot.jakarta.SentryProperties.

_{How can I configure this property?}

Configuration properties can be included and activated using the following strategies.

Note

CAS properties can be specified using the Java configuration property syntax in any and all .properties files:

sentry.instrumenter=...

CAS properties can be specified using the YAML syntax:

sentry: 
  instrumenter: "..."

Note that YAML is very specific about structure and indentation. Be sure to verify the correctness of the final result with your YAML validator of choice.

CAS properties can be passed to the CAS web application as system properties, when the application is launched:

java -Dsentry.instrumenter="..." -jar build/libs/cas.war

CAS properties can specified as system environment variables before the CAS web application is launched:

export SENTRY_INSTRUMENTER="..."

java -jar build/libs/cas.war

The above example assumes that the CAS web application is packaged as cas.war with an embedded server container and can be found in the build/libs directory.

CAS properties can be passed to the CAS web application as command-line arguments, when the application is launched:

java -jar build/libs/cas.war --sentry.instrumenter="..."

The above example assumes that the CAS web application is packaged as cas.war with an embedded server container and can be found in the build/libs directory.

sentry.integrations=

io.sentry.spring.boot.jakarta.SentryProperties.

_{How can I configure this property?}

Configuration properties can be included and activated using the following strategies.

Note

CAS properties can be specified using the Java configuration property syntax in any and all .properties files:

sentry.integrations=...

CAS properties can be specified using the YAML syntax:

sentry: 
  integrations: "..."

Note that YAML is very specific about structure and indentation. Be sure to verify the correctness of the final result with your YAML validator of choice.

CAS properties can be passed to the CAS web application as system properties, when the application is launched:

java -Dsentry.integrations="..." -jar build/libs/cas.war

CAS properties can specified as system environment variables before the CAS web application is launched:

export SENTRY_INTEGRATIONS="..."

java -jar build/libs/cas.war

The above example assumes that the CAS web application is packaged as cas.war with an embedded server container and can be found in the build/libs directory.

CAS properties can be passed to the CAS web application as command-line arguments, when the application is launched:

java -jar build/libs/cas.war --sentry.integrations="..."

The above example assumes that the CAS web application is packaged as cas.war with an embedded server container and can be found in the build/libs directory.

sentry.logger=

io.sentry.spring.boot.jakarta.SentryProperties.

_{How can I configure this property?}

Configuration properties can be included and activated using the following strategies.

Note

CAS properties can be specified using the Java configuration property syntax in any and all .properties files:

sentry.logger=...

CAS properties can be specified using the YAML syntax:

sentry: 
  logger: "..."

Note that YAML is very specific about structure and indentation. Be sure to verify the correctness of the final result with your YAML validator of choice.

CAS properties can be passed to the CAS web application as system properties, when the application is launched:

java -Dsentry.logger="..." -jar build/libs/cas.war

CAS properties can specified as system environment variables before the CAS web application is launched:

export SENTRY_LOGGER="..."

java -jar build/libs/cas.war

The above example assumes that the CAS web application is packaged as cas.war with an embedded server container and can be found in the build/libs directory.

CAS properties can be passed to the CAS web application as command-line arguments, when the application is launched:

java -jar build/libs/cas.war --sentry.logger="..."

The above example assumes that the CAS web application is packaged as cas.war with an embedded server container and can be found in the build/libs directory.

sentry.logging.enabled=true

Enable/Disable logging auto-configuration.

io.sentry.spring.boot.jakarta.SentryProperties$Logging.

_{How can I configure this property?}

Configuration properties can be included and activated using the following strategies.

Note

CAS properties can be specified using the Java configuration property syntax in any and all .properties files:

sentry.logging.enabled=true

CAS properties can be specified using the YAML syntax:

sentry: 
  logging: 
    enabled: "true"

Note that YAML is very specific about structure and indentation. Be sure to verify the correctness of the final result with your YAML validator of choice.

CAS properties can be passed to the CAS web application as system properties, when the application is launched:

java -Dsentry.logging.enabled="true" -jar build/libs/cas.war

CAS properties can specified as system environment variables before the CAS web application is launched:

export SENTRY_LOGGING_ENABLED="true"

java -jar build/libs/cas.war

The above example assumes that the CAS web application is packaged as cas.war with an embedded server container and can be found in the build/libs directory.

CAS properties can be passed to the CAS web application as command-line arguments, when the application is launched:

java -jar build/libs/cas.war --sentry.logging.enabled="true"

The above example assumes that the CAS web application is packaged as cas.war with an embedded server container and can be found in the build/libs directory.

sentry.logging.loggers=

List of loggers the SentryAppender should be added to.

io.sentry.spring.boot.jakarta.SentryProperties$Logging.

_{How can I configure this property?}

Configuration properties can be included and activated using the following strategies.

Note

CAS properties can be specified using the Java configuration property syntax in any and all .properties files:

sentry.logging.loggers=...

CAS properties can be specified using the YAML syntax:

sentry: 
  logging: 
    loggers: "..."

Note that YAML is very specific about structure and indentation. Be sure to verify the correctness of the final result with your YAML validator of choice.

CAS properties can be passed to the CAS web application as system properties, when the application is launched:

java -Dsentry.logging.loggers="..." -jar build/libs/cas.war

CAS properties can specified as system environment variables before the CAS web application is launched:

export SENTRY_LOGGING_LOGGERS="..."

java -jar build/libs/cas.war

The above example assumes that the CAS web application is packaged as cas.war with an embedded server container and can be found in the build/libs directory.

CAS properties can be passed to the CAS web application as command-line arguments, when the application is launched:

java -jar build/libs/cas.war --sentry.logging.loggers="..."

The above example assumes that the CAS web application is packaged as cas.war with an embedded server container and can be found in the build/libs directory.

sentry.logging.minimum-breadcrumb-level=

Minimum logging level for recording breadcrumb.

io.sentry.spring.boot.jakarta.SentryProperties$Logging.

_{How can I configure this property?}

Configuration properties can be included and activated using the following strategies.

Note

CAS properties can be specified using the Java configuration property syntax in any and all .properties files:

sentry.logging.minimum-breadcrumb-level=...

CAS properties can be specified using the YAML syntax:

sentry: 
  logging: 
    minimum-breadcrumb-level: "..."

Note that YAML is very specific about structure and indentation. Be sure to verify the correctness of the final result with your YAML validator of choice.

CAS properties can be passed to the CAS web application as system properties, when the application is launched:

java -Dsentry.logging.minimum-breadcrumb-level="..." -jar build/libs/cas.war

CAS properties can specified as system environment variables before the CAS web application is launched:

export SENTRY_LOGGING_MINIMUM_BREADCRUMB_LEVEL="..."

java -jar build/libs/cas.war

The above example assumes that the CAS web application is packaged as cas.war with an embedded server container and can be found in the build/libs directory.

CAS properties can be passed to the CAS web application as command-line arguments, when the application is launched:

java -jar build/libs/cas.war --sentry.logging.minimum-breadcrumb-level="..."

The above example assumes that the CAS web application is packaged as cas.war with an embedded server container and can be found in the build/libs directory.

sentry.logging.minimum-event-level=

Minimum logging level for recording event.

io.sentry.spring.boot.jakarta.SentryProperties$Logging.

_{How can I configure this property?}

Configuration properties can be included and activated using the following strategies.

Note

CAS properties can be specified using the Java configuration property syntax in any and all .properties files:

sentry.logging.minimum-event-level=...

CAS properties can be specified using the YAML syntax:

sentry: 
  logging: 
    minimum-event-level: "..."

Note that YAML is very specific about structure and indentation. Be sure to verify the correctness of the final result with your YAML validator of choice.

CAS properties can be passed to the CAS web application as system properties, when the application is launched:

java -Dsentry.logging.minimum-event-level="..." -jar build/libs/cas.war

CAS properties can specified as system environment variables before the CAS web application is launched:

export SENTRY_LOGGING_MINIMUM_EVENT_LEVEL="..."

java -jar build/libs/cas.war

The above example assumes that the CAS web application is packaged as cas.war with an embedded server container and can be found in the build/libs directory.

CAS properties can be passed to the CAS web application as command-line arguments, when the application is launched:

java -jar build/libs/cas.war --sentry.logging.minimum-event-level="..."

The above example assumes that the CAS web application is packaged as cas.war with an embedded server container and can be found in the build/libs directory.

sentry.main-thread-checker=

io.sentry.spring.boot.jakarta.SentryProperties.

_{How can I configure this property?}

Configuration properties can be included and activated using the following strategies.

Note

CAS properties can be specified using the Java configuration property syntax in any and all .properties files:

sentry.main-thread-checker=...

CAS properties can be specified using the YAML syntax:

sentry: 
  main-thread-checker: "..."

Note that YAML is very specific about structure and indentation. Be sure to verify the correctness of the final result with your YAML validator of choice.

CAS properties can be passed to the CAS web application as system properties, when the application is launched:

java -Dsentry.main-thread-checker="..." -jar build/libs/cas.war

CAS properties can specified as system environment variables before the CAS web application is launched:

export SENTRY_MAIN_THREAD_CHECKER="..."

java -jar build/libs/cas.war

The above example assumes that the CAS web application is packaged as cas.war with an embedded server container and can be found in the build/libs directory.

CAS properties can be passed to the CAS web application as command-line arguments, when the application is launched:

java -jar build/libs/cas.war --sentry.main-thread-checker="..."

The above example assumes that the CAS web application is packaged as cas.war with an embedded server container and can be found in the build/libs directory.

sentry.max-attachment-size=

io.sentry.spring.boot.jakarta.SentryProperties.

_{How can I configure this property?}

Configuration properties can be included and activated using the following strategies.

Note

CAS properties can be specified using the Java configuration property syntax in any and all .properties files:

sentry.max-attachment-size=...

CAS properties can be specified using the YAML syntax:

sentry: 
  max-attachment-size: "..."

Note that YAML is very specific about structure and indentation. Be sure to verify the correctness of the final result with your YAML validator of choice.

CAS properties can be passed to the CAS web application as system properties, when the application is launched:

java -Dsentry.max-attachment-size="..." -jar build/libs/cas.war

CAS properties can specified as system environment variables before the CAS web application is launched:

export SENTRY_MAX_ATTACHMENT_SIZE="..."

java -jar build/libs/cas.war

The above example assumes that the CAS web application is packaged as cas.war with an embedded server container and can be found in the build/libs directory.

CAS properties can be passed to the CAS web application as command-line arguments, when the application is launched:

java -jar build/libs/cas.war --sentry.max-attachment-size="..."

The above example assumes that the CAS web application is packaged as cas.war with an embedded server container and can be found in the build/libs directory.

sentry.max-breadcrumbs=

io.sentry.spring.boot.jakarta.SentryProperties.

_{How can I configure this property?}

Configuration properties can be included and activated using the following strategies.

Note

CAS properties can be specified using the Java configuration property syntax in any and all .properties files:

sentry.max-breadcrumbs=...

CAS properties can be specified using the YAML syntax:

sentry: 
  max-breadcrumbs: "..."

Note that YAML is very specific about structure and indentation. Be sure to verify the correctness of the final result with your YAML validator of choice.

CAS properties can be passed to the CAS web application as system properties, when the application is launched:

java -Dsentry.max-breadcrumbs="..." -jar build/libs/cas.war

CAS properties can specified as system environment variables before the CAS web application is launched:

export SENTRY_MAX_BREADCRUMBS="..."

java -jar build/libs/cas.war

The above example assumes that the CAS web application is packaged as cas.war with an embedded server container and can be found in the build/libs directory.

CAS properties can be passed to the CAS web application as command-line arguments, when the application is launched:

java -jar build/libs/cas.war --sentry.max-breadcrumbs="..."

The above example assumes that the CAS web application is packaged as cas.war with an embedded server container and can be found in the build/libs directory.

sentry.max-cache-items=

io.sentry.spring.boot.jakarta.SentryProperties.

_{How can I configure this property?}

Configuration properties can be included and activated using the following strategies.

Note

CAS properties can be specified using the Java configuration property syntax in any and all .properties files:

sentry.max-cache-items=...

CAS properties can be specified using the YAML syntax:

sentry: 
  max-cache-items: "..."

Note that YAML is very specific about structure and indentation. Be sure to verify the correctness of the final result with your YAML validator of choice.

CAS properties can be passed to the CAS web application as system properties, when the application is launched:

java -Dsentry.max-cache-items="..." -jar build/libs/cas.war

CAS properties can specified as system environment variables before the CAS web application is launched:

export SENTRY_MAX_CACHE_ITEMS="..."

java -jar build/libs/cas.war

The above example assumes that the CAS web application is packaged as cas.war with an embedded server container and can be found in the build/libs directory.

CAS properties can be passed to the CAS web application as command-line arguments, when the application is launched:

java -jar build/libs/cas.war --sentry.max-cache-items="..."

The above example assumes that the CAS web application is packaged as cas.war with an embedded server container and can be found in the build/libs directory.

sentry.max-depth=

io.sentry.spring.boot.jakarta.SentryProperties.

_{How can I configure this property?}

Configuration properties can be included and activated using the following strategies.

Note

CAS properties can be specified using the Java configuration property syntax in any and all .properties files:

sentry.max-depth=...

CAS properties can be specified using the YAML syntax:

sentry: 
  max-depth: "..."

Note that YAML is very specific about structure and indentation. Be sure to verify the correctness of the final result with your YAML validator of choice.

CAS properties can be passed to the CAS web application as system properties, when the application is launched:

java -Dsentry.max-depth="..." -jar build/libs/cas.war

CAS properties can specified as system environment variables before the CAS web application is launched:

export SENTRY_MAX_DEPTH="..."

java -jar build/libs/cas.war

The above example assumes that the CAS web application is packaged as cas.war with an embedded server container and can be found in the build/libs directory.

CAS properties can be passed to the CAS web application as command-line arguments, when the application is launched:

java -jar build/libs/cas.war --sentry.max-depth="..."

The above example assumes that the CAS web application is packaged as cas.war with an embedded server container and can be found in the build/libs directory.

sentry.max-queue-size=

io.sentry.spring.boot.jakarta.SentryProperties.

_{How can I configure this property?}

Configuration properties can be included and activated using the following strategies.

Note

CAS properties can be specified using the Java configuration property syntax in any and all .properties files:

sentry.max-queue-size=...

CAS properties can be specified using the YAML syntax:

sentry: 
  max-queue-size: "..."

Note that YAML is very specific about structure and indentation. Be sure to verify the correctness of the final result with your YAML validator of choice.

CAS properties can be passed to the CAS web application as system properties, when the application is launched:

java -Dsentry.max-queue-size="..." -jar build/libs/cas.war

CAS properties can specified as system environment variables before the CAS web application is launched:

export SENTRY_MAX_QUEUE_SIZE="..."

java -jar build/libs/cas.war

The above example assumes that the CAS web application is packaged as cas.war with an embedded server container and can be found in the build/libs directory.

CAS properties can be passed to the CAS web application as command-line arguments, when the application is launched:

java -jar build/libs/cas.war --sentry.max-queue-size="..."

The above example assumes that the CAS web application is packaged as cas.war with an embedded server container and can be found in the build/libs directory.

sentry.max-request-body-size=

io.sentry.spring.boot.jakarta.SentryProperties.

_{How can I configure this property?}

Configuration properties can be included and activated using the following strategies.

Note

CAS properties can be specified using the Java configuration property syntax in any and all .properties files:

sentry.max-request-body-size=...

CAS properties can be specified using the YAML syntax:

sentry: 
  max-request-body-size: "..."

Note that YAML is very specific about structure and indentation. Be sure to verify the correctness of the final result with your YAML validator of choice.

CAS properties can be passed to the CAS web application as system properties, when the application is launched:

java -Dsentry.max-request-body-size="..." -jar build/libs/cas.war

CAS properties can specified as system environment variables before the CAS web application is launched:

export SENTRY_MAX_REQUEST_BODY_SIZE="..."

java -jar build/libs/cas.war

The above example assumes that the CAS web application is packaged as cas.war with an embedded server container and can be found in the build/libs directory.

CAS properties can be passed to the CAS web application as command-line arguments, when the application is launched:

java -jar build/libs/cas.war --sentry.max-request-body-size="..."

The above example assumes that the CAS web application is packaged as cas.war with an embedded server container and can be found in the build/libs directory.

sentry.max-spans=

io.sentry.spring.boot.jakarta.SentryProperties.

_{How can I configure this property?}

Configuration properties can be included and activated using the following strategies.

Note

CAS properties can be specified using the Java configuration property syntax in any and all .properties files:

sentry.max-spans=...

CAS properties can be specified using the YAML syntax:

sentry: 
  max-spans: "..."

Note that YAML is very specific about structure and indentation. Be sure to verify the correctness of the final result with your YAML validator of choice.

CAS properties can be passed to the CAS web application as system properties, when the application is launched:

java -Dsentry.max-spans="..." -jar build/libs/cas.war

CAS properties can specified as system environment variables before the CAS web application is launched:

export SENTRY_MAX_SPANS="..."

java -jar build/libs/cas.war

The above example assumes that the CAS web application is packaged as cas.war with an embedded server container and can be found in the build/libs directory.

CAS properties can be passed to the CAS web application as command-line arguments, when the application is launched:

java -jar build/libs/cas.war --sentry.max-spans="..."

The above example assumes that the CAS web application is packaged as cas.war with an embedded server container and can be found in the build/libs directory.

sentry.max-trace-file-size=

io.sentry.spring.boot.jakarta.SentryProperties.

_{How can I configure this property?}

Configuration properties can be included and activated using the following strategies.

Note

CAS properties can be specified using the Java configuration property syntax in any and all .properties files:

sentry.max-trace-file-size=...

CAS properties can be specified using the YAML syntax:

sentry: 
  max-trace-file-size: "..."

Note that YAML is very specific about structure and indentation. Be sure to verify the correctness of the final result with your YAML validator of choice.

CAS properties can be passed to the CAS web application as system properties, when the application is launched:

java -Dsentry.max-trace-file-size="..." -jar build/libs/cas.war

CAS properties can specified as system environment variables before the CAS web application is launched:

export SENTRY_MAX_TRACE_FILE_SIZE="..."

java -jar build/libs/cas.war

The above example assumes that the CAS web application is packaged as cas.war with an embedded server container and can be found in the build/libs directory.

CAS properties can be passed to the CAS web application as command-line arguments, when the application is launched:

java -jar build/libs/cas.war --sentry.max-trace-file-size="..."

The above example assumes that the CAS web application is packaged as cas.war with an embedded server container and can be found in the build/libs directory.

sentry.modules-loader=

io.sentry.spring.boot.jakarta.SentryProperties.

_{How can I configure this property?}

Configuration properties can be included and activated using the following strategies.

Note

CAS properties can be specified using the Java configuration property syntax in any and all .properties files:

sentry.modules-loader=...

CAS properties can be specified using the YAML syntax:

sentry: 
  modules-loader: "..."

Note that YAML is very specific about structure and indentation. Be sure to verify the correctness of the final result with your YAML validator of choice.

CAS properties can be passed to the CAS web application as system properties, when the application is launched:

java -Dsentry.modules-loader="..." -jar build/libs/cas.war

CAS properties can specified as system environment variables before the CAS web application is launched:

export SENTRY_MODULES_LOADER="..."

java -jar build/libs/cas.war

The above example assumes that the CAS web application is packaged as cas.war with an embedded server container and can be found in the build/libs directory.

CAS properties can be passed to the CAS web application as command-line arguments, when the application is launched:

java -jar build/libs/cas.war --sentry.modules-loader="..."

The above example assumes that the CAS web application is packaged as cas.war with an embedded server container and can be found in the build/libs directory.

sentry.options-observers=

io.sentry.spring.boot.jakarta.SentryProperties.

_{How can I configure this property?}

Configuration properties can be included and activated using the following strategies.

Note

CAS properties can be specified using the Java configuration property syntax in any and all .properties files:

sentry.options-observers=...

CAS properties can be specified using the YAML syntax:

sentry: 
  options-observers: "..."

Note that YAML is very specific about structure and indentation. Be sure to verify the correctness of the final result with your YAML validator of choice.

CAS properties can be passed to the CAS web application as system properties, when the application is launched:

java -Dsentry.options-observers="..." -jar build/libs/cas.war

CAS properties can specified as system environment variables before the CAS web application is launched:

export SENTRY_OPTIONS_OBSERVERS="..."

java -jar build/libs/cas.war

The above example assumes that the CAS web application is packaged as cas.war with an embedded server container and can be found in the build/libs directory.

CAS properties can be passed to the CAS web application as command-line arguments, when the application is launched:

java -jar build/libs/cas.war --sentry.options-observers="..."

The above example assumes that the CAS web application is packaged as cas.war with an embedded server container and can be found in the build/libs directory.

sentry.performance-collectors=

io.sentry.spring.boot.jakarta.SentryProperties.

_{How can I configure this property?}

Configuration properties can be included and activated using the following strategies.

Note

CAS properties can be specified using the Java configuration property syntax in any and all .properties files:

sentry.performance-collectors=...

CAS properties can be specified using the YAML syntax:

sentry: 
  performance-collectors: "..."

Note that YAML is very specific about structure and indentation. Be sure to verify the correctness of the final result with your YAML validator of choice.

CAS properties can be passed to the CAS web application as system properties, when the application is launched:

java -Dsentry.performance-collectors="..." -jar build/libs/cas.war

CAS properties can specified as system environment variables before the CAS web application is launched:

export SENTRY_PERFORMANCE_COLLECTORS="..."

java -jar build/libs/cas.war

The above example assumes that the CAS web application is packaged as cas.war with an embedded server container and can be found in the build/libs directory.

CAS properties can be passed to the CAS web application as command-line arguments, when the application is launched:

java -jar build/libs/cas.war --sentry.performance-collectors="..."

The above example assumes that the CAS web application is packaged as cas.war with an embedded server container and can be found in the build/libs directory.

sentry.print-uncaught-stack-trace=

io.sentry.spring.boot.jakarta.SentryProperties.

_{How can I configure this property?}

Configuration properties can be included and activated using the following strategies.

Note

CAS properties can be specified using the Java configuration property syntax in any and all .properties files:

sentry.print-uncaught-stack-trace=...

CAS properties can be specified using the YAML syntax:

sentry: 
  print-uncaught-stack-trace: "..."

Note that YAML is very specific about structure and indentation. Be sure to verify the correctness of the final result with your YAML validator of choice.

CAS properties can be passed to the CAS web application as system properties, when the application is launched:

java -Dsentry.print-uncaught-stack-trace="..." -jar build/libs/cas.war

CAS properties can specified as system environment variables before the CAS web application is launched:

export SENTRY_PRINT_UNCAUGHT_STACK_TRACE="..."

java -jar build/libs/cas.war

The above example assumes that the CAS web application is packaged as cas.war with an embedded server container and can be found in the build/libs directory.

CAS properties can be passed to the CAS web application as command-line arguments, when the application is launched:

java -jar build/libs/cas.war --sentry.print-uncaught-stack-trace="..."

The above example assumes that the CAS web application is packaged as cas.war with an embedded server container and can be found in the build/libs directory.

sentry.profiles-sample-rate=

io.sentry.spring.boot.jakarta.SentryProperties.

_{How can I configure this property?}

Configuration properties can be included and activated using the following strategies.

Note

CAS properties can be specified using the Java configuration property syntax in any and all .properties files:

sentry.profiles-sample-rate=...

CAS properties can be specified using the YAML syntax:

sentry: 
  profiles-sample-rate: "..."

Note that YAML is very specific about structure and indentation. Be sure to verify the correctness of the final result with your YAML validator of choice.

CAS properties can be passed to the CAS web application as system properties, when the application is launched:

java -Dsentry.profiles-sample-rate="..." -jar build/libs/cas.war

CAS properties can specified as system environment variables before the CAS web application is launched:

export SENTRY_PROFILES_SAMPLE_RATE="..."

java -jar build/libs/cas.war

The above example assumes that the CAS web application is packaged as cas.war with an embedded server container and can be found in the build/libs directory.

CAS properties can be passed to the CAS web application as command-line arguments, when the application is launched:

java -jar build/libs/cas.war --sentry.profiles-sample-rate="..."

The above example assumes that the CAS web application is packaged as cas.war with an embedded server container and can be found in the build/libs directory.

sentry.profiling-enabled=

io.sentry.spring.boot.jakarta.SentryProperties.

_{How can I configure this property?}

Configuration properties can be included and activated using the following strategies.

Note

CAS properties can be specified using the Java configuration property syntax in any and all .properties files:

sentry.profiling-enabled=...

CAS properties can be specified using the YAML syntax:

sentry: 
  profiling-enabled: "..."

Note that YAML is very specific about structure and indentation. Be sure to verify the correctness of the final result with your YAML validator of choice.

CAS properties can be passed to the CAS web application as system properties, when the application is launched:

java -Dsentry.profiling-enabled="..." -jar build/libs/cas.war

CAS properties can specified as system environment variables before the CAS web application is launched:

export SENTRY_PROFILING_ENABLED="..."

java -jar build/libs/cas.war

The above example assumes that the CAS web application is packaged as cas.war with an embedded server container and can be found in the build/libs directory.

CAS properties can be passed to the CAS web application as command-line arguments, when the application is launched:

java -jar build/libs/cas.war --sentry.profiling-enabled="..."

The above example assumes that the CAS web application is packaged as cas.war with an embedded server container and can be found in the build/libs directory.

Deprecation status is WARNINGwithout a replacement setting.

sentry.profiling-traces-hz=

io.sentry.spring.boot.jakarta.SentryProperties.

_{How can I configure this property?}

Configuration properties can be included and activated using the following strategies.

Note

CAS properties can be specified using the Java configuration property syntax in any and all .properties files:

sentry.profiling-traces-hz=...

CAS properties can be specified using the YAML syntax:

sentry: 
  profiling-traces-hz: "..."

Note that YAML is very specific about structure and indentation. Be sure to verify the correctness of the final result with your YAML validator of choice.

CAS properties can be passed to the CAS web application as system properties, when the application is launched:

java -Dsentry.profiling-traces-hz="..." -jar build/libs/cas.war

CAS properties can specified as system environment variables before the CAS web application is launched:

export SENTRY_PROFILING_TRACES_HZ="..."

java -jar build/libs/cas.war

The above example assumes that the CAS web application is packaged as cas.war with an embedded server container and can be found in the build/libs directory.

CAS properties can be passed to the CAS web application as command-line arguments, when the application is launched:

java -jar build/libs/cas.war --sentry.profiling-traces-hz="..."

The above example assumes that the CAS web application is packaged as cas.war with an embedded server container and can be found in the build/libs directory.

sentry.proguard-uuid=

io.sentry.spring.boot.jakarta.SentryProperties.

_{How can I configure this property?}

Configuration properties can be included and activated using the following strategies.

Note

CAS properties can be specified using the Java configuration property syntax in any and all .properties files:

sentry.proguard-uuid=...

CAS properties can be specified using the YAML syntax:

sentry: 
  proguard-uuid: "..."

Note that YAML is very specific about structure and indentation. Be sure to verify the correctness of the final result with your YAML validator of choice.

CAS properties can be passed to the CAS web application as system properties, when the application is launched:

java -Dsentry.proguard-uuid="..." -jar build/libs/cas.war

CAS properties can specified as system environment variables before the CAS web application is launched:

export SENTRY_PROGUARD_UUID="..."

java -jar build/libs/cas.war

The above example assumes that the CAS web application is packaged as cas.war with an embedded server container and can be found in the build/libs directory.

CAS properties can be passed to the CAS web application as command-line arguments, when the application is launched:

java -jar build/libs/cas.war --sentry.proguard-uuid="..."

The above example assumes that the CAS web application is packaged as cas.war with an embedded server container and can be found in the build/libs directory.

sentry.proxy.host=

io.sentry.SentryOptions$Proxy.

_{How can I configure this property?}

Configuration properties can be included and activated using the following strategies.

Note

CAS properties can be specified using the Java configuration property syntax in any and all .properties files:

sentry.proxy.host=...

CAS properties can be specified using the YAML syntax:

sentry: 
  proxy: 
    host: "..."

Note that YAML is very specific about structure and indentation. Be sure to verify the correctness of the final result with your YAML validator of choice.

CAS properties can be passed to the CAS web application as system properties, when the application is launched:

java -Dsentry.proxy.host="..." -jar build/libs/cas.war

CAS properties can specified as system environment variables before the CAS web application is launched:

export SENTRY_PROXY_HOST="..."

java -jar build/libs/cas.war

The above example assumes that the CAS web application is packaged as cas.war with an embedded server container and can be found in the build/libs directory.

CAS properties can be passed to the CAS web application as command-line arguments, when the application is launched:

java -jar build/libs/cas.war --sentry.proxy.host="..."

The above example assumes that the CAS web application is packaged as cas.war with an embedded server container and can be found in the build/libs directory.

sentry.proxy.pass=

io.sentry.SentryOptions$Proxy.

_{How can I configure this property?}

Configuration properties can be included and activated using the following strategies.

Note

CAS properties can be specified using the Java configuration property syntax in any and all .properties files:

sentry.proxy.pass=...

CAS properties can be specified using the YAML syntax:

sentry: 
  proxy: 
    pass: "..."

Note that YAML is very specific about structure and indentation. Be sure to verify the correctness of the final result with your YAML validator of choice.

CAS properties can be passed to the CAS web application as system properties, when the application is launched:

java -Dsentry.proxy.pass="..." -jar build/libs/cas.war

CAS properties can specified as system environment variables before the CAS web application is launched:

export SENTRY_PROXY_PASS="..."

java -jar build/libs/cas.war

The above example assumes that the CAS web application is packaged as cas.war with an embedded server container and can be found in the build/libs directory.

CAS properties can be passed to the CAS web application as command-line arguments, when the application is launched:

java -jar build/libs/cas.war --sentry.proxy.pass="..."

The above example assumes that the CAS web application is packaged as cas.war with an embedded server container and can be found in the build/libs directory.

sentry.proxy.port=

io.sentry.SentryOptions$Proxy.

_{How can I configure this property?}

Configuration properties can be included and activated using the following strategies.

Note

CAS properties can be specified using the Java configuration property syntax in any and all .properties files:

sentry.proxy.port=...

CAS properties can be specified using the YAML syntax:

sentry: 
  proxy: 
    port: "..."

Note that YAML is very specific about structure and indentation. Be sure to verify the correctness of the final result with your YAML validator of choice.

CAS properties can be passed to the CAS web application as system properties, when the application is launched:

java -Dsentry.proxy.port="..." -jar build/libs/cas.war

CAS properties can specified as system environment variables before the CAS web application is launched:

export SENTRY_PROXY_PORT="..."

java -jar build/libs/cas.war

The above example assumes that the CAS web application is packaged as cas.war with an embedded server container and can be found in the build/libs directory.

CAS properties can be passed to the CAS web application as command-line arguments, when the application is launched:

java -jar build/libs/cas.war --sentry.proxy.port="..."

The above example assumes that the CAS web application is packaged as cas.war with an embedded server container and can be found in the build/libs directory.

sentry.proxy.type=

io.sentry.SentryOptions$Proxy.

_{How can I configure this property?}

Configuration properties can be included and activated using the following strategies.

Note

CAS properties can be specified using the Java configuration property syntax in any and all .properties files:

sentry.proxy.type=...

CAS properties can be specified using the YAML syntax:

sentry: 
  proxy: 
    type: "..."

Note that YAML is very specific about structure and indentation. Be sure to verify the correctness of the final result with your YAML validator of choice.

CAS properties can be passed to the CAS web application as system properties, when the application is launched:

java -Dsentry.proxy.type="..." -jar build/libs/cas.war

CAS properties can specified as system environment variables before the CAS web application is launched:

export SENTRY_PROXY_TYPE="..."

java -jar build/libs/cas.war

The above example assumes that the CAS web application is packaged as cas.war with an embedded server container and can be found in the build/libs directory.

CAS properties can be passed to the CAS web application as command-line arguments, when the application is launched:

java -jar build/libs/cas.war --sentry.proxy.type="..."

The above example assumes that the CAS web application is packaged as cas.war with an embedded server container and can be found in the build/libs directory.

sentry.proxy.user=

io.sentry.SentryOptions$Proxy.

_{How can I configure this property?}

Configuration properties can be included and activated using the following strategies.

Note

CAS properties can be specified using the Java configuration property syntax in any and all .properties files:

sentry.proxy.user=...

CAS properties can be specified using the YAML syntax:

sentry: 
  proxy: 
    user: "..."

Note that YAML is very specific about structure and indentation. Be sure to verify the correctness of the final result with your YAML validator of choice.

CAS properties can be passed to the CAS web application as system properties, when the application is launched:

java -Dsentry.proxy.user="..." -jar build/libs/cas.war

CAS properties can specified as system environment variables before the CAS web application is launched:

export SENTRY_PROXY_USER="..."

java -jar build/libs/cas.war

The above example assumes that the CAS web application is packaged as cas.war with an embedded server container and can be found in the build/libs directory.

CAS properties can be passed to the CAS web application as command-line arguments, when the application is launched:

java -jar build/libs/cas.war --sentry.proxy.user="..."

The above example assumes that the CAS web application is packaged as cas.war with an embedded server container and can be found in the build/libs directory.

sentry.reactive.thread-local-accessor-enabled=true

Enable/Disable usage of io.micrometer.context.ThreadLocalAccessor for Hub propagation

io.sentry.spring.boot.jakarta.SentryProperties$Reactive.

_{How can I configure this property?}

Configuration properties can be included and activated using the following strategies.

Note

CAS properties can be specified using the Java configuration property syntax in any and all .properties files:

sentry.reactive.thread-local-accessor-enabled=true

CAS properties can be specified using the YAML syntax:

sentry: 
  reactive: 
    thread-local-accessor-enabled: "true"

Note that YAML is very specific about structure and indentation. Be sure to verify the correctness of the final result with your YAML validator of choice.

CAS properties can be passed to the CAS web application as system properties, when the application is launched:

java -Dsentry.reactive.thread-local-accessor-enabled="true" -jar build/libs/cas.war

CAS properties can specified as system environment variables before the CAS web application is launched:

export SENTRY_REACTIVE_THREAD_LOCAL_ACCESSOR_ENABLED="true"

java -jar build/libs/cas.war

The above example assumes that the CAS web application is packaged as cas.war with an embedded server container and can be found in the build/libs directory.

CAS properties can be passed to the CAS web application as command-line arguments, when the application is launched:

java -jar build/libs/cas.war --sentry.reactive.thread-local-accessor-enabled="true"

The above example assumes that the CAS web application is packaged as cas.war with an embedded server container and can be found in the build/libs directory.

sentry.read-timeout-millis=

io.sentry.spring.boot.jakarta.SentryProperties.

_{How can I configure this property?}

Configuration properties can be included and activated using the following strategies.

Note

CAS properties can be specified using the Java configuration property syntax in any and all .properties files:

sentry.read-timeout-millis=...

CAS properties can be specified using the YAML syntax:

sentry: 
  read-timeout-millis: "..."

Note that YAML is very specific about structure and indentation. Be sure to verify the correctness of the final result with your YAML validator of choice.

CAS properties can be passed to the CAS web application as system properties, when the application is launched:

java -Dsentry.read-timeout-millis="..." -jar build/libs/cas.war

CAS properties can specified as system environment variables before the CAS web application is launched:

export SENTRY_READ_TIMEOUT_MILLIS="..."

java -jar build/libs/cas.war

The above example assumes that the CAS web application is packaged as cas.war with an embedded server container and can be found in the build/libs directory.

CAS properties can be passed to the CAS web application as command-line arguments, when the application is launched:

java -jar build/libs/cas.war --sentry.read-timeout-millis="..."

The above example assumes that the CAS web application is packaged as cas.war with an embedded server container and can be found in the build/libs directory.

sentry.release=

io.sentry.spring.boot.jakarta.SentryProperties.

_{How can I configure this property?}

Configuration properties can be included and activated using the following strategies.

Note

CAS properties can be specified using the Java configuration property syntax in any and all .properties files:

sentry.release=...

CAS properties can be specified using the YAML syntax:

sentry: 
  release: "..."

Note that YAML is very specific about structure and indentation. Be sure to verify the correctness of the final result with your YAML validator of choice.

CAS properties can be passed to the CAS web application as system properties, when the application is launched:

java -Dsentry.release="..." -jar build/libs/cas.war

CAS properties can specified as system environment variables before the CAS web application is launched:

export SENTRY_RELEASE="..."

java -jar build/libs/cas.war

The above example assumes that the CAS web application is packaged as cas.war with an embedded server container and can be found in the build/libs directory.

CAS properties can be passed to the CAS web application as command-line arguments, when the application is launched:

java -jar build/libs/cas.war --sentry.release="..."

The above example assumes that the CAS web application is packaged as cas.war with an embedded server container and can be found in the build/libs directory.

sentry.replay-controller=

io.sentry.spring.boot.jakarta.SentryProperties.

_{How can I configure this property?}

Configuration properties can be included and activated using the following strategies.

Note

CAS properties can be specified using the Java configuration property syntax in any and all .properties files:

sentry.replay-controller=...

CAS properties can be specified using the YAML syntax:

sentry: 
  replay-controller: "..."

Note that YAML is very specific about structure and indentation. Be sure to verify the correctness of the final result with your YAML validator of choice.

CAS properties can be passed to the CAS web application as system properties, when the application is launched:

java -Dsentry.replay-controller="..." -jar build/libs/cas.war

CAS properties can specified as system environment variables before the CAS web application is launched:

export SENTRY_REPLAY_CONTROLLER="..."

java -jar build/libs/cas.war

The above example assumes that the CAS web application is packaged as cas.war with an embedded server container and can be found in the build/libs directory.

CAS properties can be passed to the CAS web application as command-line arguments, when the application is launched:

java -jar build/libs/cas.war --sentry.replay-controller="..."

The above example assumes that the CAS web application is packaged as cas.war with an embedded server container and can be found in the build/libs directory.

sentry.sample-rate=

io.sentry.spring.boot.jakarta.SentryProperties.

_{How can I configure this property?}

Configuration properties can be included and activated using the following strategies.

Note

CAS properties can be specified using the Java configuration property syntax in any and all .properties files:

sentry.sample-rate=...

CAS properties can be specified using the YAML syntax:

sentry: 
  sample-rate: "..."

Note that YAML is very specific about structure and indentation. Be sure to verify the correctness of the final result with your YAML validator of choice.

CAS properties can be passed to the CAS web application as system properties, when the application is launched:

java -Dsentry.sample-rate="..." -jar build/libs/cas.war

CAS properties can specified as system environment variables before the CAS web application is launched:

export SENTRY_SAMPLE_RATE="..."

java -jar build/libs/cas.war

The above example assumes that the CAS web application is packaged as cas.war with an embedded server container and can be found in the build/libs directory.

CAS properties can be passed to the CAS web application as command-line arguments, when the application is launched:

java -jar build/libs/cas.war --sentry.sample-rate="..."

The above example assumes that the CAS web application is packaged as cas.war with an embedded server container and can be found in the build/libs directory.

sentry.scope-observers=

io.sentry.spring.boot.jakarta.SentryProperties.

_{How can I configure this property?}

Configuration properties can be included and activated using the following strategies.

Note

CAS properties can be specified using the Java configuration property syntax in any and all .properties files:

sentry.scope-observers=...

CAS properties can be specified using the YAML syntax:

sentry: 
  scope-observers: "..."

Note that YAML is very specific about structure and indentation. Be sure to verify the correctness of the final result with your YAML validator of choice.

CAS properties can be passed to the CAS web application as system properties, when the application is launched:

java -Dsentry.scope-observers="..." -jar build/libs/cas.war

CAS properties can specified as system environment variables before the CAS web application is launched:

export SENTRY_SCOPE_OBSERVERS="..."

java -jar build/libs/cas.war

The above example assumes that the CAS web application is packaged as cas.war with an embedded server container and can be found in the build/libs directory.

CAS properties can be passed to the CAS web application as command-line arguments, when the application is launched:

java -jar build/libs/cas.war --sentry.scope-observers="..."

The above example assumes that the CAS web application is packaged as cas.war with an embedded server container and can be found in the build/libs directory.

sentry.sdk-version=

io.sentry.spring.boot.jakarta.SentryProperties.

_{How can I configure this property?}

Configuration properties can be included and activated using the following strategies.

Note

CAS properties can be specified using the Java configuration property syntax in any and all .properties files:

sentry.sdk-version=...

CAS properties can be specified using the YAML syntax:

sentry: 
  sdk-version: "..."

Note that YAML is very specific about structure and indentation. Be sure to verify the correctness of the final result with your YAML validator of choice.

CAS properties can be passed to the CAS web application as system properties, when the application is launched:

java -Dsentry.sdk-version="..." -jar build/libs/cas.war

CAS properties can specified as system environment variables before the CAS web application is launched:

export SENTRY_SDK_VERSION="..."

java -jar build/libs/cas.war

The above example assumes that the CAS web application is packaged as cas.war with an embedded server container and can be found in the build/libs directory.

CAS properties can be passed to the CAS web application as command-line arguments, when the application is launched:

java -jar build/libs/cas.war --sentry.sdk-version="..."

The above example assumes that the CAS web application is packaged as cas.war with an embedded server container and can be found in the build/libs directory.

sentry.send-client-reports=

io.sentry.spring.boot.jakarta.SentryProperties.

_{How can I configure this property?}

Configuration properties can be included and activated using the following strategies.

Note

CAS properties can be specified using the Java configuration property syntax in any and all .properties files:

sentry.send-client-reports=...

CAS properties can be specified using the YAML syntax:

sentry: 
  send-client-reports: "..."

Note that YAML is very specific about structure and indentation. Be sure to verify the correctness of the final result with your YAML validator of choice.

CAS properties can be passed to the CAS web application as system properties, when the application is launched:

java -Dsentry.send-client-reports="..." -jar build/libs/cas.war

CAS properties can specified as system environment variables before the CAS web application is launched:

export SENTRY_SEND_CLIENT_REPORTS="..."

java -jar build/libs/cas.war

The above example assumes that the CAS web application is packaged as cas.war with an embedded server container and can be found in the build/libs directory.

CAS properties can be passed to the CAS web application as command-line arguments, when the application is launched:

java -jar build/libs/cas.war --sentry.send-client-reports="..."

The above example assumes that the CAS web application is packaged as cas.war with an embedded server container and can be found in the build/libs directory.

sentry.send-default-pii=

io.sentry.spring.boot.jakarta.SentryProperties.

_{How can I configure this property?}

Configuration properties can be included and activated using the following strategies.

Note

CAS properties can be specified using the Java configuration property syntax in any and all .properties files:

sentry.send-default-pii=...

CAS properties can be specified using the YAML syntax:

sentry: 
  send-default-pii: "..."

Note that YAML is very specific about structure and indentation. Be sure to verify the correctness of the final result with your YAML validator of choice.

CAS properties can be passed to the CAS web application as system properties, when the application is launched:

java -Dsentry.send-default-pii="..." -jar build/libs/cas.war

CAS properties can specified as system environment variables before the CAS web application is launched:

export SENTRY_SEND_DEFAULT_PII="..."

java -jar build/libs/cas.war

The above example assumes that the CAS web application is packaged as cas.war with an embedded server container and can be found in the build/libs directory.

CAS properties can be passed to the CAS web application as command-line arguments, when the application is launched:

java -jar build/libs/cas.war --sentry.send-default-pii="..."

The above example assumes that the CAS web application is packaged as cas.war with an embedded server container and can be found in the build/libs directory.

sentry.send-modules=

io.sentry.spring.boot.jakarta.SentryProperties.

_{How can I configure this property?}

Configuration properties can be included and activated using the following strategies.

Note

CAS properties can be specified using the Java configuration property syntax in any and all .properties files:

sentry.send-modules=...

CAS properties can be specified using the YAML syntax:

sentry: 
  send-modules: "..."

Note that YAML is very specific about structure and indentation. Be sure to verify the correctness of the final result with your YAML validator of choice.

CAS properties can be passed to the CAS web application as system properties, when the application is launched:

java -Dsentry.send-modules="..." -jar build/libs/cas.war

CAS properties can specified as system environment variables before the CAS web application is launched:

export SENTRY_SEND_MODULES="..."

java -jar build/libs/cas.war

The above example assumes that the CAS web application is packaged as cas.war with an embedded server container and can be found in the build/libs directory.

CAS properties can be passed to the CAS web application as command-line arguments, when the application is launched:

java -jar build/libs/cas.war --sentry.send-modules="..."

The above example assumes that the CAS web application is packaged as cas.war with an embedded server container and can be found in the build/libs directory.

sentry.sentry-client-name=

io.sentry.spring.boot.jakarta.SentryProperties.

_{How can I configure this property?}

Configuration properties can be included and activated using the following strategies.

Note

CAS properties can be specified using the Java configuration property syntax in any and all .properties files:

sentry.sentry-client-name=...

CAS properties can be specified using the YAML syntax:

sentry: 
  sentry-client-name: "..."

Note that YAML is very specific about structure and indentation. Be sure to verify the correctness of the final result with your YAML validator of choice.

CAS properties can be passed to the CAS web application as system properties, when the application is launched:

java -Dsentry.sentry-client-name="..." -jar build/libs/cas.war

CAS properties can specified as system environment variables before the CAS web application is launched:

export SENTRY_SENTRY_CLIENT_NAME="..."

java -jar build/libs/cas.war

The above example assumes that the CAS web application is packaged as cas.war with an embedded server container and can be found in the build/libs directory.

CAS properties can be passed to the CAS web application as command-line arguments, when the application is launched:

java -jar build/libs/cas.war --sentry.sentry-client-name="..."

The above example assumes that the CAS web application is packaged as cas.war with an embedded server container and can be found in the build/libs directory.

sentry.serializer=

io.sentry.spring.boot.jakarta.SentryProperties.

_{How can I configure this property?}

Configuration properties can be included and activated using the following strategies.

Note

CAS properties can be specified using the Java configuration property syntax in any and all .properties files:

sentry.serializer=...

CAS properties can be specified using the YAML syntax:

sentry: 
  serializer: "..."

Note that YAML is very specific about structure and indentation. Be sure to verify the correctness of the final result with your YAML validator of choice.

CAS properties can be passed to the CAS web application as system properties, when the application is launched:

java -Dsentry.serializer="..." -jar build/libs/cas.war

CAS properties can specified as system environment variables before the CAS web application is launched:

export SENTRY_SERIALIZER="..."

java -jar build/libs/cas.war

The above example assumes that the CAS web application is packaged as cas.war with an embedded server container and can be found in the build/libs directory.

CAS properties can be passed to the CAS web application as command-line arguments, when the application is launched:

java -jar build/libs/cas.war --sentry.serializer="..."

The above example assumes that the CAS web application is packaged as cas.war with an embedded server container and can be found in the build/libs directory.

sentry.server-name=

io.sentry.spring.boot.jakarta.SentryProperties.

_{How can I configure this property?}

Configuration properties can be included and activated using the following strategies.

Note

CAS properties can be specified using the Java configuration property syntax in any and all .properties files:

sentry.server-name=...

CAS properties can be specified using the YAML syntax:

sentry: 
  server-name: "..."

Note that YAML is very specific about structure and indentation. Be sure to verify the correctness of the final result with your YAML validator of choice.

CAS properties can be passed to the CAS web application as system properties, when the application is launched:

java -Dsentry.server-name="..." -jar build/libs/cas.war

CAS properties can specified as system environment variables before the CAS web application is launched:

export SENTRY_SERVER_NAME="..."

java -jar build/libs/cas.war

The above example assumes that the CAS web application is packaged as cas.war with an embedded server container and can be found in the build/libs directory.

CAS properties can be passed to the CAS web application as command-line arguments, when the application is launched:

java -jar build/libs/cas.war --sentry.server-name="..."

The above example assumes that the CAS web application is packaged as cas.war with an embedded server container and can be found in the build/libs directory.

sentry.session-flush-timeout-millis=

io.sentry.spring.boot.jakarta.SentryProperties.

_{How can I configure this property?}

Configuration properties can be included and activated using the following strategies.

Note

CAS properties can be specified using the Java configuration property syntax in any and all .properties files:

sentry.session-flush-timeout-millis=...

CAS properties can be specified using the YAML syntax:

sentry: 
  session-flush-timeout-millis: "..."

Note that YAML is very specific about structure and indentation. Be sure to verify the correctness of the final result with your YAML validator of choice.

CAS properties can be passed to the CAS web application as system properties, when the application is launched:

java -Dsentry.session-flush-timeout-millis="..." -jar build/libs/cas.war

CAS properties can specified as system environment variables before the CAS web application is launched:

export SENTRY_SESSION_FLUSH_TIMEOUT_MILLIS="..."

java -jar build/libs/cas.war

The above example assumes that the CAS web application is packaged as cas.war with an embedded server container and can be found in the build/libs directory.

CAS properties can be passed to the CAS web application as command-line arguments, when the application is launched:

java -jar build/libs/cas.war --sentry.session-flush-timeout-millis="..."

The above example assumes that the CAS web application is packaged as cas.war with an embedded server container and can be found in the build/libs directory.

sentry.session-tracking-interval-millis=

io.sentry.spring.boot.jakarta.SentryProperties.

_{How can I configure this property?}

Configuration properties can be included and activated using the following strategies.

Note

CAS properties can be specified using the Java configuration property syntax in any and all .properties files:

sentry.session-tracking-interval-millis=...

CAS properties can be specified using the YAML syntax:

sentry: 
  session-tracking-interval-millis: "..."

Note that YAML is very specific about structure and indentation. Be sure to verify the correctness of the final result with your YAML validator of choice.

CAS properties can be passed to the CAS web application as system properties, when the application is launched:

java -Dsentry.session-tracking-interval-millis="..." -jar build/libs/cas.war

CAS properties can specified as system environment variables before the CAS web application is launched:

export SENTRY_SESSION_TRACKING_INTERVAL_MILLIS="..."

java -jar build/libs/cas.war

The above example assumes that the CAS web application is packaged as cas.war with an embedded server container and can be found in the build/libs directory.

CAS properties can be passed to the CAS web application as command-line arguments, when the application is launched:

java -jar build/libs/cas.war --sentry.session-tracking-interval-millis="..."

The above example assumes that the CAS web application is packaged as cas.war with an embedded server container and can be found in the build/libs directory.

sentry.shutdown-timeout=

io.sentry.spring.boot.jakarta.SentryProperties.

_{How can I configure this property?}

Configuration properties can be included and activated using the following strategies.

Note

CAS properties can be specified using the Java configuration property syntax in any and all .properties files:

sentry.shutdown-timeout=...

CAS properties can be specified using the YAML syntax:

sentry: 
  shutdown-timeout: "..."

Note that YAML is very specific about structure and indentation. Be sure to verify the correctness of the final result with your YAML validator of choice.

CAS properties can be passed to the CAS web application as system properties, when the application is launched:

java -Dsentry.shutdown-timeout="..." -jar build/libs/cas.war

CAS properties can specified as system environment variables before the CAS web application is launched:

export SENTRY_SHUTDOWN_TIMEOUT="..."

java -jar build/libs/cas.war

The above example assumes that the CAS web application is packaged as cas.war with an embedded server container and can be found in the build/libs directory.

CAS properties can be passed to the CAS web application as command-line arguments, when the application is launched:

java -jar build/libs/cas.war --sentry.shutdown-timeout="..."

The above example assumes that the CAS web application is packaged as cas.war with an embedded server container and can be found in the build/libs directory.

Deprecation status is WARNINGwithout a replacement setting.

sentry.shutdown-timeout-millis=

io.sentry.spring.boot.jakarta.SentryProperties.

_{How can I configure this property?}

Configuration properties can be included and activated using the following strategies.

Note

CAS properties can be specified using the Java configuration property syntax in any and all .properties files:

sentry.shutdown-timeout-millis=...

CAS properties can be specified using the YAML syntax:

sentry: 
  shutdown-timeout-millis: "..."

Note that YAML is very specific about structure and indentation. Be sure to verify the correctness of the final result with your YAML validator of choice.

CAS properties can be passed to the CAS web application as system properties, when the application is launched:

java -Dsentry.shutdown-timeout-millis="..." -jar build/libs/cas.war

CAS properties can specified as system environment variables before the CAS web application is launched:

export SENTRY_SHUTDOWN_TIMEOUT_MILLIS="..."

java -jar build/libs/cas.war

The above example assumes that the CAS web application is packaged as cas.war with an embedded server container and can be found in the build/libs directory.

CAS properties can be passed to the CAS web application as command-line arguments, when the application is launched:

java -jar build/libs/cas.war --sentry.shutdown-timeout-millis="..."

The above example assumes that the CAS web application is packaged as cas.war with an embedded server container and can be found in the build/libs directory.

sentry.spotlight-connection-url=

io.sentry.spring.boot.jakarta.SentryProperties.

_{How can I configure this property?}

Configuration properties can be included and activated using the following strategies.

Note

CAS properties can be specified using the Java configuration property syntax in any and all .properties files:

sentry.spotlight-connection-url=...

CAS properties can be specified using the YAML syntax:

sentry: 
  spotlight-connection-url: "..."

Note that YAML is very specific about structure and indentation. Be sure to verify the correctness of the final result with your YAML validator of choice.

CAS properties can be passed to the CAS web application as system properties, when the application is launched:

java -Dsentry.spotlight-connection-url="..." -jar build/libs/cas.war

CAS properties can specified as system environment variables before the CAS web application is launched:

export SENTRY_SPOTLIGHT_CONNECTION_URL="..."

java -jar build/libs/cas.war

The above example assumes that the CAS web application is packaged as cas.war with an embedded server container and can be found in the build/libs directory.

CAS properties can be passed to the CAS web application as command-line arguments, when the application is launched:

java -jar build/libs/cas.war --sentry.spotlight-connection-url="..."

The above example assumes that the CAS web application is packaged as cas.war with an embedded server container and can be found in the build/libs directory.

sentry.ssl-socket-factory=

io.sentry.spring.boot.jakarta.SentryProperties.

_{How can I configure this property?}

Configuration properties can be included and activated using the following strategies.

Note

CAS properties can be specified using the Java configuration property syntax in any and all .properties files:

sentry.ssl-socket-factory=...

CAS properties can be specified using the YAML syntax:

sentry: 
  ssl-socket-factory: "..."

Note that YAML is very specific about structure and indentation. Be sure to verify the correctness of the final result with your YAML validator of choice.

CAS properties can be passed to the CAS web application as system properties, when the application is launched:

java -Dsentry.ssl-socket-factory="..." -jar build/libs/cas.war

CAS properties can specified as system environment variables before the CAS web application is launched:

export SENTRY_SSL_SOCKET_FACTORY="..."

java -jar build/libs/cas.war

The above example assumes that the CAS web application is packaged as cas.war with an embedded server container and can be found in the build/libs directory.

CAS properties can be passed to the CAS web application as command-line arguments, when the application is launched:

java -jar build/libs/cas.war --sentry.ssl-socket-factory="..."

The above example assumes that the CAS web application is packaged as cas.war with an embedded server container and can be found in the build/libs directory.

sentry.tags=

io.sentry.spring.boot.jakarta.SentryProperties.

_{How can I configure this property?}

Configuration properties can be included and activated using the following strategies.

Note

CAS properties can be specified using the Java configuration property syntax in any and all .properties files:

sentry.tags=...

CAS properties can be specified using the YAML syntax:

sentry: 
  tags: "..."

Note that YAML is very specific about structure and indentation. Be sure to verify the correctness of the final result with your YAML validator of choice.

CAS properties can be passed to the CAS web application as system properties, when the application is launched:

java -Dsentry.tags="..." -jar build/libs/cas.war

CAS properties can specified as system environment variables before the CAS web application is launched:

export SENTRY_TAGS="..."

java -jar build/libs/cas.war

The above example assumes that the CAS web application is packaged as cas.war with an embedded server container and can be found in the build/libs directory.

CAS properties can be passed to the CAS web application as command-line arguments, when the application is launched:

java -jar build/libs/cas.war --sentry.tags="..."

The above example assumes that the CAS web application is packaged as cas.war with an embedded server container and can be found in the build/libs directory.

sentry.trace-options-requests=

io.sentry.spring.boot.jakarta.SentryProperties.

_{How can I configure this property?}

Configuration properties can be included and activated using the following strategies.

Note

CAS properties can be specified using the Java configuration property syntax in any and all .properties files:

sentry.trace-options-requests=...

CAS properties can be specified using the YAML syntax:

sentry: 
  trace-options-requests: "..."

Note that YAML is very specific about structure and indentation. Be sure to verify the correctness of the final result with your YAML validator of choice.

CAS properties can be passed to the CAS web application as system properties, when the application is launched:

java -Dsentry.trace-options-requests="..." -jar build/libs/cas.war

CAS properties can specified as system environment variables before the CAS web application is launched:

export SENTRY_TRACE_OPTIONS_REQUESTS="..."

java -jar build/libs/cas.war

The above example assumes that the CAS web application is packaged as cas.war with an embedded server container and can be found in the build/libs directory.

CAS properties can be passed to the CAS web application as command-line arguments, when the application is launched:

java -jar build/libs/cas.war --sentry.trace-options-requests="..."

The above example assumes that the CAS web application is packaged as cas.war with an embedded server container and can be found in the build/libs directory.

sentry.trace-propagation-targets=

io.sentry.spring.boot.jakarta.SentryProperties.

_{How can I configure this property?}

Configuration properties can be included and activated using the following strategies.

Note

CAS properties can be specified using the Java configuration property syntax in any and all .properties files:

sentry.trace-propagation-targets=...

CAS properties can be specified using the YAML syntax:

sentry: 
  trace-propagation-targets: "..."

Note that YAML is very specific about structure and indentation. Be sure to verify the correctness of the final result with your YAML validator of choice.

CAS properties can be passed to the CAS web application as system properties, when the application is launched:

java -Dsentry.trace-propagation-targets="..." -jar build/libs/cas.war

CAS properties can specified as system environment variables before the CAS web application is launched:

export SENTRY_TRACE_PROPAGATION_TARGETS="..."

java -jar build/libs/cas.war

The above example assumes that the CAS web application is packaged as cas.war with an embedded server container and can be found in the build/libs directory.

CAS properties can be passed to the CAS web application as command-line arguments, when the application is launched:

java -jar build/libs/cas.war --sentry.trace-propagation-targets="..."

The above example assumes that the CAS web application is packaged as cas.war with an embedded server container and can be found in the build/libs directory.

sentry.trace-sampling=

io.sentry.spring.boot.jakarta.SentryProperties.

_{How can I configure this property?}

Configuration properties can be included and activated using the following strategies.

Note

CAS properties can be specified using the Java configuration property syntax in any and all .properties files:

sentry.trace-sampling=...

CAS properties can be specified using the YAML syntax:

sentry: 
  trace-sampling: "..."

Note that YAML is very specific about structure and indentation. Be sure to verify the correctness of the final result with your YAML validator of choice.

CAS properties can be passed to the CAS web application as system properties, when the application is launched:

java -Dsentry.trace-sampling="..." -jar build/libs/cas.war

CAS properties can specified as system environment variables before the CAS web application is launched:

export SENTRY_TRACE_SAMPLING="..."

java -jar build/libs/cas.war

The above example assumes that the CAS web application is packaged as cas.war with an embedded server container and can be found in the build/libs directory.

CAS properties can be passed to the CAS web application as command-line arguments, when the application is launched:

java -jar build/libs/cas.war --sentry.trace-sampling="..."

The above example assumes that the CAS web application is packaged as cas.war with an embedded server container and can be found in the build/libs directory.

Deprecation status is WARNINGwithout a replacement setting.

sentry.traces-sample-rate=

io.sentry.spring.boot.jakarta.SentryProperties.

_{How can I configure this property?}

Configuration properties can be included and activated using the following strategies.

Note

CAS properties can be specified using the Java configuration property syntax in any and all .properties files:

sentry.traces-sample-rate=...

CAS properties can be specified using the YAML syntax:

sentry: 
  traces-sample-rate: "..."

Note that YAML is very specific about structure and indentation. Be sure to verify the correctness of the final result with your YAML validator of choice.

CAS properties can be passed to the CAS web application as system properties, when the application is launched:

java -Dsentry.traces-sample-rate="..." -jar build/libs/cas.war

CAS properties can specified as system environment variables before the CAS web application is launched:

export SENTRY_TRACES_SAMPLE_RATE="..."

java -jar build/libs/cas.war

The above example assumes that the CAS web application is packaged as cas.war with an embedded server container and can be found in the build/libs directory.

CAS properties can be passed to the CAS web application as command-line arguments, when the application is launched:

java -jar build/libs/cas.war --sentry.traces-sample-rate="..."

The above example assumes that the CAS web application is packaged as cas.war with an embedded server container and can be found in the build/libs directory.

sentry.tracing-origins=

io.sentry.spring.boot.jakarta.SentryProperties.

_{How can I configure this property?}

Configuration properties can be included and activated using the following strategies.

Note

CAS properties can be specified using the Java configuration property syntax in any and all .properties files:

sentry.tracing-origins=...

CAS properties can be specified using the YAML syntax:

sentry: 
  tracing-origins: "..."

Note that YAML is very specific about structure and indentation. Be sure to verify the correctness of the final result with your YAML validator of choice.

CAS properties can be passed to the CAS web application as system properties, when the application is launched:

java -Dsentry.tracing-origins="..." -jar build/libs/cas.war

CAS properties can specified as system environment variables before the CAS web application is launched:

export SENTRY_TRACING_ORIGINS="..."

java -jar build/libs/cas.war

The above example assumes that the CAS web application is packaged as cas.war with an embedded server container and can be found in the build/libs directory.

CAS properties can be passed to the CAS web application as command-line arguments, when the application is launched:

java -jar build/libs/cas.war --sentry.tracing-origins="..."

The above example assumes that the CAS web application is packaged as cas.war with an embedded server container and can be found in the build/libs directory.

Deprecation status is WARNINGwithout a replacement setting.

sentry.transaction-performance-collector=

io.sentry.spring.boot.jakarta.SentryProperties.

_{How can I configure this property?}

Configuration properties can be included and activated using the following strategies.

Note

CAS properties can be specified using the Java configuration property syntax in any and all .properties files:

sentry.transaction-performance-collector=...

CAS properties can be specified using the YAML syntax:

sentry: 
  transaction-performance-collector: "..."

Note that YAML is very specific about structure and indentation. Be sure to verify the correctness of the final result with your YAML validator of choice.

CAS properties can be passed to the CAS web application as system properties, when the application is launched:

java -Dsentry.transaction-performance-collector="..." -jar build/libs/cas.war

CAS properties can specified as system environment variables before the CAS web application is launched:

export SENTRY_TRANSACTION_PERFORMANCE_COLLECTOR="..."

java -jar build/libs/cas.war

The above example assumes that the CAS web application is packaged as cas.war with an embedded server container and can be found in the build/libs directory.

CAS properties can be passed to the CAS web application as command-line arguments, when the application is launched:

java -jar build/libs/cas.war --sentry.transaction-performance-collector="..."

The above example assumes that the CAS web application is packaged as cas.war with an embedded server container and can be found in the build/libs directory.

sentry.transaction-profiler=

io.sentry.spring.boot.jakarta.SentryProperties.

_{How can I configure this property?}

Configuration properties can be included and activated using the following strategies.

Note

CAS properties can be specified using the Java configuration property syntax in any and all .properties files:

sentry.transaction-profiler=...

CAS properties can be specified using the YAML syntax:

sentry: 
  transaction-profiler: "..."

Note that YAML is very specific about structure and indentation. Be sure to verify the correctness of the final result with your YAML validator of choice.

CAS properties can be passed to the CAS web application as system properties, when the application is launched:

java -Dsentry.transaction-profiler="..." -jar build/libs/cas.war

CAS properties can specified as system environment variables before the CAS web application is launched:

export SENTRY_TRANSACTION_PROFILER="..."

java -jar build/libs/cas.war

The above example assumes that the CAS web application is packaged as cas.war with an embedded server container and can be found in the build/libs directory.

CAS properties can be passed to the CAS web application as command-line arguments, when the application is launched:

java -jar build/libs/cas.war --sentry.transaction-profiler="..."

The above example assumes that the CAS web application is packaged as cas.war with an embedded server container and can be found in the build/libs directory.

sentry.transport-factory=

io.sentry.spring.boot.jakarta.SentryProperties.

_{How can I configure this property?}

Configuration properties can be included and activated using the following strategies.

Note

CAS properties can be specified using the Java configuration property syntax in any and all .properties files:

sentry.transport-factory=...

CAS properties can be specified using the YAML syntax:

sentry: 
  transport-factory: "..."

Note that YAML is very specific about structure and indentation. Be sure to verify the correctness of the final result with your YAML validator of choice.

CAS properties can be passed to the CAS web application as system properties, when the application is launched:

java -Dsentry.transport-factory="..." -jar build/libs/cas.war

CAS properties can specified as system environment variables before the CAS web application is launched:

export SENTRY_TRANSPORT_FACTORY="..."

java -jar build/libs/cas.war

The above example assumes that the CAS web application is packaged as cas.war with an embedded server container and can be found in the build/libs directory.

CAS properties can be passed to the CAS web application as command-line arguments, when the application is launched:

java -jar build/libs/cas.war --sentry.transport-factory="..."

The above example assumes that the CAS web application is packaged as cas.war with an embedded server container and can be found in the build/libs directory.

sentry.transport-gate=

io.sentry.spring.boot.jakarta.SentryProperties.

_{How can I configure this property?}

Configuration properties can be included and activated using the following strategies.

Note

CAS properties can be specified using the Java configuration property syntax in any and all .properties files:

sentry.transport-gate=...

CAS properties can be specified using the YAML syntax:

sentry: 
  transport-gate: "..."

Note that YAML is very specific about structure and indentation. Be sure to verify the correctness of the final result with your YAML validator of choice.

CAS properties can be passed to the CAS web application as system properties, when the application is launched:

java -Dsentry.transport-gate="..." -jar build/libs/cas.war

CAS properties can specified as system environment variables before the CAS web application is launched:

export SENTRY_TRANSPORT_GATE="..."

java -jar build/libs/cas.war

The above example assumes that the CAS web application is packaged as cas.war with an embedded server container and can be found in the build/libs directory.

CAS properties can be passed to the CAS web application as command-line arguments, when the application is launched:

java -jar build/libs/cas.war --sentry.transport-gate="..."

The above example assumes that the CAS web application is packaged as cas.war with an embedded server container and can be found in the build/libs directory.

sentry.use-git-commit-id-as-release=true

Whether to use Git commit id as a release.

io.sentry.spring.boot.jakarta.SentryProperties.

_{How can I configure this property?}

Configuration properties can be included and activated using the following strategies.

Note

CAS properties can be specified using the Java configuration property syntax in any and all .properties files:

sentry.use-git-commit-id-as-release=true

CAS properties can be specified using the YAML syntax:

sentry: 
  use-git-commit-id-as-release: "true"

Note that YAML is very specific about structure and indentation. Be sure to verify the correctness of the final result with your YAML validator of choice.

CAS properties can be passed to the CAS web application as system properties, when the application is launched:

java -Dsentry.use-git-commit-id-as-release="true" -jar build/libs/cas.war

CAS properties can specified as system environment variables before the CAS web application is launched:

export SENTRY_USE_GIT_COMMIT_ID_AS_RELEASE="true"

java -jar build/libs/cas.war

The above example assumes that the CAS web application is packaged as cas.war with an embedded server container and can be found in the build/libs directory.

CAS properties can be passed to the CAS web application as command-line arguments, when the application is launched:

java -jar build/libs/cas.war --sentry.use-git-commit-id-as-release="true"

The above example assumes that the CAS web application is packaged as cas.war with an embedded server container and can be found in the build/libs directory.

sentry.user-filter-order=

Defines the io.sentry.spring.SentryUserFilter order. The default value is org.springframework.core.Ordered.LOWEST_PRECEDENCE, if Spring Security is auto-configured, its guaranteed to run after Spring Security filter chain.

io.sentry.spring.boot.jakarta.SentryProperties.

_{How can I configure this property?}

Configuration properties can be included and activated using the following strategies.

Note

CAS properties can be specified using the Java configuration property syntax in any and all .properties files:

sentry.user-filter-order=...

CAS properties can be specified using the YAML syntax:

sentry: 
  user-filter-order: "..."

Note that YAML is very specific about structure and indentation. Be sure to verify the correctness of the final result with your YAML validator of choice.

CAS properties can be passed to the CAS web application as system properties, when the application is launched:

java -Dsentry.user-filter-order="..." -jar build/libs/cas.war

CAS properties can specified as system environment variables before the CAS web application is launched:

export SENTRY_USER_FILTER_ORDER="..."

java -jar build/libs/cas.war

The above example assumes that the CAS web application is packaged as cas.war with an embedded server container and can be found in the build/libs directory.

CAS properties can be passed to the CAS web application as command-line arguments, when the application is launched:

java -jar build/libs/cas.war --sentry.user-filter-order="..."

The above example assumes that the CAS web application is packaged as cas.war with an embedded server container and can be found in the build/libs directory.

sentry.view-hierarchy-exporters=

io.sentry.spring.boot.jakarta.SentryProperties.

_{How can I configure this property?}

Configuration properties can be included and activated using the following strategies.

Note

CAS properties can be specified using the Java configuration property syntax in any and all .properties files:

sentry.view-hierarchy-exporters=...

CAS properties can be specified using the YAML syntax:

sentry: 
  view-hierarchy-exporters: "..."

Note that YAML is very specific about structure and indentation. Be sure to verify the correctness of the final result with your YAML validator of choice.

CAS properties can be passed to the CAS web application as system properties, when the application is launched:

java -Dsentry.view-hierarchy-exporters="..." -jar build/libs/cas.war

CAS properties can specified as system environment variables before the CAS web application is launched:

export SENTRY_VIEW_HIERARCHY_EXPORTERS="..."

java -jar build/libs/cas.war

The above example assumes that the CAS web application is packaged as cas.war with an embedded server container and can be found in the build/libs directory.

CAS properties can be passed to the CAS web application as command-line arguments, when the application is launched:

java -jar build/libs/cas.war --sentry.view-hierarchy-exporters="..."

The above example assumes that the CAS web application is packaged as cas.war with an embedded server container and can be found in the build/libs directory.

# 
# sentry.attach-server-name=

# 
# sentry.attach-stacktrace=

# 
# sentry.attach-threads=

# 
# sentry.backpressure-monitor=

# 
# sentry.bundle-ids=

# 
# sentry.cache-dir-path=

# 
# sentry.connection-status-provider=

# 
# sentry.connection-timeout-millis=

# 
# sentry.context-tags=

# 
# sentry.cron.default-checkin-margin=

# 
# sentry.cron.default-failure-issue-threshold=

# 
# sentry.cron.default-max-runtime=

# 
# sentry.cron.default-recovery-threshold=

# 
# sentry.cron.default-timezone=

# 
# sentry.date-provider=

# 
# sentry.debug=

# 
# sentry.debug-meta-loader=

# 
# sentry.diagnostic-level=

# 
# sentry.dist=

# 
# sentry.distinct-id=

# 
# sentry.dsn=

# If set to true, this flag disables all AOP related features (e.g.
# sentry.enable-aot-compatibility=false

# 
# sentry.enable-app-start-profiling=

# 
# sentry.enable-auto-session-tracking=

# 
# sentry.enable-backpressure-handling=

# 
# sentry.enable-deduplication=

# 
# sentry.enable-default-tags-for-metrics=

# 
# sentry.enable-external-configuration=

# 
# sentry.enable-metrics=

# 
# sentry.enable-pretty-serialization-output=

# 
# sentry.enable-scope-persistence=

# 
# sentry.enable-screen-tracking=

# 
# sentry.enable-shutdown-hook=

# 
# sentry.enable-span-local-metric-aggregation=

# 
# sentry.enable-spotlight=

# 
# sentry.enable-time-to-full-display-tracing=

# 
# sentry.enable-tracing=

# 
# sentry.enable-uncaught-exception-handler=

# 
# sentry.enable-user-interaction-breadcrumbs=

# 
# sentry.enable-user-interaction-tracing=

# 
# sentry.enabled=

# 
# sentry.envelope-disk-cache=

# 
# sentry.envelope-reader=

# 
# sentry.environment=

# 
# sentry.event-processors=

# Report all or only uncaught web exceptions.
# sentry.exception-resolver-order=1

# 
# sentry.executor-service=

# 
# sentry.flush-timeout-millis=

# 
# sentry.fully-displayed-reporter=

# 
# sentry.gesture-target-locators=

# List of error types the Sentry Graphql integration should ignore.
# sentry.graphql.ignored-error-types=

# 
# sentry.idle-timeout=

# 
# sentry.ignored-check-ins=

# 
# sentry.ignored-exceptions-for-type=

# 
# sentry.in-app-excludes=

# 
# sentry.in-app-includes=

# 
# sentry.instrumenter=

# 
# sentry.integrations=

# 
# sentry.logger=

# Enable/Disable logging auto-configuration.
# sentry.logging.enabled=true

# List of loggers the SentryAppender should be added to.
# sentry.logging.loggers=

# Minimum logging level for recording breadcrumb.
# sentry.logging.minimum-breadcrumb-level=

# Minimum logging level for recording event.
# sentry.logging.minimum-event-level=

# 
# sentry.main-thread-checker=

# 
# sentry.max-attachment-size=

# 
# sentry.max-breadcrumbs=

# 
# sentry.max-cache-items=

# 
# sentry.max-depth=

# 
# sentry.max-queue-size=

# 
# sentry.max-request-body-size=

# 
# sentry.max-spans=

# 
# sentry.max-trace-file-size=

# 
# sentry.modules-loader=

# 
# sentry.options-observers=

# 
# sentry.performance-collectors=

# 
# sentry.print-uncaught-stack-trace=

# 
# sentry.profiles-sample-rate=

# 
# sentry.profiling-enabled=

# 
# sentry.profiling-traces-hz=

# 
# sentry.proguard-uuid=

# 
# sentry.proxy.host=

# 
# sentry.proxy.pass=

# 
# sentry.proxy.port=

# 
# sentry.proxy.type=

# 
# sentry.proxy.user=

# Enable/Disable usage of {@link io.micrometer.context.ThreadLocalAccessor} for Hub propagation
# sentry.reactive.thread-local-accessor-enabled=true

# 
# sentry.read-timeout-millis=

# 
# sentry.release=

# 
# sentry.replay-controller=

# 
# sentry.sample-rate=

# 
# sentry.scope-observers=

# 
# sentry.sdk-version=

# 
# sentry.send-client-reports=

# 
# sentry.send-default-pii=

# 
# sentry.send-modules=

# 
# sentry.sentry-client-name=

# 
# sentry.serializer=

# 
# sentry.server-name=

# 
# sentry.session-flush-timeout-millis=

# 
# sentry.session-tracking-interval-millis=

# 
# sentry.shutdown-timeout=

# 
# sentry.shutdown-timeout-millis=

# 
# sentry.spotlight-connection-url=

# 
# sentry.ssl-socket-factory=

# 
# sentry.tags=

# 
# sentry.trace-options-requests=

# 
# sentry.trace-propagation-targets=

# 
# sentry.trace-sampling=

# 
# sentry.traces-sample-rate=

# 
# sentry.tracing-origins=

# 
# sentry.transaction-performance-collector=

# 
# sentry.transaction-profiler=

# 
# sentry.transport-factory=

# 
# sentry.transport-gate=

# Whether to use Git commit id as a release.
# sentry.use-git-commit-id-as-release=true

# Defines the {@link io.sentry.spring.SentryUserFilter} order.
# sentry.user-filter-order=

# 
# sentry.view-hierarchy-exporters=

Configuration Metadata

The collection of configuration properties listed in this section are automatically generated from the CAS source and components that contain the actual field definitions, types, descriptions, modules, etc. This metadata may not always be 100% accurate, or could be lacking details and sufficient explanations.

Be Selective

This section is meant as a guide only. Do NOT copy/paste the entire collection of settings into your CAS configuration; rather pick only the properties that you need. Do NOT enable settings unless you are certain of their purpose and do NOT copy settings into your configuration only to keep them as reference. All these ideas lead to upgrade headaches, maintenance nightmares and premature aging.

YAGNI

Note that for nearly ALL use cases, declaring and configuring properties listed here is sufficient. You should NOT have to explicitly massage a CAS XML/Java/etc configuration file to design an authentication handler, create attribute release policies, etc. CAS at runtime will auto-configure all required changes for you. If you are unsure about the meaning of a given CAS setting, do NOT turn it on without hesitation. Review the codebase or better yet, ask questions to clarify the intended behavior.

Naming Convention

Property names can be specified in very relaxed terms. For instance cas.someProperty, cas.some-property, cas.some_property are all valid names. While all forms are accepted by CAS, there are certain components (in CAS and other frameworks used) whose activation at runtime is conditional on a property value, where this property is required to have been specified in CAS configuration using kebab case. This is both true for properties that are owned by CAS as well as those that might be presented to the system via an external library or framework such as Spring Boot, etc.

Note

Settings and properties that are controlled by the CAS platform directly always begin with the prefix cas. All other settings are controlled and provided to CAS via other underlying frameworks and may have their own schemas and syntax. BE CAREFUL with the distinction. Unrecognized properties are rejected by CAS and/or frameworks upon which CAS depends. This means if you somehow misspell a property definition or fail to adhere to the dot-notation syntax and such, your setting is entirely refused by CAS and likely the feature it controls will never be activated in the way you intend.

Validation

Configuration properties are automatically validated on CAS startup to report issues with configuration binding, specially if defined CAS settings cannot be recognized or validated by the configuration schema. Additional validation processes are also handled via Configuration Metadata and property migrations applied automatically on startup by Spring Boot and family.

Indexed Settings

CAS settings able to accept multiple values are typically documented with an index, such as cas.some.setting[0]=value. The index [0] is meant to be incremented by the adopter to allow for distinct multiple configuration blocks.

Breadcrumbs are kept in memory (by default the last 100 records) and are sent with events. For example, by default, if you log 100 entries with logger.info or logger.warn, no event is sent to Sentry. If you then log with logger.error, an event is sent to Sentry that includes those 100 info or warn messages. For this to work, SentryAppender needs to receive all log entries to decide what to keep as breadcrumb or send as event. Set the SentryAppender log level configuration to a value lower than what is set for the minimumBreadcrumbLevel and minimumEventLevel so that it receives these log messages.

Finally, you will need to configure your DSN (client key) and optionally other values such as environment and release.

You can do so in a src/main/resources/sentry.properties file:

dsn=https://12345@12345.ingest.sentry.io/12345

Or via system properties when you launch CAS:

java -Dsentry.dsn=https://12345@12345.ingest.sentry.io/12345 ...

Or via environment variables before you launch CAS:

export SENTRY_DSN=https://12345@12345.ingest.sentry.io/12345