Solve and report simple problems with RDI
The following sections explain how you can get extra information from Redis Data Integration (RDI) to help you solve problems that you may encounter. Redis support may also ask you to provide this information to help you resolve issues.
If the installer fails with an error, then try installing again with the
log level set to DEBUG:
./install.sh -l DEBUG # Installer script
redis-di install -l DEBUG # Install command
This gives you more detail about the installation steps and can often help you to pinpoint the source of the error.
By default, RDI records the following logs in the host VM file system at
/opt/rdi/logs (or whichever path you specified during installation);
| Filename | Phase |
|---|---|
rdi_collector-collector-initializer.log |
Initializing the collector. |
rdi_collector-debezium-ssl-init.log |
Establishing the connector SSL connections to the source and RDI database (if you are using SSL). |
rdi_collector-collector-source.log |
Collector change data capture (CDC) operations. |
rdi_rdi-rdi-operator.log |
Main RDI control plane component. |
rdi_processor-processor.log |
RDI stream processing. |
Logs are recorded at the minimum INFO level in a simple format that
log analysis tools can use.
If you need to send a comprehensive set of forensics data to Redis support,
run the
redis-di dump-support-package
command from the CLI.
This command gathers the following data:
redis-di status commandconfig.yaml file