GitLab makes it easy to view the logs of running pods in connected Kubernetes clusters. By displaying the logs directly in GitLab in the Log Explorer, developers can avoid managing console tools or jumping to a different interface.
Kubernetes logs can be viewed directly within GitLab with the Log Explorer.
To learn more, see APM - Log Explorer.
Deploying to a Kubernetes environment is required to use Logs.
To access logs, you must have the right permissions.
You can access them in two ways.
Introduced in GitLab 12.5.
Go to Operations > Pod logs on the sidebar menu to display the Log Explorer.
Logs can be displayed by clicking on a specific pod from Deploy Boards:
- Go to Operations > Environments and find the environment
which contains the desired pod, like
- On the Environments page, you should see the status of the environment’s pods with Deploy Boards.
- When mousing over the list of pods, a tooltip will appear with the exact pod name and status.
- Click on the desired pod to display the Log Explorer.
The Log Explorer lets you filter the logs by:
Loading more than 500 log lines is possible from GitLab 12.9 onward.
Support for pods with multiple containers is coming in a future release.
Support for historical data is coming in a future release.
Introduced in GitLab 12.8.
When you enable Elastic Stack on your cluster, you can filter logs displayed in the Log Explorer by date.
Click Show last in the Log Explorer to see the available options.
Introduced in GitLab 12.7.
When you enable Elastic Stack on your cluster, you can search the content of your logs through a search bar.
The search is passed on to Elasticsearch using the simple_query_string Elasticsearch function, which supports the following operators:
|An OR operation.|
|Negates a single token.|
|An AND operation.|
|Wraps a number of tokens to signify a phrase for searching.|
||A prefix query.|
||Edit distance (fuzziness).|