<?xml version="1.0" encoding="UTF-8"?>
<rss xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/" version="2.0">
  <channel>
    <title>topic Re: Troubleshooting SplunkHecExporter in opentelemetry-collector-contrib in Getting Data In</title>
    <link>https://community.splunk.com/t5/Getting-Data-In/Troubleshooting-SplunkHecExporter-in-opentelemetry-collector/m-p/667378#M111929</link>
    <description>&lt;P&gt;Confirm you see the HF's internal logs in Splunk Cloud (search for "&lt;FONT face="courier new,courier"&gt;index=_internal host=&amp;lt;&amp;lt;your HF name&amp;gt;&amp;gt;&lt;/FONT&gt;").&amp;nbsp; If you don't then the HF is not connecting to Splunk Cloud (did you install the Universal Forwarder app on the HF?) and that should be fixed first.&amp;nbsp; If the HF's logs are in the cloud then use them to determine why otel data is not getting in.&lt;/P&gt;</description>
    <pubDate>Sat, 04 Nov 2023 15:59:56 GMT</pubDate>
    <dc:creator>richgalloway</dc:creator>
    <dc:date>2023-11-04T15:59:56Z</dc:date>
    <item>
      <title>Troubleshooting SplunkHecExporter in opentelemetry-collector-contrib</title>
      <link>https://community.splunk.com/t5/Getting-Data-In/Troubleshooting-SplunkHecExporter-in-opentelemetry-collector/m-p/667376#M111928</link>
      <description>&lt;P&gt;I need advice on troubleshooting SplunkHecExporter.&amp;nbsp; I'm using an OpenTelemetry Collector to accept logs via OTLP, export them to an on-prem Splunk Heavy Forwarder, which them forwards them to Splunk Cloud.&amp;nbsp; Below is my configuration.&amp;nbsp; I'm sending some test logs from Postman but the logs don't arrive in Splunk Cloud.&amp;nbsp; I see the arrival of the logs in the OpenTelemetry Collector through the debug exporter.&amp;nbsp; I confirmed connectivity to the Splunk Heavy Forwarder by setting an invalid token which results in an authentication error.&amp;nbsp; Using a valid token doesn't result in any debug logs being recorded.&amp;nbsp; Any suggestions on troubleshooting?&lt;/P&gt;&lt;P&gt;exporters:&lt;BR /&gt;&amp;nbsp; debug:&lt;BR /&gt;&amp;nbsp; &amp;nbsp; verbosity: normal&lt;BR /&gt;&amp;nbsp; splunk_hec:&lt;BR /&gt;&amp;nbsp; &amp;nbsp; token: "&amp;lt;valid token&amp;gt;"&lt;BR /&gt;&amp;nbsp; &amp;nbsp; endpoint: "&lt;A href="https://splunkheavyforwarder.mydomain.local:8088/services/collector/event" target="_blank" rel="noopener"&gt;https://splunkheavyforwarder.mydomain.local:8088/services/collector/event&lt;/A&gt;"&lt;BR /&gt;&amp;nbsp; &amp;nbsp; source: "oteltest"&lt;BR /&gt;&amp;nbsp; &amp;nbsp; sourcetype: "oteltest"&lt;BR /&gt;&amp;nbsp; &amp;nbsp; index: "&amp;lt;valid index&amp;gt;"&lt;BR /&gt;&amp;nbsp; &amp;nbsp; tls:&lt;BR /&gt;&amp;nbsp; &amp;nbsp; &amp;nbsp; ca_file: "/etc/otel/config/certs/ca_bundle.cer"&lt;BR /&gt;&amp;nbsp; &amp;nbsp; telemetry:&lt;BR /&gt;&amp;nbsp; &amp;nbsp; &amp;nbsp; enabled: true&lt;BR /&gt;&amp;nbsp; &amp;nbsp; health_check_enabled: true&lt;BR /&gt;&amp;nbsp; &amp;nbsp; heartbeat:&lt;BR /&gt;&amp;nbsp; &amp;nbsp; &amp;nbsp; interval: 10s&lt;BR /&gt;service:&lt;BR /&gt;&amp;nbsp; pipelines:&lt;BR /&gt;&amp;nbsp; &amp;nbsp; logs:&lt;BR /&gt;&amp;nbsp; &amp;nbsp; &amp;nbsp; receivers: [otlp]&lt;BR /&gt;&amp;nbsp; &amp;nbsp; &amp;nbsp; processors: []&lt;BR /&gt;&amp;nbsp; &amp;nbsp; &amp;nbsp; exporters: [splunk_hec, debug]&lt;BR /&gt;&amp;nbsp; &amp;nbsp; telemetry:&lt;BR /&gt;&amp;nbsp; &amp;nbsp; &amp;nbsp; logs:&lt;BR /&gt;&amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; level: "debug"&lt;/P&gt;</description>
      <pubDate>Sat, 04 Nov 2023 13:57:32 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Getting-Data-In/Troubleshooting-SplunkHecExporter-in-opentelemetry-collector/m-p/667376#M111928</guid>
      <dc:creator>bschaap</dc:creator>
      <dc:date>2023-11-04T13:57:32Z</dc:date>
    </item>
    <item>
      <title>Re: Troubleshooting SplunkHecExporter in opentelemetry-collector-contrib</title>
      <link>https://community.splunk.com/t5/Getting-Data-In/Troubleshooting-SplunkHecExporter-in-opentelemetry-collector/m-p/667378#M111929</link>
      <description>&lt;P&gt;Confirm you see the HF's internal logs in Splunk Cloud (search for "&lt;FONT face="courier new,courier"&gt;index=_internal host=&amp;lt;&amp;lt;your HF name&amp;gt;&amp;gt;&lt;/FONT&gt;").&amp;nbsp; If you don't then the HF is not connecting to Splunk Cloud (did you install the Universal Forwarder app on the HF?) and that should be fixed first.&amp;nbsp; If the HF's logs are in the cloud then use them to determine why otel data is not getting in.&lt;/P&gt;</description>
      <pubDate>Sat, 04 Nov 2023 15:59:56 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Getting-Data-In/Troubleshooting-SplunkHecExporter-in-opentelemetry-collector/m-p/667378#M111929</guid>
      <dc:creator>richgalloway</dc:creator>
      <dc:date>2023-11-04T15:59:56Z</dc:date>
    </item>
    <item>
      <title>Re: Troubleshooting SplunkHecExporter in opentelemetry-collector-contrib</title>
      <link>https://community.splunk.com/t5/Getting-Data-In/Troubleshooting-SplunkHecExporter-in-opentelemetry-collector/m-p/667418#M111930</link>
      <description>&lt;P&gt;I reviewed the _internal index and discovered that the heartbeat records to the _internal index (the SplunkHECExporter code shows this too).&amp;nbsp; My HEC token doesn't allow that index and was erroring.&amp;nbsp;&lt;/P&gt;&lt;P&gt;This explains why the heartbeat wasn't working but I'm still unable to determine why my otlp logs aren't making it to Splunk via the exporter.&amp;nbsp; I reviewed the other _internal logs but am unable to find anything.&lt;/P&gt;&lt;P&gt;For additional context, I'm reusing an existing Splunk Heavy Forwarder that has many logs going through it.&amp;nbsp; This is the first time I've used the SplunkHecExporter exporter in the OtelCollector.&amp;nbsp; The debug logs show that splunk_hec is registered to export logs.&lt;/P&gt;</description>
      <pubDate>Sun, 05 Nov 2023 15:45:26 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Getting-Data-In/Troubleshooting-SplunkHecExporter-in-opentelemetry-collector/m-p/667418#M111930</guid>
      <dc:creator>bschaap</dc:creator>
      <dc:date>2023-11-05T15:45:26Z</dc:date>
    </item>
    <item>
      <title>Re: Troubleshooting SplunkHecExporter in opentelemetry-collector-contrib</title>
      <link>https://community.splunk.com/t5/Getting-Data-In/Troubleshooting-SplunkHecExporter-in-opentelemetry-collector/m-p/667534#M111942</link>
      <description>&lt;P&gt;&lt;a href="https://community.splunk.com/t5/user/viewprofilepage/user-id/213957"&gt;@richgalloway&lt;/a&gt;&amp;nbsp;&amp;nbsp; I discovered that sending the log to the raw endpoint works.&amp;nbsp; However, the log is stripped down to the log body which is what the &lt;A href="https://github.com/open-telemetry/opentelemetry-collector-contrib/tree/main/exporter/splunkhecexporter" target="_self"&gt;documentation states&lt;/A&gt; (ie. from docs - `&lt;SPAN&gt;send only the log's body`)&lt;/SPAN&gt;.&amp;nbsp;&amp;nbsp;&lt;/P&gt;&lt;P&gt;export_raw: false&lt;/P&gt;&lt;P&gt;endpoint: ".../services/collector/raw"&lt;/P&gt;&lt;P&gt;Resulting log (only the log body shows up in Splunk) -&lt;/P&gt;&lt;P&gt;&lt;SPAN class=""&gt;&lt;SPAN class=""&gt;&amp;nbsp; &amp;nbsp;Example&lt;/SPAN&gt;&lt;/SPAN&gt; &lt;SPAN class=""&gt;log&lt;/SPAN&gt; &lt;SPAN class=""&gt;record&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;I'm still having trouble figuring out why logs aren't coming through the normal event endpoint.&amp;nbsp; The sample log I'm using is from the &lt;A href="https://github.com/open-telemetry/opentelemetry-proto/blob/main/examples/logs.json" target="_self"&gt;otlp log data spec&lt;/A&gt;.&lt;/P&gt;</description>
      <pubDate>Mon, 06 Nov 2023 13:49:21 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Getting-Data-In/Troubleshooting-SplunkHecExporter-in-opentelemetry-collector/m-p/667534#M111942</guid>
      <dc:creator>bschaap</dc:creator>
      <dc:date>2023-11-06T13:49:21Z</dc:date>
    </item>
    <item>
      <title>Re: Troubleshooting SplunkHecExporter in opentelemetry-collector-contrib</title>
      <link>https://community.splunk.com/t5/Getting-Data-In/Troubleshooting-SplunkHecExporter-in-opentelemetry-collector/m-p/667547#M111943</link>
      <description>&lt;P&gt;Splunk HEC will not accept events on the /event endpoint if they are not valid JSON.&amp;nbsp; I believe an error will be returned in that case, however.&lt;/P&gt;</description>
      <pubDate>Mon, 06 Nov 2023 14:38:48 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Getting-Data-In/Troubleshooting-SplunkHecExporter-in-opentelemetry-collector/m-p/667547#M111943</guid>
      <dc:creator>richgalloway</dc:creator>
      <dc:date>2023-11-06T14:38:48Z</dc:date>
    </item>
    <item>
      <title>Re: Troubleshooting SplunkHecExporter in opentelemetry-collector-contrib</title>
      <link>https://community.splunk.com/t5/Getting-Data-In/Troubleshooting-SplunkHecExporter-in-opentelemetry-collector/m-p/667612#M111950</link>
      <description>&lt;P&gt;Ended up getting it to work using a different sample log from the app that will be submitting the OTLP logs.&amp;nbsp; For some reason the example in the otlp spec wouldn't work on the /event endpoint using Postman but would on the /raw endpoint.&amp;nbsp; Though with the /raw endpoint it was just the log body and not all the context around it.&amp;nbsp; Thanks for your help!&lt;/P&gt;</description>
      <pubDate>Mon, 06 Nov 2023 20:05:32 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Getting-Data-In/Troubleshooting-SplunkHecExporter-in-opentelemetry-collector/m-p/667612#M111950</guid>
      <dc:creator>bschaap</dc:creator>
      <dc:date>2023-11-06T20:05:32Z</dc:date>
    </item>
    <item>
      <title>Re: Troubleshooting SplunkHecExporter in opentelemetry-collector-contrib</title>
      <link>https://community.splunk.com/t5/Getting-Data-In/Troubleshooting-SplunkHecExporter-in-opentelemetry-collector/m-p/669675#M112279</link>
      <description>&lt;P&gt;&lt;a href="https://community.splunk.com/t5/user/viewprofilepage/user-id/63493"&gt;@bschaap&lt;/a&gt;&amp;nbsp;I'm also facing the same issue. I used that sample OTLP spec log json file. How did you fix it?&lt;/P&gt;</description>
      <pubDate>Fri, 24 Nov 2023 17:25:41 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Getting-Data-In/Troubleshooting-SplunkHecExporter-in-opentelemetry-collector/m-p/669675#M112279</guid>
      <dc:creator>Av2</dc:creator>
      <dc:date>2023-11-24T17:25:41Z</dc:date>
    </item>
    <item>
      <title>Re: Troubleshooting SplunkHecExporter in opentelemetry-collector-contrib</title>
      <link>https://community.splunk.com/t5/Getting-Data-In/Troubleshooting-SplunkHecExporter-in-opentelemetry-collector/m-p/669687#M112283</link>
      <description>&lt;P data-unlink="true"&gt;If I recall it worked when I sent test logs from my client app which is instrumented with the &lt;A href="https://github.com/grafana/faro-web-sdk" target="_self"&gt;Faro Web SDK&lt;/A&gt; library.&amp;nbsp; I didn't go back to compare the log contents against the otlp spec log to figure out the difference since it was working.&amp;nbsp; I think it was silently failing for some reason.&lt;/P&gt;</description>
      <pubDate>Fri, 24 Nov 2023 19:29:24 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Getting-Data-In/Troubleshooting-SplunkHecExporter-in-opentelemetry-collector/m-p/669687#M112283</guid>
      <dc:creator>bschaap</dc:creator>
      <dc:date>2023-11-24T19:29:24Z</dc:date>
    </item>
  </channel>
</rss>

