Jonas Kunz
Jonas Kunz
In our project we are currently writing a Java agent and use ByteBuddy to perform some configurable instrumentation. Based on the configuration we apply one or multiple Advices to methods....
It seems like the metric type incorrectly defaults to "counter" when exposing metrics on the OC-Agent via prometheus which were received from a java OC-Agent exporter. In the "baseline" scenario...
A common usecase in rules is to just assign a constant or some other value to a data key. To do this, currently a "dummy"-actions needs to be used. The...
During the totally unrelated PR #2832 one of the webflux tests failed due to an invalid transaction name: ``` expected: "PUT /functional/hello-mapping" but was: "unnamedPUT /functional/hello-mapping" ``` The fact that...
## What does this PR do? Add support for the finagle http client (#2794). However, this feature is not really useful without support for context propagation across finagle futures. ##...
At the moment messaging transactions are fully handled by the instrumentation of the used underlying messaging technology. This means that for example Transactions are simply named like `Receive message from...
[Finagle](http://twitter.github.io/finagle/) is a reactive scala framework for RPC. It is internally based on netty. Finagle uses [future composition](https://twitter.github.io/finagle/guide/Futures.html) for building processing logic and therefore doesn't work well with our standard...
Implement the persistence for https://github.com/elastic/apm-data/issues/187.
Our current instrumentation only works for Dubbo 2.x. The goal of this issue is to add support and tests for dubbo 3+.
It is possible to receive and send messaged directly to queues instead of exchanges, see [this guide](https://www.springcloud.io/post/2022-01/springboot-rabbitmq-rpc/#gsc.tab=0) for example. We currently only use the exchange for naming transactions and client...