VMware {code} Community
chrissmith1
Enthusiast
Enthusiast
Jump to solution

Local plugin logging in vCenter 6.7.0.46000

How can plugin log files be configured in VCSA 6.7.0.46000? The SDK documentation doesn't seem to have been updated for this, and the previous "serviceability.xml" file no longer seems to exist.

We have an existing plugin in the field that is throwing errors with VCSA 6.7.0.46000 - but worked perfectly before the vCenter was upgraded; the indications are that vCenter has made a global change to SSL connection handling that breaks compatibility for existing plugins. We urgently need to enable higher-verbosity debug logging to isolate the cause - but appears that has also been changed...

There is also a confusing comment in the 6.7 Update 3j release notes: "Third-party plug-ins cannot use the Log4j package delivered by the vSphere Web Client: Third-party plug-ins cannot use the Log4j package delivered by the vSphere Web Client due to security considerations. Use the SLF4J library instead. This issue is resolved in this release."

Does that mean that logging from existing plugin packages using Log4j can or cannot be enabled? If not, was there any notification about this change posted here?

 

0 Kudos
1 Solution

Accepted Solutions
chrissmith1
Enthusiast
Enthusiast
Jump to solution

The "serviceability.xml" does exist, but the location has changed and is different between vCenter for Windows and VCSAs on 6.7 ("/configuration" on Windows, but "/conf" on VCSA):

https://kb.vmware.com/s/article/2011485

 

View solution in original post

0 Kudos
1 Reply
chrissmith1
Enthusiast
Enthusiast
Jump to solution

The "serviceability.xml" does exist, but the location has changed and is different between vCenter for Windows and VCSAs on 6.7 ("/configuration" on Windows, but "/conf" on VCSA):

https://kb.vmware.com/s/article/2011485

 

0 Kudos