Question
Your company is piloting a customer support agent in a Microsoft Foundry project named Project1. Project1 is connected to an existing Application Insights resource, and the company's support team reviews runs in the Traces tab.
The Foundry Agent Service is configured to perform the following actions:
- Retrieve the Application Insights connection string by calling project_client.telemetry.get_application_insights_connection_string().
- Call configure_azure_monitor(connection_string=...) to enable telemetry.
A separate LangChain service is configured to use OpenTelemetry and has the following configurations:
- Uses AzureAIOpenTelemetryTracer(connection_string=..., enable_content_recording=False)
- Passes the tracer by using config={"callbacks":[azure_tracer]}
Company policy has the following requirements:
- Telemetry from LangChain and OpenTelemetry must be distinguishable within the same Application Insights resource.
- Secrets and credentials must NOT be stored in prompts, tool arguments, or span attributes.
For each of the following statements, select Yes if the statement is true. Otherwise, select No.
NOTE: Each correct selection is worth one point.
Explanation
Statement 1 (No): LangChain emits no Foundry traces on its own. You must instrument it, for example by creating AzureAIOpenTelemetryTracer and attaching it through callbacks, and without that instrumentation its spans do not appear.
Statement 2 (Yes): OTEL_SERVICE_NAME sets the OpenTelemetry service name, which is stored as a resource attribute on the telemetry. Giving each service its own value lets you tell them apart while they share one Application Insights resource.
Statement 3 (No): Setting enable_content_recording=False redacts message content and tool call arguments from the traces. Content recording is on by default, so this setting is what stops prompts and tool data from being captured.
