[SERVER-62078] serverStatus metrics to diagnose bottlenecks in SSL Created: 15/Dec/21  Updated: 27/Oct/23  Resolved: 13/Mar/23

Status: Closed
Project: Core Server
Component/s: Diagnostics
Affects Version/s: None
Fix Version/s: None

Type: New Feature Priority: Major - P3
Reporter: Bruce Lucas (Inactive) Assignee: Backlog - Security Team
Resolution: Gone away Votes: 0
Labels: former-quick-wins
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Depends
Related
Assigned Teams:
Server Security
Sprint: Security 2022-10-03, Security 2022-10-17, Security 2022-10-31, Security 2022-11-14, Security 2022-12-12
Participants:

 Description   

On a few occasions we have seen bottlenecks in SSL code that were extremely difficult to diagnose. Can we add some instrumentation to make them visible? A simple example might be to track cumulative time spent in calls to ERR_get_state which have been a cause of bottlenecks, but there may be other places higher in the stack that would be better places to watch for unexpected bottlenecks. This would be comparable to the way we monitor other possible bottlenecks like locks, tickets, some key storage bottlenecks, etc.


Generated at Thu Feb 08 05:54:06 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.