Logs

Logs produced by running services are collected and stored persistenly. You can inspect service logs as they are being produced or filter them by specifying a timeline. To inspect the service logs, simply go into Project > Service > Logs page.

Log Capturing

Yelken collects outputs written to stdout and stderr by your application at runtime. Logs are composed of entries that are separated by new line.

Inspecting Logs

Yelken allows you to inspect logs as services produce them (live) or filter logs produced at a given timeline (history).

In live mode, logs will be displayed as they come. Yelken by default uses 5 minutes offset while displaying live logs. This means that you will first see logs produced within the 5 minutes when you start displaying the logs.

In history mode, you can specify a start time and end time that will display all the logs produced between these two times. You can also leave the end time empty to inspect all logs produced between start time and now.

Yelken displays a service's container logs separately. You can inspect a container's logs by choosing it in the select box. This is helpful for application services as they contain more than one container.

Retention Policy

Yelken currently keeps the logs for at least 3 days. However, if your service produces excessive logs, this period can be shortened for the specific service.