[SERVER-67886] Add metrics for ingress connection authentication Created: 07/Jul/22 Updated: 29/Oct/23 Resolved: 08/Dec/22 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | None |
| Affects Version/s: | None |
| Fix Version/s: | 6.3.0-rc0 |
| Type: | Improvement | Priority: | Major - P3 |
| Reporter: | Vojislav Stojkovic | Assignee: | Adam Rayner |
| Resolution: | Fixed | Votes: | 0 |
| Labels: | neweng | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||
| Backwards Compatibility: | Fully Compatible | ||||||||
| Sprint: | Security 2022-09-05, Security 2022-09-19, Security 2022-10-03, Security 2022-10-17, Security 2022-10-31, Security 2022-11-14, Security 2022-11-28, Security 2022-12-12 | ||||||||
| Participants: | |||||||||
| Description |
|
Record the duration of the authentication conversation for each ingress connection, measuring the duration in milliseconds between the start of authentication (i.e. the moment when saslStart or authenticate command was received) and the success/failure of authentication. Emit a single authentication success/failure log-line for each ingress connection, at default logging level, reporting the duration of the conversation. Emit a default log-level log statement at the conclusion of each portion of the conversation that requires disk access, network round-trips, or intensive CPU use (i.e. for crypto) with the duration in milliseconds for that portion of the conversation. Add a counter that tracks the cumulative time spent doing MongoDB-tier authentication for ingress connections and report it in serverStatus. |
| Comments |
| Comment by Githook User [ 08/Dec/22 ] |
|
Author: {'name': 'Adam Rayner', 'email': 'adam.rayner@mongodb.com', 'username': 'adamtron'}Message: |
| Comment by Githook User [ 08/Dec/22 ] |
|
Author: {'name': 'Adam Rayner', 'email': 'adam.rayner@mongodb.com', 'username': 'adamtron'}Message: |