IBM Business Automation Community Come for answers. Stay for best practices. All we’re missing is you. Join / Log in Ask a question
Have you ever been in the situation that something get wrong inside your User Management Service (UMS) installation and you want to find the cause, but you don't know how to start?This blog explains how to get the logs of the different UMS capabilities and the ICP4A operator and how to read the content of these.
volumes: - name: logs-backup persistentVolumeClaim: claimName: "cp4a-shared-log-pvc"
You can also specify a UMS specific log PersistentVolumeClaim in the Custom Resource file in the ums_configuration section:
ums_configuration: existing_claim_name_logstore: <your UMS PersistentVolumeClaim>
apiVersion: v1kind: Podmetadata: name: copy-log-podspec: containers: - name: alpine image: alpine:latest command: ["sleep", "infinity"] volumeMounts: - name: cp4a-shared-log-pvc # adapt this value if you defined an existing_claim_name_logstore mountPath: /data volumes: - name: cp4a-shared-log-pvc # adapt this value if you defined an existing_claim_name_logstore persistentVolumeClaim: claimName: cp4a-shared-log-pvc # adapt this value if you defined an existing_claim_name_logstore