How do I collect Ververica Platform logs?
Note: This article applies to Ververica Platform Enterprise Edition 2.0 - 2.3.
Ververica Platform runs in a pod in a Kubernetes cluster. The pod consists of three containers: `appmanager`, `gateway`, `ui`. The logs from each container can be collected with the following command:
kubeclt logs <ververica-platform-pod> appmanager [--namespace <namespace>]
kubeclt logs <ververica-platform-pod> gateway [--namespace <namespace>]
kubeclt logs <ververica-platform-pod> ui [--namespace <namespace>]
If Ververica Platform runs in a dedicated Kubernetes namespace, supply the option `--namespace` when you run the command above.
When DEBUG level logs are needed, first turn on DEBUG Logging in Ververica Platform, then collect logs are indicated above.
When a Ververica Platform pod is deleted/killed (e.g., during an upgrade, or if a failure happens), you will not able able to collect logs from the original pod as it does not exists any more. Therefore, we recommend to have a logging infrastructure for your Kubernetes cluster where you can persist logs and do some query/analysis. This way, logs are stored in a separate storage and have a lifecycle independent of nodes/pods/containers. There are different Kubernetes logging solutions including commercial and open source ones, a few of which are listed in the section Related Information for your reference.