CorrelationId in Metadata.json is ignored

MDVHG 0 Reputation points
2024-10-07T09:20:49.3733333+00:00

Hello,

before a singing request we supply our own CorrelationId in the metadata.json file to track which project uses the most sign requests.

We've setup monitoring to a storage account. I've downloaded the logs and found that our custom CorrelationId is nowhere to be found.

I think the CorrelationId is overwritten by a new Guid every time.

Is this a bug in the Microsoft.Trusted.Signing.Client?

Thanks,

Michael

Artifact Signing
Artifact Signing

A fully managed end-to-end service for digitally signing code, documents, and applications. (formerly Trusted Signing)

0 comments No comments

Your answer

Answers can be marked as 'Accepted' by the question author and 'Recommended' by moderators, which helps users know the answer solved the author's problem.