Ivan Topolnjak

Publish instrumentation artifacts for Scala 3

2

We went through upgrading the core libraries and reporters for Scala 3, but all the instrumentation is still pending. I got this exception at my very first attempt at running...

We have a `akka.remote.track-serialization-metrics` that is not working anymore! This probably happened after the move to using Artery's remote instrument implementation.

Support for Tapir

14

Got this one on [Gitter](https://gitter.im/kamon-io/Kamon?at=5eeb667bbb149531edb7fbe3): > when I use tapir with akka-http backend together with kamon, I observer that span metrics like span_processing_time_seconds_count{operation="http.server.request"} whereas if I dont use Tapir I...

I'm seeing this when starting/stopping a test Lagom service: 

Investigate whether Akka is creating an executor per routee with custom dispatcher

3

In one of our router metric tests we have this configuration (reduced): ``` akka { actor { deployment { "/picking-the-right-dispatcher-in-pool-router/*" { dispatcher = custom-dispatcher } } } } custom-dispatcher {...

Consider a clear way to avoid starting traces on the client/producer side of requests

1

I just noticed a situation where traces would be started automatically by the Kafka producer instrumentation and then followed on all consumers, but there was no actual current trace on...

I'm not sure whether our current Jedis instrumentation would work with clusters and pools on Jedis 4.x. We should check that out and add instrumentation if necessary

Support client-side Akka gRPC requests

3

While working on the service side support (#1119) I noticed it shouldn't be extremely hard to create client Spans for Akka gRPC calls. Also worth taking a look at @jtjeferreira's...

This discussion started on #1096, thanks to @seglo for bringing it up! Datadog might show spans differently in their UI based on the `span.type` tag and there is a tiny...

WARN about failed syctl call on BigSur 11.6

1

This warning shows up on Mac OS Big Sur 11.6: ``` 2021-11-29 17:44:41.710 31 WARN MacOperatingSystem:365 - Failed syctl call for process arguments (kern.procargs2), process 42643 may not exist. Error...