-
Notifications
You must be signed in to change notification settings - Fork 21.8k
CSS-Networking: Add "serverConnectTime" and "serverHeaderTime" to monitor-application-gateway-reference.md #127729
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
base: main
Are you sure you want to change the base?
Conversation
…itor-application-gateway-reference.md CSS-Networking: Added descriptions for columns "serverConnectTime" and "serverHeaderTime" as access logs for V2 SKUs.
@krnnkn : Thanks for your contribution! The author(s) and reviewer(s) have been notified to review your proposed change. |
Learn Build status updates of commit a18c1dc: ✅ Validation status: passed
For more details, please refer to the build report. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Pull Request Overview
This PR adds documentation for two new access log fields in Application Gateway V2 SKUs: serverConnectTime
and serverHeaderTime
. These fields provide timing metrics for backend server connection establishment and response header reception.
- Added descriptions for
serverConnectTime
andserverHeaderTime
fields in the access logs table - Included example values for these fields in the JSON sample
Tip: Customize your code reviews with copilot-instructions.md. Create the file or learn how to get started.
|serverStatus | HTTP status code of the backend server. | | ||
|serverResponseLatency | Latency of the response (in **seconds**) from the backend server. | | ||
|serverConnectTime | Time spent establishing a connection with an upstream server. | | ||
|serverHeaderTime | Time between establishing a connection to the upstream server and receiving the first byte of the response header. | |
Copilot
AI
Oct 14, 2025
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
The descriptions should include the time units for consistency with other timing fields in the table. Based on the example values (0.008, 0.028), these appear to be in seconds like serverResponseLatency.
|serverHeaderTime | Time between establishing a connection to the upstream server and receiving the first byte of the response header. | | |
|serverHeaderTime | Time (in **seconds**) between establishing a connection to the upstream server and receiving the first byte of the response header. | |
Copilot uses AI. Check for mistakes.
"serverStatus": "200", | ||
"serverResponseLatency": "0.028", | ||
"serverConnectTime":"0.008", | ||
"serverHeaderTime":"0.028" |
Copilot
AI
Oct 14, 2025
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Missing comma after the serverHeaderTime line. JSON objects require commas between key-value pairs, and the next line contains another property.
"serverHeaderTime":"0.028" | |
"serverHeaderTime":"0.028", |
Copilot uses AI. Check for mistakes.
Can you review the proposed changes? Important: When the changes are ready for publication, adding a #label:"aq-pr-triaged" |
Added descriptions for columns "serverConnectTime" and "serverHeaderTime" as access logs for V2 SKUs.