feat: wire all configuration options into runtime behavior; unify GenAI instrumentation interfaces and expand A365 config support

[Hector Hernandez (hectorhdzg)]

• document console exporter enablement and behavior\n- clarify instrumentation enable/disable patterns\n- align OpenAI/LangChain instrumentation interfaces with InstrumentationConfig\n- refresh GenAI samples with explicit enabled flags

[Copilot]

Pull request overview

Expands and clarifies A365 migration and configuration guidance across public docs and samples, including console exporter behavior and updated GenAI instrumentation configuration shapes.

Changes:

• Update InstrumentationOptions types to align GenAI configs with InstrumentationConfig-style shapes (enabled, etc.).
• Refresh OpenAI/LangChain samples and README examples to use explicit enabled: true flags.
• Expand README + A365 migration guidance around console exporters and instrumentation enable/disable patterns.

Reviewed changes

Copilot reviewed 5 out of 5 changed files in this pull request and generated 5 comments.

Show a summary per file

File	Description
src/types.ts	Adjusts public types for GenAI instrumentation configs and their documented shape.
samples/src/openaiInstrumentation.ts	Updates sample config to use enabled: true for OpenAI Agents instrumentation options.
samples/src/langchainInstrumentation.ts	Updates sample config to use enabled: true for LangChain instrumentation options.
README.md	Adds/clarifies instrumentation enable/disable guidance and documents console exporter behavior.
MIGRATION_A365.md	Expands A365 option coverage and migration guidance (env vars, console exporters, hosting utilities).

Comments suppressed due to low confidence (2)

samples/src/openaiInstrumentation.ts:29

• This sample configures instrumentationOptions.openaiAgents.enabled, but useMicrosoftOpenTelemetry() currently does not act on instrumentationOptions.openaiAgents (the distro only creates HTTP/Azure SDK/DB/Azure Functions + log instrumentations). As a result, the comment "this call is automatically traced" is misleading—either add distro support to initialize the OpenAI Agents instrumentor when enabled, or update the sample to use the actual enablement API.

  useMicrosoftOpenTelemetry({
    azureMonitor: {
      azureMonitorExporterOptions: {
        connectionString:
          process.env.APPLICATIONINSIGHTS_CONNECTION_STRING || "<your connection string>",
      },
    },
    instrumentationOptions: {
      openaiAgents: {
        enabled: true,
        isContentRecordingEnabled: true,
      },
    },
  });

samples/src/langchainInstrumentation.ts:30

• This sample configures instrumentationOptions.langchain.enabled, but useMicrosoftOpenTelemetry() currently does not act on instrumentationOptions.langchain, so the "automatically traced" behavior won’t occur. Either wire LangChain enablement into the distro when this flag is set, or update the sample to call the supported LangChain instrumentor API directly.

  useMicrosoftOpenTelemetry({
    azureMonitor: {
      azureMonitorExporterOptions: {
        connectionString:
          process.env.APPLICATIONINSIGHTS_CONNECTION_STRING || "<your connection string>",
      },
    },
    instrumentationOptions: {
      langchain: {
        enabled: true,
        isContentRecordingEnabled: true,
      },
    },
  });

---

💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.