<?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: Shipping Beats/Logslash metrics to Dynatarec in Open Q&amp;A</title>
    <link>https://community.dynatrace.com/t5/Open-Q-A/Shipping-Beats-Logslash-metrics-to-Dynatarec/m-p/297905#M38910</link>
    <description>&lt;P&gt;&lt;A href="https://www.elastic.co/docs/reference/logstash/plugins/plugins-outputs-dynatrace" target="_self"&gt;https://www.elastic.co/docs/reference/logstash/plugins/plugins-outputs-dynatrace&lt;/A&gt;&amp;nbsp;&lt;BR /&gt;It was built exactly for this use case — it sends Logstash events directly to the Dynatrace Log Ingest API v2 (/api/v2/logs/ingest), so you don’t need to manually build HTTP requests or mappings.&lt;/P&gt;</description>
    <pubDate>Fri, 17 Apr 2026 10:21:10 GMT</pubDate>
    <dc:creator>t_pawlak</dc:creator>
    <dc:date>2026-04-17T10:21:10Z</dc:date>
    <item>
      <title>Shipping Beats/Logslash metrics to Dynatarec</title>
      <link>https://community.dynatrace.com/t5/Open-Q-A/Shipping-Beats-Logslash-metrics-to-Dynatarec/m-p/297903#M38908</link>
      <description>&lt;P&gt;Hello,&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Who can help me here?&amp;nbsp; I want to send Beats/Logstash metrics to&amp;nbsp;&lt;SPAN&gt;/api/v2/metrics/ingest&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;I can find a lot about logs and openpipeline but who knows how this is accomplished.&lt;/P&gt;&lt;P&gt;Maybe I am missing something or am I the first (-;&lt;/P&gt;&lt;P&gt;&lt;a href="https://community.dynatrace.com/t5/user/viewprofilepage/user-id/63534"&gt;@Cbeecher&lt;/a&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;KR Henk&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Fri, 17 Apr 2026 10:13:24 GMT</pubDate>
      <guid>https://community.dynatrace.com/t5/Open-Q-A/Shipping-Beats-Logslash-metrics-to-Dynatarec/m-p/297903#M38908</guid>
      <dc:creator>henk_stobbe</dc:creator>
      <dc:date>2026-04-17T10:13:24Z</dc:date>
    </item>
    <item>
      <title>Re: Shipping Beats/Logslash metrics to Dynatarec</title>
      <link>https://community.dynatrace.com/t5/Open-Q-A/Shipping-Beats-Logslash-metrics-to-Dynatarec/m-p/297904#M38909</link>
      <description>&lt;P&gt;Hi,&lt;/P&gt;&lt;P&gt;The simplest approach is to use the Dynatrace Logstash output plugin.&lt;/P&gt;&lt;P&gt;It should work&lt;/P&gt;&lt;P&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;/P&gt;</description>
      <pubDate>Fri, 17 Apr 2026 10:20:40 GMT</pubDate>
      <guid>https://community.dynatrace.com/t5/Open-Q-A/Shipping-Beats-Logslash-metrics-to-Dynatarec/m-p/297904#M38909</guid>
      <dc:creator>t_pawlak</dc:creator>
      <dc:date>2026-04-17T10:20:40Z</dc:date>
    </item>
    <item>
      <title>Re: Shipping Beats/Logslash metrics to Dynatarec</title>
      <link>https://community.dynatrace.com/t5/Open-Q-A/Shipping-Beats-Logslash-metrics-to-Dynatarec/m-p/297905#M38910</link>
      <description>&lt;P&gt;&lt;A href="https://www.elastic.co/docs/reference/logstash/plugins/plugins-outputs-dynatrace" target="_self"&gt;https://www.elastic.co/docs/reference/logstash/plugins/plugins-outputs-dynatrace&lt;/A&gt;&amp;nbsp;&lt;BR /&gt;It was built exactly for this use case — it sends Logstash events directly to the Dynatrace Log Ingest API v2 (/api/v2/logs/ingest), so you don’t need to manually build HTTP requests or mappings.&lt;/P&gt;</description>
      <pubDate>Fri, 17 Apr 2026 10:21:10 GMT</pubDate>
      <guid>https://community.dynatrace.com/t5/Open-Q-A/Shipping-Beats-Logslash-metrics-to-Dynatarec/m-p/297905#M38910</guid>
      <dc:creator>t_pawlak</dc:creator>
      <dc:date>2026-04-17T10:21:10Z</dc:date>
    </item>
    <item>
      <title>Re: Shipping Beats/Logslash metrics to Dynatarec</title>
      <link>https://community.dynatrace.com/t5/Open-Q-A/Shipping-Beats-Logslash-metrics-to-Dynatarec/m-p/297906#M38911</link>
      <description>&lt;P&gt;Just install plugin on logstash instance:&lt;/P&gt;&lt;LI-CODE lang="markup"&gt;bin/logstash-plugin install logstash-output-dynatrace&lt;/LI-CODE&gt;&lt;P&gt;And add this in output in config:&lt;/P&gt;&lt;LI-CODE lang="markup"&gt;output {
  dynatrace {
    url =&amp;gt; "https://{environmentid}.live.dynatrace.com/api/v2/logs/ingest"
    api_token =&amp;gt; "YOUR_TOKEN"
  }
}&lt;/LI-CODE&gt;</description>
      <pubDate>Fri, 17 Apr 2026 10:23:09 GMT</pubDate>
      <guid>https://community.dynatrace.com/t5/Open-Q-A/Shipping-Beats-Logslash-metrics-to-Dynatarec/m-p/297906#M38911</guid>
      <dc:creator>t_pawlak</dc:creator>
      <dc:date>2026-04-17T10:23:09Z</dc:date>
    </item>
    <item>
      <title>Re: Shipping Beats/Logslash metrics to Dynatarec</title>
      <link>https://community.dynatrace.com/t5/Open-Q-A/Shipping-Beats-Logslash-metrics-to-Dynatarec/m-p/297908#M38913</link>
      <description>&lt;P&gt;Hi Pawlak,&lt;/P&gt;&lt;P&gt;Are you sure for metrics also?&lt;/P&gt;&lt;P&gt;KR Henk&lt;/P&gt;</description>
      <pubDate>Fri, 17 Apr 2026 10:28:57 GMT</pubDate>
      <guid>https://community.dynatrace.com/t5/Open-Q-A/Shipping-Beats-Logslash-metrics-to-Dynatarec/m-p/297908#M38913</guid>
      <dc:creator>henk_stobbe</dc:creator>
      <dc:date>2026-04-17T10:28:57Z</dc:date>
    </item>
    <item>
      <title>Re: Shipping Beats/Logslash metrics to Dynatarec</title>
      <link>https://community.dynatrace.com/t5/Open-Q-A/Shipping-Beats-Logslash-metrics-to-Dynatarec/m-p/297915#M38914</link>
      <description>&lt;P&gt;Sorry,&lt;BR /&gt;I saw Logstash and immediately focused on logs, not metrics.&lt;BR /&gt;In this case, IMO you should use an OpenTelemetry Collector and send them via OTLP, which is probably the cleaner long-term approach.&lt;BR /&gt;I think&amp;nbsp;a native Metricbeat --&amp;gt; OTLP/HTTP path here without an additional bridge is not possible&lt;/P&gt;</description>
      <pubDate>Fri, 17 Apr 2026 10:59:18 GMT</pubDate>
      <guid>https://community.dynatrace.com/t5/Open-Q-A/Shipping-Beats-Logslash-metrics-to-Dynatarec/m-p/297915#M38914</guid>
      <dc:creator>t_pawlak</dc:creator>
      <dc:date>2026-04-17T10:59:18Z</dc:date>
    </item>
    <item>
      <title>Re: Shipping Beats/Logslash metrics to Dynatarec</title>
      <link>https://community.dynatrace.com/t5/Open-Q-A/Shipping-Beats-Logslash-metrics-to-Dynatarec/m-p/297932#M38916</link>
      <description>&lt;P&gt;Hi&amp;nbsp;&lt;a href="https://community.dynatrace.com/t5/user/viewprofilepage/user-id/42367"&gt;@t_pawlak&lt;/a&gt;&amp;nbsp;if that was not an option could you format the elastic JSON in to an http message and send to the Dynatrace API end point? Or is that a no go&lt;/P&gt;&lt;P&gt;Thanks&lt;/P&gt;&lt;P&gt;Caroline&lt;/P&gt;</description>
      <pubDate>Fri, 17 Apr 2026 14:18:33 GMT</pubDate>
      <guid>https://community.dynatrace.com/t5/Open-Q-A/Shipping-Beats-Logslash-metrics-to-Dynatarec/m-p/297932#M38916</guid>
      <dc:creator>CSBee</dc:creator>
      <dc:date>2026-04-17T14:18:33Z</dc:date>
    </item>
    <item>
      <title>Re: Shipping Beats/Logslash metrics to Dynatarec</title>
      <link>https://community.dynatrace.com/t5/Open-Q-A/Shipping-Beats-Logslash-metrics-to-Dynatarec/m-p/297938#M38917</link>
      <description>&lt;P&gt;Hi,&lt;BR /&gt;Technically, it’s possible, but is it worth it?&lt;BR /&gt;Dynatrace metrics ingest doesn’t accept raw JSON, so you first need to transform it into the Dynatrace metric ingestion format. It can be done with Logstash + HTTP output, but it requires custom mapping.&lt;BR /&gt;That’s also why I mentioned OpenTelemetry, it handles the transformation and protocol side for you, which makes it easier to maintain in the long run.&lt;/P&gt;</description>
      <pubDate>Fri, 17 Apr 2026 14:47:26 GMT</pubDate>
      <guid>https://community.dynatrace.com/t5/Open-Q-A/Shipping-Beats-Logslash-metrics-to-Dynatarec/m-p/297938#M38917</guid>
      <dc:creator>t_pawlak</dc:creator>
      <dc:date>2026-04-17T14:47:26Z</dc:date>
    </item>
  </channel>
</rss>

