diff --git a/troubleshooting/_topics/providers.md b/troubleshooting/_topics/providers.md
new file mode 100644
index 000000000..97121ec0f
--- /dev/null
+++ b/troubleshooting/_topics/providers.md
@@ -0,0 +1,51 @@
+## Providers
+
+### VMware vCenter Provider
+
+If you are having issues with a VMware provider you can enable extensive debug
+logging which will log the raw XML payloads for all requests and responses between
+the vCenter and {{ site.data.product.title_short }}.
+
+There are two settings that you have to enable in Advanced Settings
+1. log.level_vim must be set to debug
+2. ems.ems_vmware.debug_vim_requests must be set to true
+
+With these two settings enabled you will see the full XML payloads in the vim log,
+here is a sample Login action:
+```
+[----] D, [2024-12-04T12:31:51.307304#554036:97f4] DEBUG -- vim:
+
+
+
+
+ SessionManager
+ user
+ pass
+
+
+
+[----] D, [2024-12-04T12:31:51.308114#554036:97f4] DEBUG -- vim:
+
+
+
+
+ 53e7183f-4db3-4e02-b62d-840b9a47fc31
+ user
+ user
+ 2024-12-04T17:31:51.307621525Z
+ 2024-12-04T12:31:51.307628585-05:00
+ en_US
+ en_US
+ false
+ 127.0.0.1
+ HTTPClient/1.0 (2.8.3, ruby 3.3.5 (2024-09-03))
+ 1
+
+
+
+
+
+```
+
+Depending on the payloads you are working with, they might overflow the journald `LineMax` and be cut off.
+If this is the case you can edit the `/etc/systemd/journald.conf` file and adjust the `LineMax` setting appropriately.
diff --git a/troubleshooting/index.md b/troubleshooting/index.md
index cda0bfdd6..0820a8e3e 100644
--- a/troubleshooting/index.md
+++ b/troubleshooting/index.md
@@ -4,3 +4,4 @@
# Troubleshooting
{% include_relative _topics/logging.md %}
+{% include_relative _topics/providers.md %}