<?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 is OpenPipeline? in Open Q&amp;A</title>
    <link>https://community.dynatrace.com/t5/Open-Q-A/What-is-OpenPipeline/m-p/260023#M34345</link>
    <description>&lt;P&gt;OpenPipeline is Dynatrace's platform component to handle ingestion of all data types - whether observability, security or business data - for any source and format. It's built for very large scale and deeply integrated into the Dynatrace platform.&lt;/P&gt;
&lt;P&gt;The OpenPipeline gives access to all configuration related to ingestion of data - that's different from "capturing data", so OneAgent configuration is not part of OpenPipeline.&lt;/P&gt;
&lt;P&gt;Configuration in the OpenPipeline is split into data types: logs, events, Application Security,... (the coverage will continuously be extended).&lt;/P&gt;
&lt;P&gt;Within each data type there are tabs for &lt;EM&gt;Ingest sources&lt;/EM&gt;, &lt;EM&gt;Dynamic routing&lt;/EM&gt; and &lt;EM&gt;Pipelines&lt;/EM&gt;.&lt;/P&gt;
&lt;UL&gt;
&lt;LI&gt;&lt;EM&gt;Ingest sources&lt;/EM&gt; represent how data enters Dynatrace. &lt;SPAN&gt;This could be an HTTP endpoint, OneAgent, OTLP endpoint, extension, or similar, such as OpenTelemetry Collector or Data Acquisition Controller&lt;/SPAN&gt;. Endpoints can receive from any data collectors, such as OpenTelemetry, FluentD, custom services…&lt;/LI&gt;
&lt;LI&gt;&lt;EM&gt;Pipelines&lt;/EM&gt; encapsulate all processing, data extraction and storage assignment - hence also sensitive data handling and security. Here masking, transformation, filtering, adding/removing/renaming fields, extracting metrics or bizevent and much more is configured.&lt;/LI&gt;
&lt;LI&gt;&lt;EM&gt;Routing&lt;/EM&gt; decides for each record from each source to which pipeline it should go. This can be as fine-grained or coarse as needed, depending on how the customer organization is set up.&lt;/LI&gt;
&lt;/UL&gt;
&lt;P&gt;We're constantly adding new features to OpenPipeline and making configuration more convenient. So stay tuned via blog posts and release notes.&lt;/P&gt;</description>
    <pubDate>Thu, 14 Aug 2025 07:47:45 GMT</pubDate>
    <dc:creator>thomas_billi</dc:creator>
    <dc:date>2025-08-14T07:47:45Z</dc:date>
    <item>
      <title>What is OpenPipeline?</title>
      <link>https://community.dynatrace.com/t5/Open-Q-A/What-is-OpenPipeline/m-p/260022#M34344</link>
      <description>&lt;P&gt;&lt;SPAN class="TextRun SCXW44959634 BCX0" data-contrast="auto"&gt;&lt;SPAN class="NormalTextRun SCXW44959634 BCX0"&gt;From a user perspective, I'd like to know what I can use the new &lt;/SPAN&gt;&lt;SPAN class="NormalTextRun SpellingErrorV2Themed SCXW44959634 BCX0"&gt;OpenPipeline&lt;/SPAN&gt;&lt;SPAN class="NormalTextRun SCXW44959634 BCX0"&gt;&amp;nbsp;for.&lt;/SPAN&gt;&lt;/SPAN&gt;&lt;SPAN class="EOP SCXW44959634 BCX0" data-ccp-props="{}"&gt;&amp;nbsp;&lt;/SPAN&gt;&lt;/P&gt;</description>
      <pubDate>Thu, 14 Aug 2025 07:48:02 GMT</pubDate>
      <guid>https://community.dynatrace.com/t5/Open-Q-A/What-is-OpenPipeline/m-p/260022#M34344</guid>
      <dc:creator>GosiaMurawska</dc:creator>
      <dc:date>2025-08-14T07:48:02Z</dc:date>
    </item>
    <item>
      <title>Re: What is OpenPipeline?</title>
      <link>https://community.dynatrace.com/t5/Open-Q-A/What-is-OpenPipeline/m-p/260023#M34345</link>
      <description>&lt;P&gt;OpenPipeline is Dynatrace's platform component to handle ingestion of all data types - whether observability, security or business data - for any source and format. It's built for very large scale and deeply integrated into the Dynatrace platform.&lt;/P&gt;
&lt;P&gt;The OpenPipeline gives access to all configuration related to ingestion of data - that's different from "capturing data", so OneAgent configuration is not part of OpenPipeline.&lt;/P&gt;
&lt;P&gt;Configuration in the OpenPipeline is split into data types: logs, events, Application Security,... (the coverage will continuously be extended).&lt;/P&gt;
&lt;P&gt;Within each data type there are tabs for &lt;EM&gt;Ingest sources&lt;/EM&gt;, &lt;EM&gt;Dynamic routing&lt;/EM&gt; and &lt;EM&gt;Pipelines&lt;/EM&gt;.&lt;/P&gt;
&lt;UL&gt;
&lt;LI&gt;&lt;EM&gt;Ingest sources&lt;/EM&gt; represent how data enters Dynatrace. &lt;SPAN&gt;This could be an HTTP endpoint, OneAgent, OTLP endpoint, extension, or similar, such as OpenTelemetry Collector or Data Acquisition Controller&lt;/SPAN&gt;. Endpoints can receive from any data collectors, such as OpenTelemetry, FluentD, custom services…&lt;/LI&gt;
&lt;LI&gt;&lt;EM&gt;Pipelines&lt;/EM&gt; encapsulate all processing, data extraction and storage assignment - hence also sensitive data handling and security. Here masking, transformation, filtering, adding/removing/renaming fields, extracting metrics or bizevent and much more is configured.&lt;/LI&gt;
&lt;LI&gt;&lt;EM&gt;Routing&lt;/EM&gt; decides for each record from each source to which pipeline it should go. This can be as fine-grained or coarse as needed, depending on how the customer organization is set up.&lt;/LI&gt;
&lt;/UL&gt;
&lt;P&gt;We're constantly adding new features to OpenPipeline and making configuration more convenient. So stay tuned via blog posts and release notes.&lt;/P&gt;</description>
      <pubDate>Thu, 14 Aug 2025 07:47:45 GMT</pubDate>
      <guid>https://community.dynatrace.com/t5/Open-Q-A/What-is-OpenPipeline/m-p/260023#M34345</guid>
      <dc:creator>thomas_billi</dc:creator>
      <dc:date>2025-08-14T07:47:45Z</dc:date>
    </item>
  </channel>
</rss>

