Troubleshooting Workforce Insights
If you see an error when you enable Workforce Insights, do the following steps to resolve
it.
On Kubernetes, Workforce Insights is served as a single Docker container inside a pod. A Kubernetes service does load-balancing across a set of pods. The number of pods and autoscaling configuration can be specified in the custom resource definition. For more information, see Configuring Workforce Insights.
Checking pod status and pod logs
If you see an error when you enable Workforce Insights, do the following steps to determine
the root cause.
- Check the status of the workforce_insights pod.
- List all the pods in the targeted namespace and find the name of the workforce_insights
pod.
oc get pods -n <NAMESPACE>
- Check the state of the workforce_insights pod and make sure it's
running.
oc get pod <POD_NAME>
- List all the pods in the targeted namespace and find the name of the workforce_insights
pod.
- Access the pod logs by running the following
command:
If you have more than one workforce_insights pod, the request from IBM® Business Automation Workflow might be routed to any of the pod replicas. You might need to check more than one pod to find the error.oc logs -f <POD_NAME>
Debug trace | Resolution |
---|---|
BAI time series data fetching has failed | Check run.log to get the Elasticsearch details, and test whether the Elasticsearch connection is working. |
Process event data is empty, and workforce insights can't be computed | There is no activity time series event data in Elasticsearch. Run the process to populate Elasticsearch with event data. |
Troubleshooting IBM Business Automation Workflow
To enable logging for Business Automation Workflow, follow the instructions in Enabling tracing for BPM event emitter and Machine Learning Server.
Troubleshooting Business Automation Insights
Workforce Insights relies on Business Automation Insights for data, so some problems can be solved by troubleshooting Business Automation Insights. See Troubleshooting.