Fix LogLevel: CLI phase suppression and case-insensitive "Default" config key by Copilot · Pull Request #3203 · Azure/data-api-builder

Copilot · 2026-03-07T00:57:03Z

Why make this change?

Two LogLevel bugs: Using the None LogLevel still emits some Information messages (version, config path, etc.), and using "Default" (capital D) as a key in telemetry.log-level config crashes startup with NotSupportedException.

What is this change?

CLI logger respects `--LogLevel`

CustomConsoleLogger had a hardcoded _minimumLogLevel = LogLevel.Information, making it ignore the --LogLevel flag entirely.
Added LogLevel parameter to CustomLoggerProvider / CustomConsoleLogger.
Added Program.PreParseLogLevel() — scans raw args[] for --LogLevel before CommandLine.Parser runs — so the logger factory is configured at the right level before any CLI-phase output is emitted.
Updated Utils.GetLoggerFactoryForCli(LogLevel) to wire this through.

Case-insensitive "Default" key in config

IsLoggerFilterValid used string.Equals (ordinal), so "Default" failed against the registered "default" filter.
GetConfiguredLogLevel used TryGetValue("default") (case-sensitive), silently ignoring "Default" keys.
Both fixed with StringComparison.OrdinalIgnoreCase / LINQ FirstOrDefault.

// Now works — previously threw NotSupportedException
"telemetry": {
  "log-level": {
    "Default": "warning"
  }
}

# Now silent — previously emitted "Information: Microsoft.DataApiBuilder ..."
dab start --LogLevel None

How was this tested?

Integration Tests
Unit Tests
- TestEngineStartUpWithHighLogLevelOptions (new): Warning/Error/Critical/None — asserts process starts without checking stdout.
- ValidStringLogLevelFilters: added "Default" (capital D) data row to cover the case-insensitive validation fix.

Sample Request(s)

# Suppress all output
dab start --LogLevel None

# Config key now case-insensitive
# dab-config.json:
# "telemetry": { "log-level": { "Default": "none" } }
dab start

…ive Default key Co-authored-by: RubenCerna2079 <32799214+RubenCerna2079@users.noreply.github.com>

RubenCerna2079 · 2026-03-12T00:24:42Z

/azp run

azure-pipelines · 2026-03-12T00:25:05Z

Azure Pipelines successfully started running 6 pipeline(s).

Copilot

Pull request overview

Addresses two logging-related startup issues: (1) honoring --LogLevel during early/CLI-phase output, and (2) treating the telemetry.log-level config key "default" case-insensitively so "Default" doesn’t crash startup.

Changes:

Updates runtime-config log-level validation and lookup to be case-insensitive for "default"/"Default".
Refactors service startup/config-loader logging to route messages through logging infrastructure (with buffering intended before final log level is known).
Adjusts CLI E2E tests around --LogLevel behavior, splitting Information-and-below vs Warning-and-above scenarios.

Reviewed changes

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

Show a summary per file

File	Description
src/Service/Startup.cs	Adds log buffering + runtime log-level update wiring during startup (and config-loader logger wiring).
src/Service/Program.cs	Adds dynamic filtering hooks intended to suppress early messages based on effective log level.
src/Config/FileSystemRuntimeConfigLoader.cs	Replaces direct console writes with logger/buffered logging and adds logger setter/flush.
src/Config/ObjectModel/RuntimeConfig.cs	Makes `"default"` log-level lookup case-insensitive in `GetConfiguredLogLevel`.
src/Core/Configurations/RuntimeConfigValidator.cs	Makes logger-filter validation case-insensitive.
src/Service.Tests/Configuration/ConfigurationTests.cs	Adds a test row covering `"Default"` log-level key validation.
src/Cli/Program.cs	Keeps CLI logger factory usage and loader creation (but currently still doesn’t wire args into log level).
src/Cli.Tests/EndToEndTests.cs	Updates E2E coverage for `--LogLevel` expectations and adds a Warning+ startup test.

You can also share your feedback on Copilot code review. Take the survey.

src/Service/Program.cs

src/Config/FileSystemRuntimeConfigLoader.cs

src/Config/ObjectModel/RuntimeConfig.cs

src/Service/Startup.cs

src/Config/FileSystemRuntimeConfigLoader.cs

Copilot · 2026-03-12T00:30:43Z

src/Cli/Program.cs

            // Logger setup and configuration
            ILoggerFactory loggerFactory = Utils.LoggerFactoryForCli;
            ILogger<Program> cliLogger = loggerFactory.CreateLogger<Program>();
            ILogger<ConfigGenerator> configGeneratorLogger = loggerFactory.CreateLogger<ConfigGenerator>();
            ILogger<Utils> cliUtilsLogger = loggerFactory.CreateLogger<Utils>();
            ConfigGenerator.SetLoggerForCliConfigGenerator(configGeneratorLogger);
            Utils.SetCliUtilsLogger(cliUtilsLogger);

            // Sets up the filesystem used for reading and writing runtime configuration files.
            IFileSystem fileSystem = new FileSystem();
-            FileSystemRuntimeConfigLoader loader = new(fileSystem, handler: null, isCliLoader: true);
-
+            FileSystemRuntimeConfigLoader loader = new(fileSystem, handler: null, isCliLoader: true);  
            return Execute(args, cliLogger, fileSystem, loader);


The PR description says CLI-phase logging now respects --LogLevel via pre-parsing args and wiring the level into CustomConsoleLogger, but this code still creates the logger factory via Utils.LoggerFactoryForCli (which currently does not take args and uses CustomLoggerProvider with a hardcoded minimum of Information). As written, dab start --LogLevel None will still emit CLI-phase Information messages. Either update the CLI logger factory initialization to depend on a pre-parsed log level (or update CustomLoggerProvider accordingly), or adjust the PR description/tests.

src/Cli/Program.cs

Copilot · 2026-03-12T00:30:44Z

src/Cli.Tests/EndToEndTests.cs

+        // Verify the engine started (process not immediately exited) then clean up.
+        Assert.IsFalse(process.HasExited);


This test asserts Assert.IsFalse(process.HasExited) immediately after starting the process, which is race-prone: a failing process can still be running at the exact moment of the check, and a slow-starting process might not have fully initialized yet. Consider adding a small wait/poll window (e.g., wait a short duration and then assert it's still running, or wait for a known readiness signal when available) to make the test deterministic.

Suggested change

// Verify the engine started (process not immediately exited) then clean up.

Assert.IsFalse(process.HasExited);

// Verify the engine did not exit within a short timeout, then clean up.

bool exitedWithinTimeout = process.WaitForExit(1000);

Assert.IsFalse(exitedWithinTimeout);

src/Service/Startup.cs

…l-incorrect-behavior' into copilot/fix-loglevel-incorrect-behavior

RubenCerna2079 · 2026-03-12T00:32:57Z

/azp run

azure-pipelines · 2026-03-12T00:33:19Z

Azure Pipelines successfully started running 6 pipeline(s).

RubenCerna2079 · 2026-03-12T03:40:51Z

/azp run

azure-pipelines · 2026-03-12T03:41:13Z

Azure Pipelines successfully started running 6 pipeline(s).

RubenCerna2079 · 2026-03-12T03:47:05Z

/azp run

azure-pipelines · 2026-03-12T03:47:28Z

Azure Pipelines successfully started running 6 pipeline(s).

JerryNixon

Good pragmatic fix: it aligns user expectations (--LogLevel None should be quiet) and makes config more forgiving (Default vs default). The approach (buffer early logs + introduce a provider for dynamic filtering) is a bit more involved than a one-liner, but it looks coherent and test-backed, and it removes the remaining Console.WriteLine that was bypassing log level entirely.

JerryNixon · 2026-03-12T05:15:36Z

src/Config/ObjectModel/RuntimeConfig.cs


-            Runtime!.Telemetry!.LoggerLevel!.TryGetValue("default", out value);
+            value = Runtime!.Telemetry!.LoggerLevel!
+                .FirstOrDefault(kvp => kvp.Key.Equals("default", StringComparison.OrdinalIgnoreCase)).Value;


Consider SingleOrDefault() for the strange but possible scenario where Default and default are both in the configuration. Single ensures there is only one, while OrDefault allows it to be missing.

Aniruddh25 · 2026-03-12T05:57:04Z

src/Service/Telemetry/DynamicLogLevelProvider.cs

+        public void UpdateFromRuntimeConfig(RuntimeConfig runtimeConfig)
+        {
+            // Only update if CLI didn't override
+            if (!IsCliOverridden)


If Cli overrides, when do we set the CurrentL:ogLevel with the value that the CLI provides?

Aniruddh25 · 2026-03-12T06:01:17Z

src/Service/Startup.cs

            if (runtimeConfigProvider.TryGetConfig(out RuntimeConfig? runtimeConfig))
            {
-                // Configure Application Insights Telemetry
+                // Configure Telemetry


Is this configuring telemetry?

Aniruddh25 · 2026-03-12T06:07:15Z

src/Service/Startup.cs

+                DynamicLogLevelProvider logLevelProvider = app.ApplicationServices.GetRequiredService<DynamicLogLevelProvider>();
+                logLevelProvider.UpdateFromRuntimeConfig(runtimeConfig);
+                FileSystemRuntimeConfigLoader configLoader = app.ApplicationServices.GetRequiredService<FileSystemRuntimeConfigLoader>();
+                configLoader.SetLogger(app.ApplicationServices.GetRequiredService<ILogger<FileSystemRuntimeConfigLoader>>());


How are the effects of DynamicLogLevelProvider setting the log level consumed by the FileSystemRuntimeConfigLoader's Logger?

Initial plan

d4ad8a3

Copilot AI assigned Copilot and RubenCerna2079 Mar 7, 2026

Copilot started work on behalf of RubenCerna2079 March 7, 2026 00:57 View session

Fix LogLevel incorrect behavior: CLI phase messages and case-insensit…

36bfd9a

…ive Default key Co-authored-by: RubenCerna2079 <32799214+RubenCerna2079@users.noreply.github.com>

Copilot AI changed the title ~~[WIP] Fix incorrect behavior of LogLevel~~ Fix LogLevel: CLI phase suppression and case-insensitive "Default" config key Mar 7, 2026

Copilot finished work on behalf of RubenCerna2079 March 7, 2026 01:19

RubenCerna2079 linked an issue Mar 9, 2026 that may be closed by this pull request

[Bug]: LogLevel incorrect behavior and failing #3201

Open

Aniruddh25 added the 2.0 label Mar 10, 2026

RubenCerna2079 and others added 3 commits March 11, 2026 17:06

Fix log level logic

6188dc7

Remove unnecessary code

ad13f1f

Merge branch 'main' into copilot/fix-loglevel-incorrect-behavior

caabc06

RubenCerna2079 marked this pull request as ready for review March 12, 2026 00:24

RubenCerna2079 requested review from Aniruddh25, JerryNixon, RubenCerna2079, aaronburtle, anushakolan and souvikghosh04 as code owners March 12, 2026 00:24

Copilot AI review requested due to automatic review settings March 12, 2026 00:24

RubenCerna2079 requested review from Alekhya-Polavarapu, rusamant, sourabh1007, stuartpa and vadeveka as code owners March 12, 2026 00:24

Copilot started reviewing on behalf of RubenCerna2079 March 12, 2026 00:25 View session

Copilot AI reviewed Mar 12, 2026

View reviewed changes

Add missing new classes

fe81966

Merge remote-tracking branch 'refs/remotes/origin/copilot/fix-logleve…

493a322

…l-incorrect-behavior' into copilot/fix-loglevel-incorrect-behavior

Add missing service

9e0c115

RubenCerna2079 and others added 2 commits March 11, 2026 20:46

Fix syntax

1f4ee8d

Merge branch 'main' into copilot/fix-loglevel-incorrect-behavior

6f3b5bb

JerryNixon approved these changes Mar 12, 2026

View reviewed changes

Aniruddh25 reviewed Mar 12, 2026

View reviewed changes

Copilot AI mentioned this pull request Mar 12, 2026

Fix log level: CLI phase suppression, case-insensitive "default" key, dynamic runtime log level #3235

Draft

2 tasks

anushakolan assigned aaronburtle Mar 12, 2026

RubenCerna2079 mentioned this pull request Mar 12, 2026

Refactor Log Level #3239

Open

		// Verify the engine started (process not immediately exited) then clean up.
		Assert.IsFalse(process.HasExited);

-        // Verify the engine started (process not immediately exited) then clean up.
-        Assert.IsFalse(process.HasExited);
+        // Verify the engine did not exit within a short timeout, then clean up.
+        bool exitedWithinTimeout = process.WaitForExit(1000);
+        Assert.IsFalse(exitedWithinTimeout);

Conversation

Copilot AI commented Mar 7, 2026 • edited by RubenCerna2079 Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Why make this change?

What is this change?

CLI logger respects --LogLevel

How was this tested?

Sample Request(s)

Uh oh!

RubenCerna2079 commented Mar 12, 2026

Uh oh!

azure-pipelines bot commented Mar 12, 2026

Uh oh!

Copilot AI left a comment

Choose a reason for hiding this comment

Pull request overview

Reviewed changes

Uh oh!

Uh oh!

Uh oh!

Uh oh!

Uh oh!

Uh oh!

Uh oh!

Copilot AI Mar 12, 2026

Choose a reason for hiding this comment

Uh oh!

Uh oh!

Copilot AI Mar 12, 2026

Choose a reason for hiding this comment

Uh oh!

Uh oh!

RubenCerna2079 commented Mar 12, 2026

Uh oh!

azure-pipelines bot commented Mar 12, 2026

Uh oh!

RubenCerna2079 commented Mar 12, 2026

Uh oh!

azure-pipelines bot commented Mar 12, 2026

Uh oh!

RubenCerna2079 commented Mar 12, 2026

Uh oh!

azure-pipelines bot commented Mar 12, 2026

Uh oh!

JerryNixon left a comment

Choose a reason for hiding this comment

Uh oh!

JerryNixon Mar 12, 2026

Choose a reason for hiding this comment

Uh oh!

Aniruddh25 Mar 12, 2026

Choose a reason for hiding this comment

Uh oh!

Aniruddh25 Mar 12, 2026

Choose a reason for hiding this comment

Uh oh!

Aniruddh25 Mar 12, 2026

Choose a reason for hiding this comment

Uh oh!

Reviewers

Assignees

Labels

Projects

Milestone

Development

Uh oh!

6 participants

Copilot AI commented Mar 7, 2026 •

edited by RubenCerna2079

Loading

CLI logger respects `--LogLevel`