d087d0d0d1
Bumps [mockito-core](https://github.com/mockito/mockito) from 4.10.0 to
4.11.0.
<details>
<summary>Release notes</summary>
<p><em>Sourced from <a
href="https://github.com/mockito/mockito/releases">mockito-core's
releases</a>.</em></p>
<blockquote>
<h2>v4.11.0</h2>
<p><!-- raw HTML omitted --><!-- raw HTML omitted --><em>Changelog
generated by <a
href="https://github.com/shipkit/shipkit-changelog">Shipkit Changelog
Gradle Plugin</a></em><!-- raw HTML omitted --><!-- raw HTML omitted
--></p>
<h4>4.11.0</h4>
<ul>
<li>2022-12-28 - <a
href="https://github.com/mockito/mockito/compare/v4.10.0...v4.11.0">1
commit(s)</a> by Andy Coates</li>
<li>Improve vararg handling: approach 2 [(<a
href="https://github-redirect.dependabot.com/mockito/mockito/issues/2807">#2807</a>)](<a
href="https://github-redirect.dependabot.com/mockito/mockito/pull/2807">mockito/mockito#2807</a>)</li>
<li>Mocking varargs method with <code>any(String[].class)</code> doesn't
work as expected [(<a
href="https://github-redirect.dependabot.com/mockito/mockito/issues/2796">#2796</a>)](<a
href="https://github-redirect.dependabot.com/mockito/mockito/issues/2796">mockito/mockito#2796</a>)</li>
<li>(Argument)Matchers regression from 1.10.19 to 2.18.3 for varargs
[(<a
href="https://github-redirect.dependabot.com/mockito/mockito/issues/1498">#1498</a>)](<a
href="https://github-redirect.dependabot.com/mockito/mockito/issues/1498">mockito/mockito#1498</a>)</li>
<li>Cannot verify varargs parameter as an array [(<a
href="https://github-redirect.dependabot.com/mockito/mockito/issues/1222">#1222</a>)](<a
href="https://github-redirect.dependabot.com/mockito/mockito/issues/1222">mockito/mockito#1222</a>)</li>
<li>ArgumentCaptor can't capture varargs-arrays [(<a
href="https://github-redirect.dependabot.com/mockito/mockito/issues/584">#584</a>)](<a
href="https://github-redirect.dependabot.com/mockito/mockito/issues/584">mockito/mockito#584</a>)</li>
<li>Verification of an empty varargs call fails when isNotNull() is used
[(<a
href="https://github-redirect.dependabot.com/mockito/mockito/issues/567">#567</a>)](<a
href="https://github-redirect.dependabot.com/mockito/mockito/issues/567">mockito/mockito#567</a>)</li>
</ul>
</blockquote>
</details>
<details>
<summary>Commits</summary>
<ul>
<li><a
href="
|
||
|---|---|---|
| .. | ||
| agent | ||
| bootstrap | ||
| custom | ||
| gradle | ||
| instrumentation | ||
| smoke-tests | ||
| testing/agent-for-testing | ||
| README.md | ||
| build.gradle | ||
| gradle.properties | ||
| gradlew | ||
| gradlew.bat | ||
| settings.gradle | ||
README.md
Distro
Introduction
This repository serves as a collection of examples of extending functionality of OpenTelemetry Java instrumentation agent. It demonstrates how to repackage the aforementioned agent adding custom functionality. For every extension point provided by OpenTelemetry Java instrumentation, this repository contains an example of its usage.
General structure
This repository has four main submodules:
customcontains all custom functionality, SPI and other extensionsagentcontains the main repackaging functionality and, optionally, an entry point to the agent, if one wishes to customize thatinstrumentationcontains custom instrumentations added by vendorsmoke-testscontains simple tests to verify that resulting agent builds and applies correctly
Extensions examples
- DemoIdGenerator - custom
IdGenerator - DemoPropagator - custom
TextMapPropagator - DemoSampler - custom
Sampler - DemoSpanProcessor - custom
SpanProcessor - DemoSpanExporter - custom
SpanExporter - DemoServlet3InstrumentationModule - additional instrumentation
Instrumentation customisation
There are several options to override or customise instrumentation provided by the upstream agent. The following description follows one specific use-case:
Instrumentation X from Otel distribution creates span that I don't like and I want to change it in my vendor distro.
As an example, let us take some database client instrumentation that creates a span for database call and extracts data from db connection to provide attributes for that span.
I don't want this span at all
The easiest case. You can just pre-configure your distribution and disable given instrumentation.
I want to add/modify some attributes and their values does NOT depend on a specific db connection instance
E.g. you want to add some data from call stack as span attribute.
In this case just provide your custom SpanProcessor.
No need for touching instrumentation itself.
I want to add/modify some attributes and their values depend on a specific db connection instance
Write a new instrumentation which injects its own advice into the same method as the original one.
Use getOrder method to ensure it is run after the original instrumentation.
Now you can augment current span with new information.
See DemoServlet3Instrumentation.
I want to remove some attributes
Write custom exporter or use attribute filtering functionality in Collector.
I don't like Otel span at all. I want to significantly modify it and its lifecycle
Disable existing instrumentation.
Write a new one, which injects Advice into the same (or better) method as the original instrumentation.
Write your own Advice for this.
Use existing Tracer directly or extend it.
As you have your own Advice, you can control which Tracer you use.