Loading

×Sorry to interrupt
Uncaught ReferenceError: addCTracking is not defined
throws at https://kb.vmware.com/resource/KM_TealiumTrackingJS?v=0.5:100:1

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

Redirect selected log files to another machine or a Syslog Server (76325)

Last Updated: 6/11/2020Categories: How toTotal Views: 12420Language:
English

9 like this article

Subscribe to get an email
newsletter with new updates

9 people found this helpful Please provide article feedback:

Symptoms

With the default settings, we are getting far more messages than we want, and we would only really like VCSA to send Syslog messages at level "error" and above.

Resolution

Back up the syslog.conf file located at /etc/vmware-syslog
Edit the syslog.conf and replace *.* with the type of messages you want to forward
eg: *.warn;*.error;*.crit;*.alert;*.emerg @192.168.0.89:514;RSYSLOG_SyslogProtocol23Format

Log files to redirect

Option

Description

*

All log files are redirected to the remote machine.

info

Only informational log files are redirected to the remote machine.

notice

Only notices are redirected to the remote machine.Notice indicates normal but significant condition.

warn

Only warnings are redirected to the remote machine.

error

Only error messages are redirected to the remote machine.

crit

Only critical log files are redirected to the remote machine.

alert

Only alerts are redirected to the remote machine. Alert indicates that action must be taken immediately.

emerg

Only emergency log files are redirected to the remote machine. Emergency indicates that the system stopped responding and cannot be used.

Run the command systemctl restart rsyslog to restart the rsyslog service

Run  the following commands to test

logger -p syslog.info "Info test - this won't appear at syslog server"

logger -p syslog.warn "Warn test - this won't appear at syslog server"

logger -p syslog.error "Error test - this will appear at syslog server"

logger -p syslog.crit "Crit test - this will appear at syslog server"

Related Information

https://communities.vmware.com/thread/588518
https://docs.vmware.com/en/VMware-vSphere/6.7/com.vmware.vsphere.monitoring.doc/GUID-9633A961-A5C3-4658-B099-B81E0512DC21.html

Detectable by VMware SkylineTM

Actions

Copy

link to clipboard
copied!

Print

Language:
English

Attachments

Additional Resources

KB
•
适用于 vRA 8.0.0 HA 环境的修补程序解决了阻止某些服务在数据库故障切换事件后恢复的问题 (76222)

KB
•
vRealize Automation 7.x での Internet Information Services (IIS) アプリケーション プールのリサイクルの無効化 (76333)

Results 1-2 of 2

Ask The Community

Get answers quickly from VMware experts in the community

Post Subject

CONTINUE IN COMMUNITIES

Related Products:

VMware vCenter Server

Related Versions:

VMware vCenter Server Appliance 6.7.x

VMware vCenter Server Appliance 6.5.x

VMware vCenter Server Appliance 6.0.x

Take Our Survey

Support Assistant