Troubleshooting IBM Business Automation Insights on Kubernetes

If event emission or data visualization does not work as expected, the following pages help you resolve issues.

Troubleshooting the BPM event emitter
To better follow up the activity of the BPM event emitter, you can enable tracing. If events are not flowing to the JMS queue or to Kafka, use the check lists to ascertain proper JMS configuration.
Troubleshooting the Case event emitter
To better follow up the activity of the Case event emitter, you can enable tracing. You can resolve JAR file conflicts, class loading, and user authentication errors. You can also replay events to regenerate your business data.
Troubleshooting the undefined case type in dashboards
If you see the case type value displayed as <Undefined> in some activity dashboards, create a scripted field to replace the predefined field for the display name of the case type.
Troubleshooting the Content event emitter
If you observe that no events are flowing to Kafka, there might be a problem with the Content event emitter configuration. Check the event handler configuration, the Content Platform Engine log, and the status of the messaging engine.
Troubleshooting the Content dashboard
The index pattern might be outdated in the Content dashboards. When indexing new fields in Elasticsearch, Kibana does not display the new fields.
Troubleshooting the ODM event emitter
You might observe that ODM events do not appear to be processed and stored in Elasticsearch.
Troubleshooting Apache Flink jobs
If you observe that no events are flowing to Elasticsearch and that Flink job logs report errors, explore possible diagnoses and solutions.
Troubleshooting Setup
If the bai-setup pod does not work as expected, here are diagnoses and solutions.

Parent topic: IBM Business Automation Insights specifics on Red Hat OpenShift