Augment JFR Socket Events

[Erik Gahlin]

Aditional fields might introduce overhead. I would expect, but I could be wrong, that local host is the same in most applications and that the local port is not set by the user, which makes it hard to map to program logic?

I wonder if the existing event thread or the stack trace could be used to separate concurrent connection in your use case? Perhaps a virtual thread per connection task could provide the context?

Thanks
Erik

________________________________
From: hotspot-jfr-dev <hotspot-jfr-dev-retn at openjdk.org> on behalf of Elliot Barlas <elliot.barlas at goto.com>
Sent: Monday, March 6, 2023 6:47 AM
To: hotspot-jfr-dev at openjdk.org <hotspot-jfr-dev at openjdk.org>
Subject: Augment JFR Socket Events

The JFR SocketReadEvent and SocketWriteEvent classes include remote host, remote address, and remote port fields.

The absence of corresponding local host and port fields makes these events much less valueable. In a setting with many concurrent connections to the same target from a particular host, it can be very difficult to associate an event with a particular connection. There just isn't enough context.

Is it possible to extend the events to include that information? Is that something I can contribute?
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://mail.openjdk.org/pipermail/hotspot-jfr-dev/attachments/20230307/955b4634/attachment.htm>