We are currently integrating our OpenTelemetry Collector with the Splunk HTTP Event Collector (HEC) at the endpoint: https://prd-p-1zjgq.splunkcloud.com:8088 During TLS validation, we encounter the following issue: The server presents a certificate with Common Name (CN): SplunkServerDefaultCert This CN does not match the expected hostname prd-p-1zjgq.splunkcloud.com Despite trusting the SplunkCommonCA root certificate, TLS hostname verification fails with:   certificate subject name 'SplunkServerDefaultCert' does not match target host name 'prd-p-1zjgq.splunkcloud.com'   This leads to failed export attempts from the collector due to strict hostname validation. Could you please advise: Is the current certificate with CN SplunkServerDefaultCert expected behavior for this Splunk Cloud HEC endpoint? If not, can you provide or generate a certificate with the correct hostname (CN or SAN) matching prd-p-1zjgq.splunkcloud.com for production use? If this is a known limitation, what is the recommended approach to securely connect to the HEC endpoint and avoid these TLS validation errors? We want to ensure our integration is secure and compliant with TLS best practices, avoiding the need to disable hostname verification or skip certificate validation. Thank you for your assistance. ... View more