Viewing and copying log files in Kubernetes

The log files for each software component used within IBM FCII are externalized from each pod (Docker container). There is a shared file system accessible by all pods named /fci-exports.

Accessing log files through Kubernetes

Before you begin

Under /fci-exports, there is a directory for each Docker container:

fci-security-audit-data
security audit service
datastorefci-messaging
fci-cedm-data-store-data
es-datafci-cedm-integration-data
fci-cui-web

Ensure that all nodes have read and write access to /fci-exports.

Procedure

To view log information from the command line for Docker images managed by Kubernetes:

From the Kubernetes master node, log in as root, or if you enabled a non-root user, such as fciadmin, run the following command:

kubectl get pods

For example, if you have a system with the IBM FCII platform, output is similar to the following:

fcco-case-manager-fci-messaging-66d58bf8d-7lflv      8/8       Running     0          1d
fcco-case-manager-fci-solution-5f54c79f58-t4d9b      3/3       Running     0          1d
fcco-cedm-datastore-6599d4b89d-vstzl                 2/2       Running     0          1d
fcco-cedm-integration-6cc78f976-ddqdn                3/3       Running     0          1d
fcco-cedm-ui-5cbc77cc65-x5z4d                        1/1       Running     0          1d
fcco-common-scripts-bgq7n                            0/1       Completed   0          7d
fcco-common-ui-nginx-78b96966f5-s2v7f                1/1       Running     0          1d
fcco-common-ui-nodejs-67d4c7cbc5-lj25j               1/1       Running     3          1d
fcco-logging-es-cfc5dcd6d-btxdl                      1/1       Running     0          1d
fcco-logging-fb-4mkq9                                1/1       Running     0          1d
fcco-logging-fb-5fwhl                                1/1       Running     0          1d
fcco-logging-fb-5kz2n                                1/1       Running     0          1d
fcco-logging-fb-675cb                                1/1       Running     0          1d
fcco-logging-fb-7x2dt                                1/1       Running     0          1d
fcco-logging-fb-plppb                                1/1       Running     0          1d
fcco-logging-fb-rrz42                                1/1       Running     0          1d
fcco-logging-fb-srwsm                                1/1       Running     0          1d
fcco-logging-kb-7fdbc7d45c-h4wpl                     1/1       Running     0          1d
fcco-logging-ls-6f44b4f7d-kl2dd                      1/1       Running     0          1d
fcco-rms-datastore-b7dbc5c5f-fdbmc                   2/2       Running     0          1d
fcco-rms-designstudio-7c7dfcd8f8-mbghv               3/3       Running     0          1d
fcco-rms-odm-76c68c797f-th2hs                        3/3       Running     0          1d
fcco-rms-odm-datastore-6d48868fc4-znqpk              2/2       Running     0          1d
fcco-security-audit-app-55f44d7c4d-56sd4             3/3       Running     0          1d
fcco-security-audit-datastore-6d44f65d8-spt64        2/2       Running     0          1d
fcco-security-auth-nodejs-77c84d6794-4brfk           0/1       Running     0          10h
fcco-security-auth-nodejs-77c84d6794-96z48           0/1       Running     0          10h
fcco-security-auth-redis-5f5cf95646-dv72q            1/1       Running     0          1d

For containers that specify 1/1 in the Status column, run the following command:
```
kubectl logs container_name
```
For containers that specify more than one Ready container in the Status column, enter the following command:
```
kubectl logs pod_name -c container_name
```
For example:
```
kubectl logs fcco-case-manager-fci-solution-5f54c79f58-t4d9b -c message-log
```
If you run kubectl logs pod_name, a list of containers in the pod is displayed. You can use one of the container names to get the logs for that specific container.
DB2 containers specify datasource in the pod name. To view db2diag log files, enter the following command:
```
kubectl logs pod_name db2diag-log
```
For example, to view the CEDM DB2 log file in the prior example:
```
kubectl logs fcco-cedm-datastore-6599d4b89d-vstzl db2diag-log
```
To view information through Kibana using a browser, do the following:
1. Log in to the Kubernetes master node:
```
https://kubernetes_master_node:5601/
```
2. Log on to Kibana. When prompted, enter elasticuser for the user and the password specified in the fci-values.yaml file at installation time.
3. Click Discover to view log file information using Kibana. The log indexes all start with filebeat, so the index pattern to search through the log file is filebeat*. The time field used by the indexes is @timestamp. For example (no ID or password required):
  For more information about Discover, see the Kibana User Guide.