search

F5Networks / f5-cloud-libs

Node.js libraries to assist in cloud deployments.
Apache License 2.0
29 stars 14 forks source link

[RFE] Improve readability of Service Discovery logs / improve diagnostics #8

Open alonsocamaro opened 5 years ago

alonsocamaro commented 5 years ago

Hi

Trying to figure out why a VM doesn't match a service tag by the Service Discovery function is challenging. From the logs there is no introspection of the filtering why a non empty list of VMs/NICs results in an empty list of VMs/NICs. Please see below for an example.

Note: from the log below please notice the <> annotations. I have removed part of the output because of security reasons. Please ask me directly for the actual log file.

2018-12-18T18:40:34.470Z debug: [pid: 7546] [scripts/getNodes.js] getNodes.js Getting NICs 2018-12-18T18:40:34.655Z silly: [pid: 7546] [lib/azureCloudProvider.js] virtualMachineScaleSets.list results: <nothing> 2018-12-18T18:40:34.668Z silly: [pid: 7546] [lib/azureCloudProvider.js] virtualMachineScaleSets.list results: <nothing> 2018-12-18T18:40:34.681Z silly: [pid: 7546] [lib/azureCloudProvider.js] virtualMachines.list results: <non empty list of the VMs> 2018-12-18T18:40:35.408Z silly: [pid: 7546] [lib/azureCloudProvider.js] networkInterfaces.list results: <non empty list of nics> 2018-12-18T18:40:35.409Z silly: [pid: 7546] [scripts/getNodes.js] getNodes.js nics [] 2018-12-18T18:40:35.410Z info: [pid: 7546] [lib/util.js] getNodes finished. 2018-12-18T18:40:35.409Z silly: [pid: 7546] [scripts/getNodes.js] getNodes.js vms [] 2018-12-18T18:40:35.410Z debug: [pid: 7546] [scripts/getNodes.js] getNodes.js no valid nics found, trying vms 2018-12-18T18:40:35.410Z debug: [pid: 7546] [scripts/getNodes.js] getNodes.js no valid pool nodes found

f5-gasingh commented 5 years ago

Hi alonsocamaro, I've created an internal issue #1194 to track this request. Thank you!