{ "api_version": "1", "kind": "dse_post", "self": "https://update.dsesecurity.com/api/v1/posts/dse-20260909-543-choose-the-otlp-transport-for-the-actual-azure-monitor-ingestion-path/", "item": { "id": "https://update.dsesecurity.com/updates/dse-20260909-543-choose-the-otlp-transport-for-the-actual-azure-monitor-ingestion-path/", "slug": "dse-20260909-543-choose-the-otlp-transport-for-the-actual-azure-monitor-ingestion-path", "url": "https://update.dsesecurity.com/updates/dse-20260909-543-choose-the-otlp-transport-for-the-actual-azure-monitor-ingestion-path/", "alternate_urls": { "markdown": "https://update.dsesecurity.com/updates/dse-20260909-543-choose-the-otlp-transport-for-the-actual-azure-monitor-ingestion-path.md", "json": "https://update.dsesecurity.com/api/v1/posts/dse-20260909-543-choose-the-otlp-transport-for-the-actual-azure-monitor-ingestion-path/" }, "title": "Choose the OTLP transport for the actual Azure Monitor ingestion path", "summary": "Can the same OTLP protocol and port configuration be reused for AMA, AKS and Collector ingestion?", "format": { "slug": "guide", "name": "Guide" }, "priority": { "slug": "info", "name": "Information" }, "featured": false, "image": { "theme": "network-infrastructure", "label": "Networks & infrastructure", "alt": "Resilient network core with engineered blue and gold data paths.", "card_url": "https://update.dsesecurity.com/assets/editorial/network-infrastructure-card.webp?v=1.8.20", "hero_url": "https://update.dsesecurity.com/assets/editorial/network-infrastructure-hero.webp?v=1.8.20", "social_url": "https://update.dsesecurity.com/assets/editorial/network-infrastructure-social-v2.jpg?v=1.8.20", "width": 2400, "height": 1350 }, "topics": [ { "slug": "it", "name": "IT", "url": "https://update.dsesecurity.com/topic/it/" }, { "slug": "networks-infrastructure", "name": "Networks & Infrastructure", "url": "https://update.dsesecurity.com/topic/networks-infrastructure/" } ], "author": { "name": "DSE Security Editorial Team", "url": "https://update.dsesecurity.com/#editorial-team", "type": "Organization" }, "publisher": { "name": "Detection Systems & Engineering", "url": "https://dsesecurity.com/" }, "published_at": "2026-09-10T00:22:53+00:00", "modified_at": "2026-09-10T02:11:19+00:00", "reviewed_on": "2026-09-09", "reading_minutes": 2, "word_count": 229, "potentially_affected": "Nonproduction evaluations of Azure Monitor's preview OpenTelemetry ingestion paths.", "dse_recommendation": "Document the application's immediate receiver and its required transport before copying an OTLP endpoint configuration.", "primary_source": { "name": "Collect and analyze OpenTelemetry data with Azure Monitor (Preview) - Azure Monitor | Microsoft Learn", "url": "https://learn.microsoft.com/en-us/azure/azure-monitor/containers/collect-use-observability-data", "published_on": null, "authority": "Microsoft Learn" }, "publishing_principles": "https://update.dsesecurity.com/updates/dse-updates-editorial-methodology/", "usage_info": "https://update.dsesecurity.com/usage/", "copyright_notice": "Copyright © 2026 Detection Systems & Engineering. All rights reserved.", "content_html": "

Source facts

\n

Azure Monitor’s documented OpenTelemetry experience is preview and is not recommended for production workloads. Its AMA path uses local gRPC: port 4317 for metrics and 4319 for logs and traces. Port 4319 is AMA-specific, not a canonical OTLP port. The AKS integration supports HTTP/protobuf, not JSON or OTLP/gRPC, while the Collector’s Azure export also uses HTTP/protobuf. Microsoft Learn.

\n

Applicability

\n

Use this comparison during a bounded preview evaluation. Identify each hop separately: an application’s connection to a local receiver and that receiver’s export to Azure are not automatically the same protocol contract.

\n

DSE recommendation

\n

Document the application’s immediate receiver and its required transport before copying an OTLP endpoint configuration. Have the application and platform owners agree which ingestion path is being tested. Keep signal-specific endpoints explicit, and do not infer that a familiar port number makes gRPC and HTTP payloads interchangeable. Avoid changing network controls until the selected transport matches the documented receiver.

\n

Verification

\n

Inspect the effective exporter endpoint, signal type and protocol in the test deployment. Send an approved identifiable sample through each intended signal path and check receiver errors as well as destination data. Record which hop accepted the sample and whether it reached the expected experience. A reachable socket alone is not the acceptance result; retain unresolved protocol mismatches before expanding the preview test.

\n

Official references

\n

Microsoft Learn: OpenTelemetry ingestion paths, preview. Source reviewed September 9, 2026.

", "content_text": "Source facts\nAzure Monitor’s documented OpenTelemetry experience is preview and is not recommended for production workloads. Its AMA path uses local gRPC: port 4317 for metrics and 4319 for logs and traces. Port 4319 is AMA-specific, not a canonical OTLP port. The AKS integration supports HTTP/protobuf, not JSON or OTLP/gRPC, while the Collector’s Azure export also uses HTTP/protobuf. Microsoft Learn.\nApplicability\nUse this comparison during a bounded preview evaluation. Identify each hop separately: an application’s connection to a local receiver and that receiver’s export to Azure are not automatically the same protocol contract.\nDSE recommendation\nDocument the application’s immediate receiver and its required transport before copying an OTLP endpoint configuration. Have the application and platform owners agree which ingestion path is being tested. Keep signal-specific endpoints explicit, and do not infer that a familiar port number makes gRPC and HTTP payloads interchangeable. Avoid changing network controls until the selected transport matches the documented receiver.\nVerification\nInspect the effective exporter endpoint, signal type and protocol in the test deployment. Send an approved identifiable sample through each intended signal path and check receiver errors as well as destination data. Record which hop accepted the sample and whether it reached the expected experience. A reachable socket alone is not the acceptance result; retain unresolved protocol mismatches before expanding the preview test.\nOfficial references\nMicrosoft Learn: OpenTelemetry ingestion paths, preview. Source reviewed September 9, 2026.", "content_markdown": "## Source facts\n\nAzure Monitor’s documented OpenTelemetry experience is preview and is not recommended for production workloads. Its AMA path uses local gRPC: port 4317 for metrics and 4319 for logs and traces. Port 4319 is AMA-specific, not a canonical OTLP port. The AKS integration supports HTTP/protobuf, not JSON or OTLP/gRPC, while the Collector’s Azure export also uses HTTP/protobuf. [Microsoft Learn](https://learn.microsoft.com/en-us/azure/azure-monitor/containers/collect-use-observability-data).\n\n## Applicability\n\nUse this comparison during a bounded preview evaluation. Identify each hop separately: an application’s connection to a local receiver and that receiver’s export to Azure are not automatically the same protocol contract.\n\n## DSE recommendation\n\nDocument the application’s immediate receiver and its required transport before copying an OTLP endpoint configuration. Have the application and platform owners agree which ingestion path is being tested. Keep signal-specific endpoints explicit, and do not infer that a familiar port number makes gRPC and HTTP payloads interchangeable. Avoid changing network controls until the selected transport matches the documented receiver.\n\n## Verification\n\nInspect the effective exporter endpoint, signal type and protocol in the test deployment. Send an approved identifiable sample through each intended signal path and check receiver errors as well as destination data. Record which hop accepted the sample and whether it reached the expected experience. A reachable socket alone is not the acceptance result; retain unresolved protocol mismatches before expanding the preview test.\n\n## Official references\n\n[Microsoft Learn: OpenTelemetry ingestion paths, preview](https://learn.microsoft.com/en-us/azure/azure-monitor/containers/collect-use-observability-data). Source reviewed September 9, 2026." }, "json_ld": { "@context": "https://schema.org", "@graph": [ { "@type": "Organization", "@id": "https://dsesecurity.com/#organization", "name": "Detection Systems & Engineering", "alternateName": "DSE Security", "url": "https://dsesecurity.com/", "logo": { "@type": "ImageObject", "url": "https://update.dsesecurity.com/assets/dse-logo-20260812.png?v=1.8.20" } }, { "@type": "Organization", "@id": "https://update.dsesecurity.com/#editorial-team", "name": "DSE Security Editorial Team", "url": "https://update.dsesecurity.com/", "parentOrganization": { "@id": "https://dsesecurity.com/#organization" } }, { "@type": "WebSite", "@id": "https://update.dsesecurity.com/#website", "name": "DSE Updates", "alternateName": "DSE Security Knowledge Hub", "url": "https://update.dsesecurity.com/", "inLanguage": "en-US", "publisher": { "@id": "https://dsesecurity.com/#organization" }, "potentialAction": { "@type": "SearchAction", "target": { "@type": "EntryPoint", "urlTemplate": "https://update.dsesecurity.com/?q={search_term_string}" }, "query-input": "required name=search_term_string" } }, { "@type": "WebPage", "@id": "https://update.dsesecurity.com/updates/dse-20260909-543-choose-the-otlp-transport-for-the-actual-azure-monitor-ingestion-path/", "url": "https://update.dsesecurity.com/updates/dse-20260909-543-choose-the-otlp-transport-for-the-actual-azure-monitor-ingestion-path/", "isPartOf": { "@id": "https://update.dsesecurity.com/#website" }, "lastReviewed": "2026-09-09" }, { "@type": "BreadcrumbList", "@id": "https://update.dsesecurity.com/updates/dse-20260909-543-choose-the-otlp-transport-for-the-actual-azure-monitor-ingestion-path/#breadcrumbs", "itemListElement": [ { "@type": "ListItem", "position": 1, "name": "DSE Updates", "item": "https://update.dsesecurity.com/" }, { "@type": "ListItem", "position": 2, "name": "Choose the OTLP transport for the actual Azure Monitor ingestion path", "item": "https://update.dsesecurity.com/updates/dse-20260909-543-choose-the-otlp-transport-for-the-actual-azure-monitor-ingestion-path/" } ] }, { "@type": [ "Article", "TechArticle" ], "@id": "https://update.dsesecurity.com/updates/dse-20260909-543-choose-the-otlp-transport-for-the-actual-azure-monitor-ingestion-path/#article", "identifier": "https://update.dsesecurity.com/updates/dse-20260909-543-choose-the-otlp-transport-for-the-actual-azure-monitor-ingestion-path/", "url": "https://update.dsesecurity.com/updates/dse-20260909-543-choose-the-otlp-transport-for-the-actual-azure-monitor-ingestion-path/", "headline": "Choose the OTLP transport for the actual Azure Monitor ingestion path", "description": "Can the same OTLP protocol and port configuration be reused for AMA, AKS and Collector ingestion?", "abstract": "Can the same OTLP protocol and port configuration be reused for AMA, AKS and Collector ingestion?", "articleBody": "Source facts\nAzure Monitor’s documented OpenTelemetry experience is preview and is not recommended for production workloads. Its AMA path uses local gRPC: port 4317 for metrics and 4319 for logs and traces. Port 4319 is AMA-specific, not a canonical OTLP port. The AKS integration supports HTTP/protobuf, not JSON or OTLP/gRPC, while the Collector’s Azure export also uses HTTP/protobuf. Microsoft Learn.\nApplicability\nUse this comparison during a bounded preview evaluation. Identify each hop separately: an application’s connection to a local receiver and that receiver’s export to Azure are not automatically the same protocol contract.\nDSE recommendation\nDocument the application’s immediate receiver and its required transport before copying an OTLP endpoint configuration. Have the application and platform owners agree which ingestion path is being tested. Keep signal-specific endpoints explicit, and do not infer that a familiar port number makes gRPC and HTTP payloads interchangeable. Avoid changing network controls until the selected transport matches the documented receiver.\nVerification\nInspect the effective exporter endpoint, signal type and protocol in the test deployment. Send an approved identifiable sample through each intended signal path and check receiver errors as well as destination data. Record which hop accepted the sample and whether it reached the expected experience. A reachable socket alone is not the acceptance result; retain unresolved protocol mismatches before expanding the preview test.\nOfficial references\nMicrosoft Learn: OpenTelemetry ingestion paths, preview. Source reviewed September 9, 2026.", "datePublished": "2026-09-10T00:22:53+00:00", "dateModified": "2026-09-10T02:11:19+00:00", "mainEntityOfPage": { "@id": "https://update.dsesecurity.com/updates/dse-20260909-543-choose-the-otlp-transport-for-the-actual-azure-monitor-ingestion-path/" }, "inLanguage": "en-US", "isAccessibleForFree": true, "author": { "@type": "Organization", "name": "DSE Security Editorial Team", "url": "https://update.dsesecurity.com/#editorial-team" }, "publisher": { "@id": "https://dsesecurity.com/#organization" }, "image": { "@type": "ImageObject", "@id": "https://update.dsesecurity.com/updates/dse-20260909-543-choose-the-otlp-transport-for-the-actual-azure-monitor-ingestion-path/#primaryimage", "url": "https://update.dsesecurity.com/assets/editorial/network-infrastructure-social-v2.jpg?v=1.8.20", "contentUrl": "https://update.dsesecurity.com/assets/editorial/network-infrastructure-social-v2.jpg?v=1.8.20", "width": 1200, "height": 630, "caption": "Choose the OTLP transport for the actual Azure Monitor ingestion path" }, "articleSection": [ "IT", "Networks & Infrastructure" ], "keywords": [ "IT", "Networks & Infrastructure", "Guide", "Information priority" ], "genre": "Guide", "about": [ { "@type": "Thing", "name": "IT", "url": "https://update.dsesecurity.com/topic/it/" }, { "@type": "Thing", "name": "Networks & Infrastructure", "url": "https://update.dsesecurity.com/topic/networks-infrastructure/" } ], "wordCount": 229, "timeRequired": "PT2M", "publishingPrinciples": "https://update.dsesecurity.com/updates/dse-updates-editorial-methodology/", "usageInfo": "https://update.dsesecurity.com/usage/", "copyrightHolder": { "@id": "https://dsesecurity.com/#organization" }, "copyrightNotice": "Copyright © 2026 Detection Systems & Engineering. All rights reserved.", "citation": { "@type": "CreativeWork", "name": "Collect and analyze OpenTelemetry data with Azure Monitor (Preview) - Azure Monitor | Microsoft Learn", "url": "https://learn.microsoft.com/en-us/azure/azure-monitor/containers/collect-use-observability-data" } } ] } }