BMC Helix IT Operations Management (ITOM) - How to check and collect Pod or Service Logs in OnPrem Deployment

Please refer to the below steps to review and collect the pod logs:

For Kubernetes:
kubectl get pod -n <namespace-of-ITOM>

For OpenShift:
oc get pod -n <namespace-of-ITOM>

To fetch the logs for a particular pod:
kubectl logs <pod-name> -n <namespace-of-ITOM>
oc logs <pod-name> -n <namespace-of-ITOM>

If there are two containers associated with a pod then use the following to fetch logs for a particular container:
kubectl logs <pod-name> -c <container-name> -n <namespace-of-ITOM>

Please note that the user can redirect the output of the pod log to a text file for sharing with the support team if further troubleshooting is required. Here's an example:

For a pod:
kubectl logs <pod-name> -n <namespace-of-ITOM> > pod1.txt
oc logs <pod-name> -n <namespace-of-ITOM> > pod2.txt

For a particular container:
kubectl logs <pod-name> -c <container-name> -n <namespace-of-ITOM> > pod1_1.txt
oc logs <pod-name> -c <container-name> -n <namespace-of-ITOM> > pod1_1.txt

Watch the video which covers how to collect logs how to check and collect Pod or Service Logs in BMC Helix IT Operations Management (ITOM) OnPrem Deployment