feat: vereinheitliche Startup-Logs in allen Backend-Services, verbessere Konsistenz und Diagnosemöglichkeiten

Signed-off-by: StefanMoCoAt <stefan.mo.co@gmail.com>

backend/services/scheduling/scheduling-service/src/main/kotlin/at/mocode/scheduling/service/SchedulingServiceApplication.kt

@@ -1,12 +1,31 @@
 package at.mocode.scheduling.service
 
+import org.slf4j.LoggerFactory
 import org.springframework.boot.autoconfigure.SpringBootApplication
+import org.springframework.boot.context.event.ApplicationReadyEvent
 import org.springframework.boot.runApplication
+import org.springframework.context.event.EventListener
+import org.springframework.core.env.Environment
 import org.springframework.web.bind.annotation.GetMapping
 import org.springframework.web.bind.annotation.RestController
 
 @SpringBootApplication
-class SchedulingServiceApplication
+class SchedulingServiceApplication(private val env: Environment) {
+
+  private val log = LoggerFactory.getLogger(SchedulingServiceApplication::class.java)
+
+  @EventListener(ApplicationReadyEvent::class)
+  fun onApplicationReady() {
+    val springPort = env.getProperty("server.port", "8089")
+    val appName = env.getProperty("spring.application.name", "scheduling-service")
+
+    log.info("----------------------------------------------------------")
+    log.info("Application '{}' is running!", appName)
+    log.info("Spring Management Port: {}", springPort)
+    log.info("Profiles:               {}", env.activeProfiles.joinToString(", "))
+    log.info("----------------------------------------------------------")
+  }
+}
 
 fun main(args: Array<String>) {
     runApplication<SchedulingServiceApplication>(*args)