On Tue, 3 Dec 2024 12:34:20 GMT, Alan Bateman <al...@openjdk.org> wrote:
>> A connection failure introduces a latency in the application, so probably >> best to have such an event durational as well. > > @egahlin The updated PR proposes two duration events: jdk.SocketConnect for > when a connection is established, and jdk.SocketConnectFailed for when a > connection cannot be established. Naming aside, it seems that would allow the > jfr views that you listed above. We could have two views with only one event. The query for the view could filter for exceptionMessage != null or a failure property. The advantage of having two events is that the failure event could have a threshold of 0 ms. We are planning to add a throttling mechanism for exception events, perhaps per call site. The same mechanism could be used for a failed event. If you receive 500 events per second for a call site, there is little value in having additional events. ------------- PR Review Comment: https://git.openjdk.org/jdk/pull/21528#discussion_r1868506166
