VMware ESXi and vSphere Cluster Management
Configure vCenter Server Log Levels
Learn what each vCenter Server logging level records and how to change it in the vSphere Web Client for troubleshooting and VMware Support.
vCenter Server is the central management service for vSphere inventory, ESXi hosts, virtual machines, and related platform operations. Its logs provide evidence about normal activity, warnings, failures, and diagnostic behavior.
A log level is a verbosity threshold that determines which classes of messages vCenter Server records. Choosing a level is a balance: higher verbosity can provide more useful troubleshooting detail, but it also creates more log data and can consume storage faster.
vCenter Server Logging Level Hierarchy
The supported levels, from least to greatest detail, are none, error, warning, information, verbose, and trivia. Except for none, each higher level includes the message categories provided by the levels below it.
| Level | Relative verbosity | Message categories included | Typical use | Operational caution |
|---|---|---|---|---|
| none | Disabled | No messages for the applicable setting | Only when logging must be suppressed under an explicitly approved procedure | Useful evidence is not captured; use with deliberate operational approval |
| error | Lowest enabled detail | Error messages only | Confirming that failures are occurring while minimizing log volume | Warnings and ordinary operational context are omitted |
| warning | Low | Warning and error messages | Reviewing nonfatal concerns and failures | Informational activity and additional diagnostic context are omitted |
| information | Normal operational detail | Informational, warning, and error messages | Routine production operation | Recommended as the normal setting |
| verbose | High | Verbose diagnostics plus informational, warning, and error messages | Targeted troubleshooting or a support-requested collection window | Can increase log volume quickly; use temporarily |
| trivia | Highest | Trivia messages plus every lower-level category | Highly detailed, targeted investigation when specifically needed | Produces the greatest volume; monitor storage and restore the normal level promptly |
What each level means
- None: Disables logging for the controlled vCenter Server logging setting. It should not be used casually because future diagnostic evidence will be unavailable.
- Error: Records error conditions only. This is appropriate when an intentionally small logging footprint is more important than warnings and normal activity.
- Warning: Records warnings and errors. It can help identify recurring nonfatal concerns without recording ordinary informational messages.
- Information: Records informational, warning, and error messages. This is the normal operational level because it preserves useful context without the volume of elevated diagnostic levels.
- Verbose: Adds verbose diagnostic messages to the information, warning, and error categories.
- Trivia: Records the most detailed trivia messages as well as every lower-level category. It is the maximum-detail setting.
Choosing an Appropriate Log Level
Use the lowest level that still captures the evidence needed for the task. Reducing verbosity can conserve storage, but it can also remove context needed to understand a problem.
| Situation | Recommended level | Why | When to revert |
|---|---|---|---|
| Routine production operations | Information | Preserves normal operational context without the extra volume of diagnostic levels | Keep this level during normal operation |
| Failures must be confirmed with minimal log volume | Error | Captures failed conditions while excluding warnings and ordinary informational activity | Return to information when the reduced footprint is no longer required |
| Recurring nonfatal concerns need review | Warning | Captures both warnings and errors | Return to information after reviewing the condition |
| An intermittent problem is being investigated | Verbose or trivia for a limited collection window | Provides additional diagnostic detail for reproduction or analysis | Return to information as soon as evidence collection ends |
| Logging must be temporarily suppressed under an approved procedure | None | Disables the applicable logging setting | Re-enable an appropriate level immediately after the approved interval |
Change the vCenter Server Log Level in the vSphere Web Client
The vSphere Web Client is the web-based administration interface used for this procedure. You need basic inventory navigation skills, the ability to identify the vCenter Server object, and appropriate permissions to edit vCenter Server settings.
- Sign in to the vSphere Web Client.
- In the inventory, select the vCenter Server object whose logging setting you want to change.
- Open Manage.
- Select Settings.
- Open General.
- Use the Edit control for the General settings.
- In the edit dialog, choose Logging settings.
- Select the required log level: none, error, warning, information, verbose, or trivia.
- Save the change.
- Reopen or review the vCenter Server settings and verify that the selected level is displayed.
Select vCenter Server in inventory > Manage > Settings > General > Edit > Logging settings > choose log level > save
The saved logging-level change is applied immediately. A vCenter Server restart is not required. The setting affects log entries generated after the change; it does not retroactively add detail to records that were already written.
Change Behavior and Operational Impact
- Immediate effect: The new threshold applies as soon as the saved setting is accepted.
- No restart: Do not restart vCenter Server solely to activate this logging-level change.
- Future entries only: Existing log records retain the detail that was available when they were written.
- Storage monitoring: Elevated levels can increase log volume. Check available storage and monitor log growth for the entire troubleshooting window.
- Restore the baseline: Return the setting to information after troubleshooting or support data collection is complete.
Troubleshooting Examples
VMware Support requests more detailed diagnostics
- Record the existing logging level.
- Raise the level to verbose or trivia only as requested by VMware Support.
- Reproduce or observe the problem during the requested interval.
- Monitor log storage consumption while the elevated level is enabled.
- Restore information after collection ends.
Expected troubleshooting details are missing
The configured threshold may be too low for the diagnostic messages needed. Temporarily increase the setting to information, verbose, or trivia as appropriate, reproduce the condition, and then return to information. A higher level should be selected deliberately rather than left enabled indefinitely.
Log volume grows rapidly after a settings change
Verbose or trivia logging is a likely cause. Confirm that the troubleshooting collection is complete, return the level to information, and assess available log storage. Preserve any required logs before retention or rotation removes them.
An administrator expects a restart before the change works
A restart is not required for this setting. Confirm that the new selection was saved and that the vCenter Server settings display the selected level. The change is active immediately.
Exam-Relevant Notes
- Know the order from least to greatest detail: none, error, warning, information, verbose, trivia.
- Information is the normal operational setting.
- Each higher enabled level includes the lower-level message categories.
- None disables logging for the applicable setting.
- Changing the level takes effect immediately and does not require a vCenter Server restart.
- Changing the level affects future log entries, not existing records.
- Verbose and trivia should be time-limited, and the setting should be returned to information after troubleshooting.
Related Administration Topics
For broader vSphere administration practice, review VMware ESXi Online Course, adding an ESXi host to the vCenter Server inventory, and assigning permissions. Understanding inventory selection and permissions helps avoid errors when editing vCenter Server settings.