Loading

×Sorry to interrupt
CSS Error

Refresh

Cookie Preference Center

General Information on cookies

When you visit our website, we use cookies to ensure that we give you the best experience. This information does not usually directly identify you, but it can give you a more personalized web experience. Because we respect your right to privacy, you can choose not to allow some types of cookies by clicking on the different category headings to find out more and change your settings. However, blocking some types of cookies may impact your experience on the site and the services we are able to offer. Further information can be found in our

Cookie Policy.

Strictly Necessary

Strictly Necessary

Always Active

Strictly Necessary

Strictly necessary cookies are always enabled since they are essential for our website to function. They enable core functionality such as security, network management, and website accessibility. You can set your browser to block or alert you about these cookies, but this may affect how the website functions. For more information please visit www.aboutcookies.org or www.allaboutcookies.org.

Cookie Details‎

Performance

Performance

Performance

Performance cookies are used to analyze the user experience to improve our website by collecting and reporting information on how you use it. They allow us to know which pages are the most and least popular, see how visitors move around the site, optimize our website and make it easier to navigate.

Cookie Details‎

Please confirm your settings by refreshing the page.

Functional

Functional

Functional

Functional cookies help us keep track of your past browsing choices so we can improve usability and customize your experience. These cookies enable the website to remember your preferred settings, language preferences, location and other customizable elements such as font or text size. If you do not allow these cookies, then some or all of these services may not function properly.

Cookie Details‎

Advertising

Advertising

Advertising

Advertising cookies are used to send you relevant advertising and promotional information. They may be set through our site by third parties to build a profile of your interests and show you relevant advertisements on other sites. These cookies do not directly store personal information, but their function is based on uniquely identifying your browser and internet device.

Cookie Details‎

Advertising Cookies

Consent Leg.Interest

Select All Vendors

Select All Vendors

Select All Hosts

Select All

Clear Filters

Information storage and access

Apply

Confirm My Choices Reject All Allow All

My Subscriptions

Loading

Knowledge Base

Changing debug logging settings in VMware vRealize Operations Enterprise 1.0 (1034978)

Last Updated: 5/21/2022Categories: Total Views: 3931Language:
English

Subscribe to get an email
newsletter with new updates

Please provide article feedback:

Purpose

This article provides information about how modifying debug logging settings has changed in VMware vRealize Operations Enterprise 1.0 (formerly known as vCenter Operations Enterprise) .

Resolution

Previously, when setting /user/conf/collector/log4j.properties for specific adapter classes (for example, to increase debug logging), the CollectorService had to be restarted for the changes to take effect. Restarting the CollectorService impacts:

New lines of adapter classes

Changed lines of existing adapter classes (for example, from error to debug).

In VMware vRealize Operations Enterprise 1.0 (formerly known as vCenter Operations Enterprise), all changes to the log4j.properties file take effect without restarting the CollectorService. This is an advantage as restarting the CollectorService requires a change request and has an impact on the Alive system (that is, it can take a while for the restart to occur and can interrupt data collection).

Note: Although you do not have to restart the CollectorService, changes to log4j.properties file do not take effect immediately. The log4j.properties file has a watch time with a default value of one minute. This means that you have to wait up to one minute for the changes to be applied.

When you set the log level for a class in the log4j.properties file, log4j removes the default root log level from the class. However, when you remove a log level from log4j.properties file, log4j does not remove old log levels from the default root class. You must set the root log level explicitly.

For example, if you set these levels, AAA logs in debug level after the one minute delay:

log4j.rootLogger=error

log4j.logger.com.integrien.AAA=debug

If you then comment out or remove the line, AAA continues to log in debug level:

log4j.rootLogger=error

#log4j.logger.com.integrien.AAA=debug

Instead of simply removing the line or commenting it out, specifically set the level you want:

log4j.rootLogger=error

log4j.logger.com.integrien.AAA=error

After one minute, log4j applies this configuration and AAA logs in error level.

This is true for all classes in the VMware Operations Enterprise 1.0.

Detectable by VMware SkylineTM

Actions

Copy

link to clipboard
copied!

Print

Language:
English

Attachments

Additional Resources

KB
•
End Of General Availability of the Free vSphere Hypervisor (ESXi 7.x and 8.x) (2107518)

Result 1 of 1

Ask The Community

Get answers quickly from VMware experts in the community

Post Subject

CONTINUE IN COMMUNITIES

Related Products:

VMware vCenter Operations Enterprise

Related Versions:

VMware vCenter Operations Enterprise 1.0.x

Take Our Survey

Support Assistant