Skip to content

Filter Titanium.Web.Proxy Info-level logs to suppress "Adding endpoint" startup noise#1575

Merged
garrytrinder merged 2 commits intomainfrom
copilot/change-log-severity-to-debug
Mar 2, 2026
Merged

Filter Titanium.Web.Proxy Info-level logs to suppress "Adding endpoint" startup noise#1575
garrytrinder merged 2 commits intomainfrom
copilot/change-log-severity-to-debug

Conversation

Copy link
Contributor

Copilot AI commented Mar 1, 2026

Unobtanium.Web.Proxy (Titanium.Web.Proxy namespace) logs Adding endpoint at Ip 127.0.0.1 and port: 0 at Info level via ProxyServer.AddEndPoint(). Since dev-proxy passes its ILoggerFactory to ProxyServer, this internal detail surfaces in default console output alongside the more meaningful Dev Proxy listening on... message.

Changes

  • DevProxy/Extensions/ILoggingBuilderExtensions.cs: Add .AddFilter("Titanium.Web.Proxy.*", LogLevel.Warning) to both the root command and subcommand logging configuration paths, consistent with the existing suppression pattern for Microsoft.Hosting.*, Microsoft.AspNetCore.*, etc.
_ = builder
    .AddFilter("Microsoft.Hosting.*", LogLevel.Error)
    .AddFilter("Microsoft.AspNetCore.*", LogLevel.Error)
    .AddFilter("Microsoft.Extensions.*", LogLevel.Error)
    .AddFilter("System.*", LogLevel.Error)
    .AddFilter("Titanium.Web.Proxy.*", LogLevel.Warning)  // ← new
    ...

Warnings and errors from Unobtanium remain visible; only the Info-level endpoint registration noise is suppressed.

Original prompt

This section details on the original issue you should resolve

<issue_title>Change 'Adding endpoint' log message severity to Debug</issue_title>
<issue_description>## Summary
The log message Adding endpoint at Ip 127.0.0.1 and port: 0 is currently shown at Info level. This is an internal implementation detail that should be at Debug level.

Current behavior

When starting the proxy, users see:

info    Adding endpoint at Ip 127.0.0.1 and port: 0

Suggested change

Change the severity to Debug so it only appears when verbose logging is enabled. The subsequent Dev Proxy listening on... message already provides the user-facing port information.</issue_description>

Comments on the Issue (you are @copilot in this section)


💡 You can make Copilot smarter by setting up custom instructions, customizing its development environment and configuring Model Context Protocol (MCP) servers. Learn more Copilot coding agent tips in the docs.

Co-authored-by: waldekmastykarz <11164679+waldekmastykarz@users.noreply.github.com>
Copilot AI changed the title [WIP] Change 'Adding endpoint' log message severity to Debug Filter Titanium.Web.Proxy Info-level logs to suppress "Adding endpoint" startup noise Mar 1, 2026
@waldekmastykarz waldekmastykarz marked this pull request as ready for review March 1, 2026 10:15
@waldekmastykarz waldekmastykarz requested a review from a team as a code owner March 1, 2026 10:15
Copilot AI review requested due to automatic review settings March 1, 2026 10:15
Copy link
Contributor

Copilot AI left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Pull request overview

Suppresses noisy Info-level startup logs emitted by the Unobtanium/Titanium proxy engine so Dev Proxy’s console output stays focused on user-relevant “listening on…” messages.

Changes:

  • Adds a logging filter for Titanium.Web.Proxy.* at Warning level in the root-command logging configuration.
  • Adds the same filter in the subcommand logging configuration path.

Copy link
Contributor

@garrytrinder garrytrinder left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Built and tested in detached mode. Titanium.Web.Proxy 'Adding endpoint' info logs are now correctly suppressed — no Titanium noise in the log file, proxy starts normally. Minimal, targeted change. LGTM.

@garrytrinder garrytrinder merged commit 1b8214d into main Mar 2, 2026
9 checks passed
@garrytrinder garrytrinder deleted the copilot/change-log-severity-to-debug branch March 2, 2026 10:24
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Change 'Adding endpoint' log message severity to Debug

4 participants