<?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 Open Telemetry Errors in Windows in Getting Data In</title>
    <link>https://community.splunk.com/t5/Getting-Data-In/Open-Telemetry-Errors-in-Windows/m-p/666834#M111872</link>
    <description>&lt;P&gt;Getting a ton of these Telemetry errors in Event Log of a windows server with at UF installed. They started a few days ago. What could be causing them? No changes have been made to the UF or splunk infrastructure recently.&lt;BR /&gt;&lt;BR /&gt;&lt;/P&gt;&lt;DIV&gt;1.6987038408387303e+09 error exporterhelper/queued_retry.go:183 Exporting failed. The error is not retryable. Dropping data. {"kind": "exporter", "name": "signalfx", "error": "Permanent error: \"HTTP/2.0 401 Unauthorized\\r\\nContent-Length: 0\\r\\nDate: Mon, 30 Oct 2023 22:10:40 GMT\\r\\nServer: istio-envoy\\r\\nWww-Authenticate: Basic realm=\\\"Splunk\\\"\\r\\nX-Envoy-Upstream-Service-Time: 5\\r\\n\\r\\n\"", "dropped_items": 50}&lt;/DIV&gt;&lt;DIV&gt;go.opentelemetry.io/collector/exporter/exporterhelper.(*retrySender).send&lt;/DIV&gt;&lt;DIV&gt;&lt;SPAN&gt;/builds/o11y-gdi/splunk-otel-collector-releaser/.go/pkg/mod/go.opentelemetry.io/collector@v0.53.0/exporter/exporterhelper/queued_retry.go:183&lt;/SPAN&gt;&lt;/DIV&gt;&lt;DIV&gt;go.opentelemetry.io/collector/exporter/exporterhelper.(*metricsSenderWithObservability).send&lt;/DIV&gt;&lt;DIV&gt;&lt;SPAN&gt;/builds/o11y-gdi/splunk-otel-collector-releaser/.go/pkg/mod/go.opentelemetry.io/collector@v0.53.0/exporter/exporterhelper/metrics.go:132&lt;/SPAN&gt;&lt;/DIV&gt;&lt;DIV&gt;go.opentelemetry.io/collector/exporter/exporterhelper.(*queuedRetrySender).start.func1&lt;/DIV&gt;&lt;DIV&gt;&lt;SPAN&gt;/builds/o11y-gdi/splunk-otel-collector-releaser/.go/pkg/mod/go.opentelemetry.io/collector@v0.53.0/exporter/exporterhelper/queued_retry_inmemory.go:119&lt;/SPAN&gt;&lt;/DIV&gt;&lt;DIV&gt;go.opentelemetry.io/collector/exporter/exporterhelper/internal.consumerFunc.consume&lt;/DIV&gt;&lt;DIV&gt;&lt;SPAN&gt;/builds/o11y-gdi/splunk-otel-collector-releaser/.go/pkg/mod/go.opentelemetry.io/collector@v0.53.0/exporter/exporterhelper/internal/bounded_memory_queue.go:82&lt;/SPAN&gt;&lt;/DIV&gt;&lt;DIV&gt;go.opentelemetry.io/collector/exporter/exporterhelper/internal.(*boundedMemoryQueue).StartConsumers.func2&lt;/DIV&gt;&lt;DIV&gt;&lt;SPAN&gt;/builds/o11y-gdi/splunk-otel-collector-releaser/.go/pkg/mod/go.opentelemetry.io/collector@v0.53.0/exporter/exporterhelper/internal/bounded_memory_queue.go:69&lt;/SPAN&gt;&lt;/DIV&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
    <pubDate>Mon, 30 Oct 2023 22:38:14 GMT</pubDate>
    <dc:creator>Dominic32</dc:creator>
    <dc:date>2023-10-30T22:38:14Z</dc:date>
    <item>
      <title>Open Telemetry Errors in Windows</title>
      <link>https://community.splunk.com/t5/Getting-Data-In/Open-Telemetry-Errors-in-Windows/m-p/666834#M111872</link>
      <description>&lt;P&gt;Getting a ton of these Telemetry errors in Event Log of a windows server with at UF installed. They started a few days ago. What could be causing them? No changes have been made to the UF or splunk infrastructure recently.&lt;BR /&gt;&lt;BR /&gt;&lt;/P&gt;&lt;DIV&gt;1.6987038408387303e+09 error exporterhelper/queued_retry.go:183 Exporting failed. The error is not retryable. Dropping data. {"kind": "exporter", "name": "signalfx", "error": "Permanent error: \"HTTP/2.0 401 Unauthorized\\r\\nContent-Length: 0\\r\\nDate: Mon, 30 Oct 2023 22:10:40 GMT\\r\\nServer: istio-envoy\\r\\nWww-Authenticate: Basic realm=\\\"Splunk\\\"\\r\\nX-Envoy-Upstream-Service-Time: 5\\r\\n\\r\\n\"", "dropped_items": 50}&lt;/DIV&gt;&lt;DIV&gt;go.opentelemetry.io/collector/exporter/exporterhelper.(*retrySender).send&lt;/DIV&gt;&lt;DIV&gt;&lt;SPAN&gt;/builds/o11y-gdi/splunk-otel-collector-releaser/.go/pkg/mod/go.opentelemetry.io/collector@v0.53.0/exporter/exporterhelper/queued_retry.go:183&lt;/SPAN&gt;&lt;/DIV&gt;&lt;DIV&gt;go.opentelemetry.io/collector/exporter/exporterhelper.(*metricsSenderWithObservability).send&lt;/DIV&gt;&lt;DIV&gt;&lt;SPAN&gt;/builds/o11y-gdi/splunk-otel-collector-releaser/.go/pkg/mod/go.opentelemetry.io/collector@v0.53.0/exporter/exporterhelper/metrics.go:132&lt;/SPAN&gt;&lt;/DIV&gt;&lt;DIV&gt;go.opentelemetry.io/collector/exporter/exporterhelper.(*queuedRetrySender).start.func1&lt;/DIV&gt;&lt;DIV&gt;&lt;SPAN&gt;/builds/o11y-gdi/splunk-otel-collector-releaser/.go/pkg/mod/go.opentelemetry.io/collector@v0.53.0/exporter/exporterhelper/queued_retry_inmemory.go:119&lt;/SPAN&gt;&lt;/DIV&gt;&lt;DIV&gt;go.opentelemetry.io/collector/exporter/exporterhelper/internal.consumerFunc.consume&lt;/DIV&gt;&lt;DIV&gt;&lt;SPAN&gt;/builds/o11y-gdi/splunk-otel-collector-releaser/.go/pkg/mod/go.opentelemetry.io/collector@v0.53.0/exporter/exporterhelper/internal/bounded_memory_queue.go:82&lt;/SPAN&gt;&lt;/DIV&gt;&lt;DIV&gt;go.opentelemetry.io/collector/exporter/exporterhelper/internal.(*boundedMemoryQueue).StartConsumers.func2&lt;/DIV&gt;&lt;DIV&gt;&lt;SPAN&gt;/builds/o11y-gdi/splunk-otel-collector-releaser/.go/pkg/mod/go.opentelemetry.io/collector@v0.53.0/exporter/exporterhelper/internal/bounded_memory_queue.go:69&lt;/SPAN&gt;&lt;/DIV&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Mon, 30 Oct 2023 22:38:14 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Getting-Data-In/Open-Telemetry-Errors-in-Windows/m-p/666834#M111872</guid>
      <dc:creator>Dominic32</dc:creator>
      <dc:date>2023-10-30T22:38:14Z</dc:date>
    </item>
    <item>
      <title>Re: Open Telemetry Errors in Windows</title>
      <link>https://community.splunk.com/t5/Getting-Data-In/Open-Telemetry-Errors-in-Windows/m-p/667028#M111893</link>
      <description>&lt;P&gt;Error was being caused by the OpenTelemetry Collector service, which is separate from the Splunk UF service. I stopped the service and errors are no longer being logged in Event Viewer.&lt;/P&gt;</description>
      <pubDate>Wed, 01 Nov 2023 15:36:52 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Getting-Data-In/Open-Telemetry-Errors-in-Windows/m-p/667028#M111893</guid>
      <dc:creator>Dominic32</dc:creator>
      <dc:date>2023-11-01T15:36:52Z</dc:date>
    </item>
  </channel>
</rss>

