Exam AZ-400 topic 2 question 34 discussion

Application Insights now supports distributed tracing through OpenTelemetry. OpenTelemetry provides a vendor-neutral instrumentation to send traces, metrics, and logs to Application Insights. Initially, the OpenTelemetry community took on distributed tracing. In addition to the Application Insights SDKs, Application Insights also supports distributed tracing through OpenCensus. OpenCensus is an open-source, vendor-agnostic, single distribution of libraries to provide metrics collection and distributed tracing for services. https://learn.microsoft.com/en-us/azure/azure-monitor/app/distributed-tracing

This question is weird. OpenCensus and OpenTracing have merged to form OpenTelemetry, which serves as the next major version of OpenCensus and OpenTracing.

D. OpenTelemetry E. OpenCensus Both OpenTelemetry and OpenCensus have built-in support for exporting telemetry data to various backends, including Application Insights. Therefore, they can seamlessly integrate with Application Insights, allowing you to centralize distributed tracing for your microservices-based apps.

OpenTelemetry: This is a vendor-neutral tracing API that aims to unify distributed tracing across different platforms. Application Insights offers an OpenTelemetry exporter, allowing your microservices to send tracing data directly to Application Insights for centralized analysis. OpenCensus: OpenCensus is another open-source tracing library that predated OpenTelemetry. While it's not actively developed anymore, Application Insights still supports OpenCensus exporters for existing applications using this library.

Both OpenTelemetry and OpenCensus provide exporters that allow you to send telemetry data, including distributed tracing information, to Application Insights. This enables you to centralize distributed tracing for your microservices-based apps in Azure Monitor.

The only valid answer is OpenTelemetry. Source: https://learn.microsoft.com/en-us/azure/azure-monitor/app/opentelemetry-overview?tabs=aspnetcore OpenCensus and OpenTracing have merged to form OpenTelemetry.

https://learn.microsoft.com/en-us/python/api/overview/azure/opentelemetry-exporter-azuremonitor-readme?view=azure-python-preview D Open Telemetry E openCensus

DE is the answer. https://learn.microsoft.com/en-us/azure/azure-monitor/app/opentelemetry-overview Microsoft is excited to embrace OpenTelemetry as the future of telemetry instrumentation. You, our customers, have asked for vendor-neutral instrumentation, and we're pleased to partner with the OpenTelemetry community to create consistent APIs and SDKs across languages. Microsoft worked with project stakeholders from two previously popular open-source telemetry projects, OpenCensus and OpenTracing. Together, we helped to create a single project, OpenTelemetry. OpenTelemetry includes contributions from all major cloud and Application Performance Management (APM) vendors and lives within the Cloud Native Computing Foundation (CNCF). Microsoft is a Platinum Member of the CNCF.

The two libraries that can integrate directly with Application Insights are: D. OpenTelemetry E. OpenCensus Both OpenTelemetry and OpenCensus provide libraries and integrations for sending tracing data to Application Insights, allowing you to centralize and analyze your distributed tracing data in one place. OpenTracing and Jaeger are also open-source tracing libraries, but they do not integrate directly with Application Insights. Honeycomb is a commercial tracing and observability platform that provides its own tracing and analysis capabilities, but it does not integrate directly with Application Insights.