<?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: What are the differences between OpenTelemetry Collector (otel) and Splunk Connect for Kubernetes? in Getting Data In</title>
    <link>https://community.splunk.com/t5/Getting-Data-In/What-are-the-differences-between-OpenTelemetry-Collector-otel/m-p/649933#M110451</link>
    <description>&lt;P&gt;Here's a link on the migration/differences provided on the Slack channel #opentelemetry:&amp;nbsp;&lt;A href="https://github.com/signalfx/splunk-otel-collector-chart/blob/main/docs/migration-from-sck.md#extracted-fields-for-logs" target="_blank"&gt;splunk-otel-collector-chart/docs/migration-from-sck.md at main · signalfx/splunk-otel-collector-chart · GitHub&lt;/A&gt;&lt;/P&gt;</description>
    <pubDate>Tue, 11 Jul 2023 07:26:49 GMT</pubDate>
    <dc:creator>stefan_habuline</dc:creator>
    <dc:date>2023-07-11T07:26:49Z</dc:date>
    <item>
      <title>What are the differences between OpenTelemetry Collector (otel) and Splunk Connect for Kubernetes?</title>
      <link>https://community.splunk.com/t5/Getting-Data-In/What-are-the-differences-between-OpenTelemetry-Collector-otel/m-p/648536#M110248</link>
      <description>&lt;P&gt;Hi all,&lt;/P&gt;
&lt;P&gt;We're migrating from&amp;nbsp;Splunk Connect for Kubernetes to&amp;nbsp;OpenTelemetry Collector (otel) and noticed several differences, which are breaking our dashboards.&lt;/P&gt;
&lt;P&gt;For example, to get the pods information (k8sObjects) from the otel collector, we have to search them with&lt;/P&gt;
&lt;P&gt;&lt;EM&gt;sourcetype="kube:object:pods"&lt;/EM&gt;&lt;/P&gt;
&lt;P&gt;However from Splunk Connect it's&lt;/P&gt;
&lt;P&gt;&lt;EM&gt;sourcetype="kube:objects:pods"&lt;/EM&gt;&lt;/P&gt;
&lt;P&gt;Notice the plural in object&lt;STRONG&gt;s&lt;/STRONG&gt;.&lt;/P&gt;
&lt;P&gt;Another example is the pod field, which is different in the otel collector:&lt;/P&gt;
&lt;P&gt;Splunk Connect:&amp;nbsp;&lt;EM&gt;&lt;STRONG&gt;pod&lt;/STRONG&gt;::*$STRING*&lt;/EM&gt;&lt;BR /&gt;Otel:&amp;nbsp;&lt;EM&gt;&lt;STRONG&gt;source&lt;/STRONG&gt;::*$STRING*&lt;/EM&gt;&lt;/P&gt;
&lt;P&gt;Is there a way how to align the Otel Collector to the above mentioned format? Or there some sort of list of the complete differences between otel and Splunk Connect?&lt;/P&gt;
&lt;P&gt;We have quite a lot productive dashboards and report and it would take big effort to change/check every single of them.&lt;/P&gt;
&lt;P&gt;Thanks much for help in advance.&lt;/P&gt;
&lt;P&gt;Stefan&lt;/P&gt;</description>
      <pubDate>Fri, 30 Jun 2023 15:06:26 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Getting-Data-In/What-are-the-differences-between-OpenTelemetry-Collector-otel/m-p/648536#M110248</guid>
      <dc:creator>stefan_habuline</dc:creator>
      <dc:date>2023-06-30T15:06:26Z</dc:date>
    </item>
    <item>
      <title>Re: What are the differences between OpenTelemetry Collector (otel) and Splunk Connect for Kubernetes?</title>
      <link>https://community.splunk.com/t5/Getting-Data-In/What-are-the-differences-between-OpenTelemetry-Collector-otel/m-p/649933#M110451</link>
      <description>&lt;P&gt;Here's a link on the migration/differences provided on the Slack channel #opentelemetry:&amp;nbsp;&lt;A href="https://github.com/signalfx/splunk-otel-collector-chart/blob/main/docs/migration-from-sck.md#extracted-fields-for-logs" target="_blank"&gt;splunk-otel-collector-chart/docs/migration-from-sck.md at main · signalfx/splunk-otel-collector-chart · GitHub&lt;/A&gt;&lt;/P&gt;</description>
      <pubDate>Tue, 11 Jul 2023 07:26:49 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Getting-Data-In/What-are-the-differences-between-OpenTelemetry-Collector-otel/m-p/649933#M110451</guid>
      <dc:creator>stefan_habuline</dc:creator>
      <dc:date>2023-07-11T07:26:49Z</dc:date>
    </item>
  </channel>
</rss>

