Add option to trace eureka registration in v3 #592
Merged
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Depends upon zowe/zlux-app-server#336
v2 version of #591
This PR adds the property components.app-server.node.mediationLayer.traceTls
It is used to set enableTrace from the NodeJS TLS level https://nodejs.org/api/tls.html#tlscreateserveroptions-secureconnectionlistener
This is needed because it seems to be the only way to get handshake tracing for NodeJS.
There's a previous property, components.app-server.node.https.enableTrace but it is only for inbound request from clients.
This new property allows you to trace the connection this server gives out to the discovery server, as an outbound request instead.
This can reveal the cause of low level networking issues if they arise.
How to test
Enabling components.app-server.node.mediationLayer.traceTls will show plenty of TLS handshake information during eureka registration. With it off (default), you should notice nothing different.