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

How to adjust the purge interval for the vRealize Automation postgres database ebs_event table (70759)

Last Updated: 6/20/2019Categories: InformationalTotal Views: 3239Language:
Chinese (Simplified)JapaneseEnglish

Subscribe to get an email
newsletter with new updates

Please provide article feedback:

Details

In some cases, the ebs_event table in the vRealize Automation postgres database can grow quickly enough that it can fill the filesystem causing an outage. This article outlines how to adjust the purge interval for records in this table to prevent this from occurring.

This can be caused by a large number of event broker subscriptions being executed in a relatively short period of time.

The default interval for retention of the events is 90 days.

The default time for executing the event purge is 1 a.m. every day.

Note: Both of these values are adjustable.

Solution

ssh to the vRA VA.

Open the file /etc/vcac/vcac.properties

Notice the new entries added there:

# Configure the scheduled job for purging event logs.

# data.purge.eventlog.cron=0 0 1 * * ?

# Configure the retention period of the event logs in days.
# Setting this property will override settings done via the event log API.

# data.eventlog.retentionPeriod=90

# Configure a collection of event target types which will be ignored and not persisted.
# Setting this property will override settings done via the event log API.

# data.eventlog.blacklistedTargetypes=

Notice that the default retention period for events is 90 days. The purge job will run at 1:00 a.m. by default and events of all target types will be persisted. There is an option to blacklist some event target types to keep them from being persisted in the database.

Change the property values to match the environment needs.

Restart vcac-service /etc/init.d/vcac-service restart.

The procedure will have to be done for all vRA VA nodes of an HA environment.

Detectable by VMware SkylineTM

Actions

Copy

link to clipboard
copied!

Print

Language:
Chinese (Simplified)JapaneseEnglish

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 Aria Automation

Related Versions:

VMware vRealize Automation 7.6.x

Take Our Survey

Support Assistant