Assigned
Status Update
Comments
ba...@google.com <ba...@google.com>
ka...@google.com <ka...@google.com> #2
I have forwarded this request to the engineering team. We will update this issue with any progress updates and a resolution.
Best Regards,
Josh Moyer
Google Cloud Platform Support
Best Regards,
Josh Moyer
Google Cloud Platform Support
Description
Please describe your requested enhancement. Good feature requests will solve common problems or enable new use cases.
Problem you have encountered: Customer was trying to troubleshoot TLS error.
'{"@type":"
"proxyStatus":"error="tls_certificate_error"; details="client_to_server: certificate_unknown""}'
What you expected to happen:
Customer expects Cloud logs to include the request URL that produced the TLS error and the cipher associated or used for the request to assist troubleshoot the issue.
[1] Currently, logs do not include this information.
How this might work: URL and Cipher will help customer to isolate the issue quicker.
If applicable, reasons why alternative solutions are not sufficient: NA
Other information (workarounds you have tried, documentation consulted, etc): NA
[1] (Masked customer information in logs with *******)
httpRequest: {
latency: "0.435945s"
protocol: "HTTP/1.0"
}
jsonPayload: {
@type: "
proxyStatus: "error="tls_certificate_error"; details="client_to_server: certificate_unknown""
}
logName: "projects/********/logs/
receiveTimestamp: "2024-06-04T09:26:41.787080223Z"
resource: {
labels: {
backend_name: ""
backend_scope: ""
backend_scope_type: "UNKNOWN"
backend_target_name: ""
backend_target_type: "UNKNOWN"
backend_type: "UNKNOWN"
forwarding_rule_name: "*******"
matched_url_path_rule: "UNKNOWN"
network_name: "*****"
project_id: "********"
region: "us-central2"
target_proxy_name: "*****"
url_map_name: ""
}
type: "internal_http_lb_rule"
}
severity: "ERROR"
timestamp: "2024-06-04T09:26:38.965759Z"
}