Add vmId to the Rntbd Health Check Error Message

[nehrao1]

Description

Issue 42811
Currently vmId is part of our client-side diagnostics. However, diagnostics can only be obtained if an operation succeeds or fails - if it hangs, we will not see anything. There was a WMT Sev2 where we saw channel health check failure logs (the log itself has the source and destination IP) but not the vmId, so we couldn't diagnose the VM well enough. With this change, the vmId can be extracted from health check logs and correlated so we can get VM level visibility.

All SDK Contribution checklist:

• The pull request does not introduce [breaking changes]
• CHANGELOG is updated for new features, bug fixes or other significant changes.
• I have read the contribution guidelines.

General Guidelines and Best Practices

• Title of the pull request is clear and informative.
• There are a small number of commits, each of which have an informative message. This means that previously merged commits do not appear in the history of the PR. For more information on cleaning up the commits in your PR, see this page.

Testing Guidelines

• Pull request includes test coverage for the included changes.

[azure-sdk]

API change check

API changes are not detected in this pull request.

[FabianMeiswinkel]

Left one blocking comment

[tvaron3]

LGTM besides some small comments

[FabianMeiswinkel]

LGTM - Thanks!

[jeet1995]

One suggestion is to modify the logs when requests see cancellation or transit timeouts. It is not fully clear whether we'll definitely have diagnostics in these scenarios (or at least not clear to me :P) so it would not hurt to have clientVmId or equivalent here too.

[jeet1995]

LGTM - thanks!

[jeet1995]

/azp run java - cosmos - tests

[azure-pipelines]

Azure Pipelines successfully started running 1 pipeline(s).

[nehrao1]

/check-enforcer override