* First draft of instrumenting Spring Security
* Create events based on Authentication not SecurityContext
* Simplifying security config
* Checkstyle reformat
* Create DocumentedSpan and EventValue for Spring Security instrumentation
* Adding spring-security-bom to ensure the right dependencies are used.
* TracingSecurityContextChangedListenerTests
* Adding integration tests
* Deleting spring-cloud-sleuth-sample-security
* Checkstyle, license, javadoc
* Inlining SleuthSecuritySpan methods
* Deleting javadoc links from DocumentedSpan
* Updating auto-generated docs
Fixes gh-1996
Change order of TextOutputFormat enum and give `CONTENT_TYPE_OPENZIPKIN_JSON_V2`
highest ordinal value, so that it will be matched first by spring-boot-actuator
and in case of default Accept header JSON data will be returned.
Fixes gh-1990
When using `@ValuePropertySource` in reactive web app,
`KafkaSender` bean is getting created before `BeanPostProcessor` populate `@Value`
and as a result topic is passed as `null` in `KafkaSender.Builder` and it throws `NullPointerException`
To resolve this we are using `Environment` to get the property value instead on relying on `BeanPostProcessor`
to populate `@Value`
Handle BeanCreationException instead of just BeanCurrentlyInCreationException.
This handles the case when a cyclic reference (causing a BeanCurrentlyInCreationException) occurs further down the line - when it is not the actuator of that references the in-creation HttpTracing bean, but a dependency of that actuator. In this case the exception that bubbles up here is an UnsatisfiedDependencyException, which is a BeanCreationException
* Fix datasource-proxy log-level is not working
- Aligned default values of `Query` & `SlowQuery` in
`TraceJdbcProperties.DataSourceProxyProperties`
and `DataSourceProxyProperties`
- Add code to copy properties of `Query` and `SlowQuery` in
`DataSourceProxyConfiguration`
- Add test case to check if `log-level` can be override or not.
Fixes gh-1973
* Disable query log listener by default
- By default `QueryLogListener` and `LoggingQueryLogListener`
will be disabled, dev need to enable it by using properties
- By default `Slf4j` will be enlabled for query logging
so by adding below property slow query logging will be enabled
`spring.sleuth.jdbc.datasource-proxy.slow-query.enable-logging=true`
this property will register `SLF4JSlowQueryListener`
* Add docs for how-to enable data-proxy query logs
without this change there were cases (that we didn't test) where the tracing context would leak and pollute other parts of the code (including tests)
with this change we ensure that in case of errors we don't allow any dangling tracing context
* Bump javadocs since version to 3.1.0
* Extend integration tests to cover all Kafka clients
* Add autoconfiguration module for kafka instrumentation
* Refactor instrumentation for reactive Kafka Receiver
* Refactor instrumentation for reactive Kafka Receiver
* Add docs for Kafka instrumentation
* Revert "Refactor instrumentation for reactive Kafka Receiver"
This reverts commit 58c8f2fa
* Revert "Revert "Refactor instrumentation for reactive Kafka Receiver""
This reverts commit 450a9f8c
* Remove empty test
* Resolve comments from PR 1936
* Revert whitespaces
* Revert whitespaces in common tests pom.xml
* Fix autoconfig to consider generics when registering beans.
Only register reactor-kafka beans if the dependency is on the classpath.
* Split autoconfig for kafka and reactor-kafka