Add support for Sentry monitoring

README.md

@@ -571,6 +571,15 @@ Deploying the Spring Boot Admin server and the client as different components ma
 used to register multiple client apps and the server's lifecycle is not associated with the client. This also means that
 our client app is lighter and production ready.
 
+### Sentry monitoring
+
+To enable Sentry monitoring:
+
+1. Add the `sentry` profile to active spring profiles.
+2. Set a `SENTRY_DSN` environment variable that points to the desired Sentry DSN.
+3. (Optional) Set the `SENTRY_LOG_LEVEL` environment variable to control the minimum log level of events sent to Sentry.
+   The default log level for Sentry is `WARN`. Possible values are `TRACE`, `DEBUG`, `INFO`, `WARN`, and `ERROR`.
+
 ## Performance Testing
 
 The app server supports performance testing using Gatling and Scala. The simulations are located in the

build.gradle

@@ -5,6 +5,7 @@ plugins {
     id 'org.springframework.boot' version "3.0.4"
     id 'org.openjfx.javafxplugin' version '0.0.13'
     id("com.github.ben-manes.versions") version "0.46.0"
+    id 'io.sentry.jvm.gradle' version '4.11.0'
 }
 
 apply plugin: 'checkstyle'

src/main/resources/logback-spring.xml

@@ -59,12 +59,18 @@
     </filter>
   </appender>
 
+  <appender name="Sentry" class="io.sentry.logback.SentryAppender">
+    <minimumEventLevel>${SENTRY_LOG_LEVEL:-WARN}</minimumEventLevel>
+  </appender>
 
   <!-- LOG everything at INFO level -->
   <root level="info">
     <appender-ref ref="RollingFile" />
     <appender-ref ref="Console" />
     <appender-ref ref="RollingFile-Error" />
+    <springProfile name="sentry">
+      <appender-ref ref="Sentry"/>
+    </springProfile>
   </root>
 
 </configuration>