You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
While working on the new Pekko instrumentation, we noticed that with Pekko Http 1 (fork of Akka Http 10.2), it's possible for server routes to skirt our instrumentation.
As of Akka Http 10.2, the seal method in http.scaladsl.server.Route no longer applies to routes in all cases. An alternate method (toFunction) is sometimes called. Since our instrumentation uses seal as the entrypoint to wrap incoming requests and start transactions, routes that go through toFunction fail to report transactions.
This issue was demonstrated with Pekko Http 1.
Description
Verify that for apps using Akka Http 10.2, the existing instrumentation doesn't work.
Then add instrumentation as we have for Pekko Http 1 which captures routes in all cases (likely by instrumenting createAsyncHandler). Add a new AIT for Akka Http 10.2.
The text was updated successfully, but these errors were encountered:
While working on the new Pekko instrumentation, we noticed that with Pekko Http 1 (fork of Akka Http 10.2), it's possible for server routes to skirt our instrumentation.
As of Akka Http 10.2, the
seal
method inhttp.scaladsl.server.Route
no longer applies to routes in all cases. An alternate method (toFunction
) is sometimes called. Since our instrumentation usesseal
as the entrypoint to wrap incoming requests and start transactions, routes that go throughtoFunction
fail to report transactions.This issue was demonstrated with Pekko Http 1.
Description
Verify that for apps using Akka Http 10.2, the existing instrumentation doesn't work.
Then add instrumentation as we have for Pekko Http 1 which captures routes in all cases (likely by instrumenting
createAsyncHandler
). Add a new AIT for Akka Http 10.2.The text was updated successfully, but these errors were encountered: