Skip to content

Allow certain response headers coming from AzurePipelinesCredential to be logged #1823

@heaths

Description

@heaths

These two response headers are useful for the service team to debug and diagnose issues, and hence it is requested that we do log them.

  • x-vss-e2eid
  • x-msedge-ref

We decided, other than logging them, to also add these header values to the exception message that is thrown, so they are always visible, even with logging disabled.

Given our logged headers are based on an allow list, currently these two headers are REDACTED.

https://github.com/Azure/azure-sdk-for-net/blob/a70122eed52b0980afc10db30c76cb56b7bb76db/sdk/core/Azure.Core/src/DiagnosticsOptions.cs#L44-L71

Metadata

Metadata

Assignees

Labels

Azure.IdentityThe azure_identity crateClientThis issue points to a problem in the data-plane of the library.

Projects

Status

Blocked

Status

Not Started

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions