Turn off CosmosDiagnostics when logging CosmosException

[fivetran-kevinzhao]

Query/Question
Currently, when our process encounters a CosmosException, massive amounts of useless message gets printed. See attached txt file.
openai-cosmosexception.txt

For example, I only want the contents of the innerErrorMessage

"innerErrorMessage":"PartitionKeyRange with id 333 in collection null doesn't exist","causeInfo":null,"responseHeaders":"{x-ms-substatus=1002}"

However, tons of CosmosDiagnostics messages get included in CosmosException.java#getMessage():

    public String getMessage() {
        try {
            ObjectNode messageNode = mapper.createObjectNode();
            messageNode.put("innerErrorMessage", this.innerErrorMessage());
            if (this.cosmosDiagnostics != null) {
                this.cosmosDiagnostics.fillCosmosDiagnostics(messageNode, (StringBuilder)null);
            }

            return mapper.writeValueAsString(messageNode);
        } catch (JsonProcessingException var2) {
            return this.cosmosDiagnostics == null ? this.innerErrorMessage() : this.innerErrorMessage() + ", " + this.cosmosDiagnostics.toString();
        }
    }

Is there a way to exclude fillCosmosDiagnostics() when logging the exception? It's causing problems in our logging system because it can't handle these massive logs.

Why is this not a Bug or a feature Request?
This is not a bug because it's an intentional design. It could be a feature request if turning off CosmosDiagnostics isn't already supported.

Setup (please complete the following information if applicable):

• OS: MacOS
• IDE: IntelliJ
• Library/Libraries: com.azure:azure-cosmos:4.39.0

Information Checklist
Kindly make sure that you have added all the following information above and checkoff the required fields otherwise we will treat the issuer as an incomplete report

• [ na] Query Added
• [ x] Setup information Added

[ghost]

Thanks for the feedback! We are routing this to the appropriate team for follow-up. cc @kushagraThapar, @TheovanKraay

[fivetran-kevinzhao]

Hello any update here?