Defining the storage for IBM RPA on Red Hat® OpenShift® Container Platform
Learn more about the storage considerations before using audit logs on the IBM Robotic Process Automation on Red Hat® OpenShift® Container Platform.
About this task
The IBM RPA operator has volumes to store log data: rpa-server and rpa-audit-syslog-sidecar.
rpa-server
The contrainer from the IBM RPA server. It can access log files to read and write on it.
rpa-audit-syslog-sidecar
The container to store and manage the audit logs over Rsyslog. This is the default storage for audit logs. It can access log files to read and write on it.
This container is enabled by the Fowarding Enabled switcher when you create or update your IBM RPA operator. For instructions, see Enabling forwarding for IBM RPA on Red Hat® OpenShift® Container Platform.
Procedure
Before you install the IBM RPA operator, create the AUDIT database. For more information, see Database requirements.
When you update the IBM RPA operator, the AUDIT database is created when data start be logging with computers or user actions.
What to do next
By default, the option to store logs on a database is enabled. If you disable this option, the table on the IBM RPA Control Center no longer updates with new data. For instructions on how to enable or to disable logging in the database, see Logging in the database.
After you capture and store data from audit logs, you can retrieve them by accessing the Audit log window on the IBM RPA Control Center. For procedures on how to access the log data, see Accessing Audit logs recordings.
You can also connect with a security information and event management (SIEM) system over Fluentd for monitoring and analysing log events. For more information, see Forwarding audit logs records on IBM RPA on Red Hat® OpenShift® Container Platform.