Opentelemetry Splunk Hec Exporter x509: certificate is not valid for any names, but wanted to match

ericaooi — Thu, 27 Jul 2023 05:27:37 GMT

Hi,

I am trying to export data into Splunk using splunkhecexporter by Opentelemetry with TLS insecure_skip_verify=false. When I tried to send it into Splunk, it will shows an error message. After that, I tried to add in the TLS certificate inside the configuration, it still shows the same error message.

Following is the configuration I configured in Opentelemetry .yaml

exporters:
logging:
verbosity: detailed

splunk_hec:
token: "SPLUNK HEC TOKEN"
endpoint: "SPLUNK COLLECTOR URL"
tls:
ca_file: /etc/ssl/certs/cert.crt
cert_file: /etc/ssl/certs/<Splunk_cert>.crt
key_file: /etc/ssl/certs/<Splunk_Key>.key

Following is the error message prompted.

2023-07-26T06:12:01.308Z info exporterhelper/queued_retry.go:433 Exporting failed. Will retry the request after interval. {"kind": "exporter", "data_type": "metrics", "name": "splunk_hec", "error": "Post \"https://<SPLUNK_LINK>:<SPLUNK_PORT>/services/collector\": x509: certificate is not valid for any names, but wanted to match <SPLUNK DNS>", "interval": "7.402035261s"}

May I know what causes this to happen and how to solve this issue, please?

Thank you.

Re: Opentelemetry Splunk Hec Exporter x509: certificate is not valid for any names, but wanted to match
livehybrid — Fri, 04 Aug 2023 22:48:26 GMT

In /etc/ssl/certs/cert.crt do you have the corresponding CA that signed the certificate presented by the HEC endpoint that you are attempting to connect to?

topic Opentelemetry Splunk Hec Exporter x509: certificate is not valid for any names, but wanted to match <Splunk_Link> in Getting Data In

Opentelemetry Splunk Hec Exporter x509: certificate is not valid for any names, but wanted to match