Requirements for Events Framework
To use the events framework, allocate enough disk space for event data and be familiar with the disk capacity requirements.
Database Sizing for Events
Disk space for a single event is estimated at an average of 1,500 bytes.
Caution
As the number of events increases, the increase in disk space is not a straight line. The projections below are rough estimates. Disk usage can vary in production and depends on the type of messages stored.
Number of Events | Disk Space |
---|---|
25 million | 38GB |
50 million | 58GB |
Data and Disk Capacity for Events
For information about the default events data retention period, database dumps with and without events data, disk compacting, and more, see Manage Data and Disk Capacity in the PCE Administration Guide.
Events Preview Runtime Setting
If you participated in the preview of Events in 18.1.0, you enabled it by configuring a setting in your PCE runtime_env.yml
file.
Warning
Remove preview parameter from runtime_env.yml
Before you upgrade to the latest release, you must remove v2_auditable_events_recording_enabled:true
from runtime_env.yml
. Otherwise, the upgrade will not succeed.
Removing this preview parameter does not affect the ongoing recording of “organization events” records.
To remove the Events preview setting:
Edit the
runtime_env.yml
file and remove the linev2_auditable_events_recording_enabled
:v2_auditable_events_recording_enabled: true
If you are not participating in other previews, you can also remove the line
enable_preview_features
.Save your changes.