New spring-boot 3.2 log format broke the direct link in "tempo button" after a log search in Loki

building-resilient-microservices / observability

A microservice observability (Logs, Metrics and Traces) example

2 stars 2 forks source link

New spring-boot 3.2 log format broke the direct link in "tempo button" after a log search in Loki #5

Open wanderleisouza opened 10 months ago

wanderleisouza commented 10 months ago

the problem is in the regex docker/grafana/provisioning/datasources/datasource.yml > datasources > 3/3 > jsonData > derivedFields > matcherRegex...

wanderleisouza commented 10 months ago

NEW default log output after Spring 3.2 include [application-name] and [traceID-SpanID] as default.

2023-12-03T11:07:30.181-03:00 INFO 46912 --- [kafka-consumer-demo] [org.springframework.kafka.KafkaListenerEndpointContainer#0-0-C-1] [ca4c324c20f227d9ca4c4bce81deed8d-86a58932a4afe377] c.e.messaging.listener.KafkaConsumer : FactDTO[id=235299, fact=Chuck Norris can spawn threads that complete before they are started.] (metadata: full sync after 0ms)

wanderleisouza commented 8 months ago

can be useful => https://digma.ai/blog/key-changes-in-observability-in-spring-boot-3-2