<?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 Splunk Observability platform integration with Dynatrace in Automations</title>
    <link>https://community.dynatrace.com/t5/Automations/Splunk-Observability-platform-integration-with-Dynatrace/m-p/281599#M2272</link>
    <description>&lt;P&gt;Looking to understand the integration patterns for receiving data (metrics, logs) from Splunk and incorporating into Dynatrace dashboards.&lt;/P&gt;</description>
    <pubDate>Tue, 15 Jul 2025 18:13:36 GMT</pubDate>
    <dc:creator>dsteinbrick</dc:creator>
    <dc:date>2025-07-15T18:13:36Z</dc:date>
    <item>
      <title>Splunk Observability platform integration with Dynatrace</title>
      <link>https://community.dynatrace.com/t5/Automations/Splunk-Observability-platform-integration-with-Dynatrace/m-p/281599#M2272</link>
      <description>&lt;P&gt;Looking to understand the integration patterns for receiving data (metrics, logs) from Splunk and incorporating into Dynatrace dashboards.&lt;/P&gt;</description>
      <pubDate>Tue, 15 Jul 2025 18:13:36 GMT</pubDate>
      <guid>https://community.dynatrace.com/t5/Automations/Splunk-Observability-platform-integration-with-Dynatrace/m-p/281599#M2272</guid>
      <dc:creator>dsteinbrick</dc:creator>
      <dc:date>2025-07-15T18:13:36Z</dc:date>
    </item>
    <item>
      <title>Re: Splunk Observability platform integration with Dynatrace</title>
      <link>https://community.dynatrace.com/t5/Automations/Splunk-Observability-platform-integration-with-Dynatrace/m-p/281606#M2273</link>
      <description>&lt;P&gt;Hi&amp;nbsp;&lt;a href="https://community.dynatrace.com/t5/user/viewprofilepage/user-id/93385"&gt;@dsteinbrick&lt;/a&gt;&amp;nbsp;,&amp;nbsp; there is no direct integration, and it's going to be messy either way.&lt;BR /&gt;Realistically this needs to be done at the collection point rather than export - especially for the big 3 metrics, logs and traces.&amp;nbsp;&lt;BR /&gt;&lt;BR /&gt;For this I'd suggest option 2 - it will just make life so much easier.&amp;nbsp; &amp;nbsp;&lt;BR /&gt;&lt;BR /&gt;Last time I checked Splunk only had minimal capabilities of streaming data as an export to 3rd parties.&amp;nbsp; &amp;nbsp;Maybe there is something on Splunk base that could do this.&amp;nbsp; There is a dynatrace add on, that can send metrics, problems .. to splunk *(does not cover logs or traces)&amp;nbsp;&amp;nbsp;&lt;BR /&gt;&lt;BR /&gt;If you're after events only, then this is easy -&amp;gt; standard search query with alert &amp;amp; use option 1 or the events api as an endpoint for the alert to send to.&amp;nbsp;You could possibly extend this to certain scheduled searches.&amp;nbsp; &amp;nbsp;&lt;BR /&gt;&lt;BR /&gt;For the big 3&lt;BR /&gt;&lt;BR /&gt;1. use the&amp;nbsp;&lt;A href="https://docs.dynatrace.com/docs/discover-dynatrace/platform/openpipeline" target="_blank"&gt;OpenPipeline — Dynatrace Docs&lt;/A&gt;&amp;nbsp;to ingest data and export from Splunk (you'll need to figure that part out)&lt;BR /&gt;&lt;BR /&gt;2. Adding a Dynatrace exporter to the Splunk OTEL collector (I'm assuming you are using this since you mentioned Splunk observability).&amp;nbsp; you can dual stream to both Dynatrace and Splunk.&amp;nbsp; benefit here is that you get raw data and it's going to be able to be used directly in dynatrace.&amp;nbsp;&lt;BR /&gt;e.g&lt;/P&gt;&lt;LI-CODE lang="markup"&gt;apiVersion: v1
kind: ConfigMap
metadata:
  name: otel-collector-config
  namespace: observability
  labels:
    app: otel-collector
data:
  otel-collector-config.yaml: |
    receivers:
      otlphttp:
        endpoint: 0.0.0.0:4318

    exporters:
      splunk_hec:
        token: "&amp;lt;your-splunk-hec-token&amp;gt;"
        endpoint: "https://&amp;lt;your-splunk-hec-endpoint&amp;gt;"
        source: "otel"
        sourcetype: "_json"
        index: "main"
        disable_compression: false
        max_connections: 20
        timeout: 10s

      dynatrace:
        api_token: "&amp;lt;your-dynatrace-api-token&amp;gt;"
        endpoint: "https://&amp;lt;your-dynatrace-endpoint&amp;gt;/api/v2/otlp"
        tls:
          insecure: false

    processors:
      batch:
        timeout: 5s
        send_batch_size: 512

    service:
      pipelines:
        traces:
          receivers: [otlphttp]
          processors: [batch]
          exporters: [splunk_hec, dynatrace]

        metrics:
          receivers: [otlphttp]
          processors: [batch]
          exporters: [splunk_hec, dynatrace]

        logs:
          receivers: [otlphttp]
          processors: [batch]
          exporters: [splunk_hec, dynatrace]&lt;/LI-CODE&gt;&lt;P&gt;&lt;BR /&gt;If your not using the splunk otel collector, you could also possibly try and fudge a heavy forwarder to send to the open pipeline by using the HEC configuration.&amp;nbsp;&lt;BR /&gt;be the guineapig&amp;nbsp;&lt;span class="lia-unicode-emoji" title=":grinning_face:"&gt;😀&lt;/span&gt;&lt;BR /&gt;&lt;BR /&gt;Enjoy&lt;/P&gt;</description>
      <pubDate>Tue, 15 Jul 2025 21:20:20 GMT</pubDate>
      <guid>https://community.dynatrace.com/t5/Automations/Splunk-Observability-platform-integration-with-Dynatrace/m-p/281606#M2273</guid>
      <dc:creator>gopher</dc:creator>
      <dc:date>2025-07-15T21:20:20Z</dc:date>
    </item>
  </channel>
</rss>

