<?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 Unity AI Gateway OTel to other collectors in Administration &amp; Architecture</title>
    <link>https://community.databricks.com/t5/administration-architecture/shipping-unity-ai-gateway-otel-to-other-collectors/m-p/161214#M5383</link>
    <description>&lt;P class="wnfdntt _1ibi0s3f5 _1ibi0s3ce _1ibi0s3ea" data-pm-slice="1 1 []"&gt;Thanks for raising this. Based on the current public documentation, Unity AI Gateway’s documented OpenTelemetry path for coding-agent telemetry is to Databricks-managed Unity Catalog Delta tables, rather than to an arbitrary external OTel collector.&lt;/P&gt;
&lt;P class="wnfdntt _1ibi0s3f5 _1ibi0s3ce _1ibi0s3ea"&gt;The setup shown in the docs uses Databricks OTLP endpoints such as &lt;CODE&gt;/api/2.0/otel/v1/metrics&lt;/CODE&gt; and &lt;CODE&gt;/api/2.0/otel/v1/logs&lt;/CODE&gt;, with the Unity Catalog destination table specified through the &lt;CODE&gt;X-Databricks-UC-Table-Name&lt;/CODE&gt; header.&lt;/P&gt;
&lt;P class="wnfdntt _1ibi0s3f5 _1ibi0s3ce _1ibi0s3ea"&gt;You may be remembering MLflow tracing, which is documented separately and does support exporting to an OpenTelemetry Collector. That documentation explicitly describes both “OpenTelemetry only” and “Dual export” modes.&lt;/P&gt;
&lt;P class="wnfdntt _1ibi0s3f5 _1ibi0s3ce _1ibi0s3ea"&gt;Relevant docs:&lt;/P&gt;
&lt;UL class="wnfdnte" dir="auto"&gt;
&lt;LI class="wnfdntd _1ibi0s33w" dir="auto"&gt;
&lt;P class="wnfdntt _1ibi0s3f5 _1ibi0s3ce _1ibi0s3ea"&gt;Unity AI Gateway coding-agent OTel setup: &lt;A href="https://docs.databricks.com/aws/en/ai-gateway/coding-agent-integration-model-services" rel="noopener noreferrer nofollow" target="_blank"&gt;Integrate with coding agents&lt;/A&gt;&lt;/P&gt;
&lt;/LI&gt;
&lt;LI class="wnfdntd _1ibi0s33w" dir="auto"&gt;
&lt;P class="wnfdntt _1ibi0s3f5 _1ibi0s3ce _1ibi0s3ea"&gt;MLflow tracing OTel export: &lt;A href="https://docs.databricks.com/aws/en/mlflow3/genai/tracing/integrations/open-telemetry" rel="noopener noreferrer nofollow" target="_blank"&gt;OpenTelemetry Export&lt;/A&gt;&lt;/P&gt;
&lt;/LI&gt;
&lt;/UL&gt;
&lt;P class="wnfdntt _1ibi0s3f5 _1ibi0s3ce _1ibi0s3ea"&gt;So the short answer is: not as a documented Unity AI Gateway capability today, but Databricks does document external OTel collector export for MLflow tracing.&lt;/P&gt;</description>
    <pubDate>Thu, 02 Jul 2026 14:25:17 GMT</pubDate>
    <dc:creator>yogeshsingh</dc:creator>
    <dc:date>2026-07-02T14:25:17Z</dc:date>
    <item>
      <title>Shipping Unity AI Gateway OTel to other collectors</title>
      <link>https://community.databricks.com/t5/administration-architecture/shipping-unity-ai-gateway-otel-to-other-collectors/m-p/161212#M5381</link>
      <description>&lt;P&gt;We've enabled Open Telemetry logs in our Unity AI Gateway and have them shipped to Unity Catalog tables, but I am curious if we can configure the gateway to ship OTel to any other collector?&amp;nbsp; I could swear at one time I saw documentation for that but I can't find it now.&lt;/P&gt;</description>
      <pubDate>Thu, 02 Jul 2026 13:55:08 GMT</pubDate>
      <guid>https://community.databricks.com/t5/administration-architecture/shipping-unity-ai-gateway-otel-to-other-collectors/m-p/161212#M5381</guid>
      <dc:creator>Rjdudley</dc:creator>
      <dc:date>2026-07-02T13:55:08Z</dc:date>
    </item>
    <item>
      <title>Re: Shipping Unity AI Gateway OTel to other collectors</title>
      <link>https://community.databricks.com/t5/administration-architecture/shipping-unity-ai-gateway-otel-to-other-collectors/m-p/161213#M5382</link>
      <description>&lt;P&gt;Unity AI Gateway currently only supports logging to Unity Catalog &lt;STRONG&gt;Delta&lt;/STRONG&gt; tables.&lt;/P&gt;&lt;P&gt;You can read the data that lands in Unity Catalog tables and follow below&lt;/P&gt;&lt;OL&gt;&lt;LI&gt;Query the inference table periodically and forward the data to the &lt;STRONG&gt;external collector&lt;/STRONG&gt;&lt;/LI&gt;&lt;LI&gt;Set up a &lt;STRONG&gt;streaming&lt;/STRONG&gt; pipeline that reads from the Delta table and pushes to the OTel collector&lt;/LI&gt;&lt;LI&gt;Plan a &lt;STRONG&gt;scheduled export&lt;/STRONG&gt; to send the data to the observability platform or use Delta Sharing&lt;/LI&gt;&lt;/OL&gt;&lt;P&gt;You can suggest it as a addition of&amp;nbsp;&lt;SPAN&gt;feature on Databricks Ideas portal&lt;/SPAN&gt;&lt;/P&gt;</description>
      <pubDate>Thu, 02 Jul 2026 14:25:14 GMT</pubDate>
      <guid>https://community.databricks.com/t5/administration-architecture/shipping-unity-ai-gateway-otel-to-other-collectors/m-p/161213#M5382</guid>
      <dc:creator>balajij8</dc:creator>
      <dc:date>2026-07-02T14:25:14Z</dc:date>
    </item>
    <item>
      <title>Re: Shipping Unity AI Gateway OTel to other collectors</title>
      <link>https://community.databricks.com/t5/administration-architecture/shipping-unity-ai-gateway-otel-to-other-collectors/m-p/161214#M5383</link>
      <description>&lt;P class="wnfdntt _1ibi0s3f5 _1ibi0s3ce _1ibi0s3ea" data-pm-slice="1 1 []"&gt;Thanks for raising this. Based on the current public documentation, Unity AI Gateway’s documented OpenTelemetry path for coding-agent telemetry is to Databricks-managed Unity Catalog Delta tables, rather than to an arbitrary external OTel collector.&lt;/P&gt;
&lt;P class="wnfdntt _1ibi0s3f5 _1ibi0s3ce _1ibi0s3ea"&gt;The setup shown in the docs uses Databricks OTLP endpoints such as &lt;CODE&gt;/api/2.0/otel/v1/metrics&lt;/CODE&gt; and &lt;CODE&gt;/api/2.0/otel/v1/logs&lt;/CODE&gt;, with the Unity Catalog destination table specified through the &lt;CODE&gt;X-Databricks-UC-Table-Name&lt;/CODE&gt; header.&lt;/P&gt;
&lt;P class="wnfdntt _1ibi0s3f5 _1ibi0s3ce _1ibi0s3ea"&gt;You may be remembering MLflow tracing, which is documented separately and does support exporting to an OpenTelemetry Collector. That documentation explicitly describes both “OpenTelemetry only” and “Dual export” modes.&lt;/P&gt;
&lt;P class="wnfdntt _1ibi0s3f5 _1ibi0s3ce _1ibi0s3ea"&gt;Relevant docs:&lt;/P&gt;
&lt;UL class="wnfdnte" dir="auto"&gt;
&lt;LI class="wnfdntd _1ibi0s33w" dir="auto"&gt;
&lt;P class="wnfdntt _1ibi0s3f5 _1ibi0s3ce _1ibi0s3ea"&gt;Unity AI Gateway coding-agent OTel setup: &lt;A href="https://docs.databricks.com/aws/en/ai-gateway/coding-agent-integration-model-services" rel="noopener noreferrer nofollow" target="_blank"&gt;Integrate with coding agents&lt;/A&gt;&lt;/P&gt;
&lt;/LI&gt;
&lt;LI class="wnfdntd _1ibi0s33w" dir="auto"&gt;
&lt;P class="wnfdntt _1ibi0s3f5 _1ibi0s3ce _1ibi0s3ea"&gt;MLflow tracing OTel export: &lt;A href="https://docs.databricks.com/aws/en/mlflow3/genai/tracing/integrations/open-telemetry" rel="noopener noreferrer nofollow" target="_blank"&gt;OpenTelemetry Export&lt;/A&gt;&lt;/P&gt;
&lt;/LI&gt;
&lt;/UL&gt;
&lt;P class="wnfdntt _1ibi0s3f5 _1ibi0s3ce _1ibi0s3ea"&gt;So the short answer is: not as a documented Unity AI Gateway capability today, but Databricks does document external OTel collector export for MLflow tracing.&lt;/P&gt;</description>
      <pubDate>Thu, 02 Jul 2026 14:25:17 GMT</pubDate>
      <guid>https://community.databricks.com/t5/administration-architecture/shipping-unity-ai-gateway-otel-to-other-collectors/m-p/161214#M5383</guid>
      <dc:creator>yogeshsingh</dc:creator>
      <dc:date>2026-07-02T14:25:17Z</dc:date>
    </item>
    <item>
      <title>Re: Shipping Unity AI Gateway OTel to other collectors</title>
      <link>https://community.databricks.com/t5/administration-architecture/shipping-unity-ai-gateway-otel-to-other-collectors/m-p/161236#M5387</link>
      <description>&lt;P&gt;&lt;a href="https://community.databricks.com/t5/user/viewprofilepage/user-id/95271"&gt;@yogeshsingh&lt;/a&gt;&amp;nbsp;Thank you&amp;nbsp;&amp;nbsp;that's exactly what I had confused in my brain.&amp;nbsp;&amp;nbsp;&lt;a href="https://community.databricks.com/t5/user/viewprofilepage/user-id/210897"&gt;@balajij8&lt;/a&gt;&amp;nbsp;&amp;nbsp;as you suggested I will add a feature request.&amp;nbsp; It probably wouldn't be difficult to roll our own log shipping but endpoint config would be smoother and "platform level".&lt;/P&gt;</description>
      <pubDate>Thu, 02 Jul 2026 17:27:57 GMT</pubDate>
      <guid>https://community.databricks.com/t5/administration-architecture/shipping-unity-ai-gateway-otel-to-other-collectors/m-p/161236#M5387</guid>
      <dc:creator>Rjdudley</dc:creator>
      <dc:date>2026-07-02T17:27:57Z</dc:date>
    </item>
  </channel>
</rss>

