Cosmos: downgrade request-status error logs to debug

[Copilot]

Create-if-not-exists and similar flows can intentionally treat non-2xx service responses (for example, 409 Conflict) as successful control flow. The Cosmos pipeline was emitting high-severity logs for these outcomes, creating noisy WARN/ERROR output under normal usage.

• Pipeline abort logging severity

  • Changed operation_pipeline abort-path logging from tracing::error! to tracing::debug! for terminal operation outcomes that include typed Cosmos HTTP status.

• Hedged terminal HTTP outcome severity

  • Changed hedged terminal HTTP status logging (cosmos.hedge.terminal_http_error) from tracing::warn! to tracing::debug!.

• Behavioral impact

  • Status/sub-status telemetry remains logged, but request-status messages no longer surface as warn/error by default for user-handled HTTP outcomes.

// before
tracing::error!(status = ?cosmos_status, "operation aborted");
tracing::warn!(http_status = u16::from(status.status_code()), "cosmos.hedge.terminal_http_error");

// after
tracing::debug!(status = ?cosmos_status, "operation aborted");
tracing::debug!(http_status = u16::from(status.status_code()), "cosmos.hedge.terminal_http_error");

[azure-pipelines]

Azure Pipelines:
Successfully started running 1 pipeline(s).
2 pipeline(s) were filtered out due to trigger conditions.
There may be pipelines that require an authorized user to comment /azp run to run.

[Copilot]

Pull request overview

Downgrades Cosmos HTTP-status logging to reduce noise from expected control-flow responses.

Changes:

• Changes pipeline abort logs from error to debug.
• Changes hedged terminal HTTP logs from warning to debug.

Show a summary per file

File	Description
operation_pipeline.rs	Lowers terminal outcome log severity.

Review details

• Files reviewed: 1/1 changed files
• Comments generated: 1
• Review effort level: Medium

[analogrelay]

@copilot While you're fixing up the issues below, look out for any places where we're tracing "event name"-style strings like cosmos.hedge.terminal_http_error. Tracing events should have human-readable log-line-style messages.

[analogrelay]

@copilot This one should probably be debug! as well.

[Copilot]

Done in 16ae25a. This log is now emitted at debug!.

[analogrelay]

@copilot Fix this up to use a human-readable log line instead of an "event name" style. Something like non-retriable http error in hedging attempt

[Copilot]

Updated in 16ae25a. This now uses a human-readable message: non-retriable http error in hedging attempt.

[analogrelay]

@copilot Fix this up to use a human-readable log line instead of an "event name" style. Something like non-retriable transport error in hedging attempt

[Copilot]

Updated in 16ae25a. This now uses a human-readable message: non-retriable transport error in hedging attempt.

[Copilot]

@copilot While you're fixing up the issues below, look out for any places where we're tracing "event name"-style strings like cosmos.hedge.terminal_http_error. Tracing events should have human-reada...

Addressed in 16ae25a. Updated the touched hedging terminal tracing events to use human-readable log-line messages instead of event-name-style strings.