As these seem to be tied to spring and more specifically Springs reactive implementation 'io.reactor' i.e. 'Mono / Flux' should they be called 'qudini-reactor' ? as they possibly won't work with other reactive implementations. @sp00m Thoughts?

This issue lists Renovate updates and detected dependencies. Read the Dependency Dashboard docs to learn more.

Rate-Limited

These updates are currently rate-limited. Click on a checkbox below to force their creation now.

• Update dependency org.jacoco:jacoco-maven-plugin to v0.8.12
• Update dependency com.google.guava:guava to v33.1.0-jre
• Update dependency com.newrelic.agent.java:newrelic-api to v8.11.0
• Update dependency org.bouncycastle:bcpkix-jdk18on to v1.78.1
• 🔐 Create all rate-limited PRs at once 🔐

Open

These updates have all been created already. Click a checkbox below to force a retry/rebase of any.

• Update dependency org.springframework.boot:spring-boot-starter-parent to v3.2.5
• Update testcontainers-java monorepo to v1.19.7 (org.testcontainers:r2dbc, org.testcontainers:mysql, org.testcontainers:junit-jupiter, org.testcontainers:testcontainers)
• Update aws-java-sdk-v2 monorepo to v2.25.34 (software.amazon.awssdk:sns, software.amazon.awssdk:s3, software.amazon.awssdk:sts, software.amazon.awssdk:sqs)
• Update dependency io.sentry:sentry to v7.8.0
• Update dependency org.apache.maven.plugins:maven-gpg-plugin to v3.2.4
• Update dependency org.wiremock:wiremock-standalone to v3.5.3
• Update actions/cache action to v4
• Update actions/setup-java action to v4
• Update dependency com.lmax:disruptor to v4
• Update dependency com.qudini:qudini-gom to v9
• Click on this checkbox to rebase all open PRs at once

Detected dependencies

• Check this box to trigger a request for Renovate to run again on this repository

Most of the codebases need to exclude the probes from the auth layer when Spring Security's HTTP filter level auth is used:

.pathMatchers(HttpMethod.GET, "/liveness", "/readiness", "/metrics").permitAll()
.pathMatchers(HttpMethod.HEAD, "/liveness").permitAll()

Could be interesting to prepare such a matcher in reactive-metrics directly so that we're fully in charge of the paths.

• toMap without a value mapper
• unmodifiableGroupingBy

See how spring-projects/spring-framework#25633 can help to improve #40.

Hey, first of thank you for developing this. I have an issue, I'm trying to get contextual logging working with a gateway application. I've tried several different solutions and failed since its either resource intensive (Spring Sleuth) or it can produce misleading results (https://www.novatec-gmbh.de/en/blog/how-can-the-mdc-context-be-used-in-the-reactive-spring-applications/. ( Correlation ids showing up in logs that were not triggered by my request but rather some background process that uses WebClient))
.
Ive wired up your solution and it does seem to add a correlation_id to the reactive context but the QudiniLogEvent always has an empty context. Below is an example of a log line generated in the HttpWebHandlerAdapter. Notice theres nothing in the MDC

{"timestamp":"2021-11-02T21:43:06.058Z","level":"DEBUG","message":"[9d56bc30-2, L:/0:0:0:0:0:0:0:1:8085 - R:/0:0:0:0:0:0:0:1:51859] HTTP GET \"/services/unified/v1/authn/.well-known/webfinger?resource=iampsrtenant-robin3&tenantAlias=IAMPSRTENANT288\"","build_version":"unknown","thread":"reactor-http-nio-6","logger":"org.springframework.web.server.adapter.HttpWebHandlerAdapter","env":"unknown"}

Do you know how to get this working for a project based of spring cloud gateway?
I've gotten it to where it will output
{"correlation_id":"dca04dc2-a4f1-4242-9932-dd1971948bda","timestamp":"2021-11-03T14:06:45.714Z","level":"INFO","message":"TESTTESTTEST","build_version":"unknown","thread":"reactor-http-nio-6","logger":"com.something.gateway.filters.CorrelationFilter","env":"unknown"}

However that is when the log statement is inside Log.thenMono. Is there any way to do this throughout the whole request chain? Starting at the httphandler?

https://spring.io/projects/spring-cloud-gateway#samples

https://www.elastic.co/guide/en/ecs/current/ecs-getting-started.html

Via Mono#fromFuture