Skip to main content
Every environment comes pre-installed with its own instance of open source Loki and Grafana. Grafana will be running on its own URL for each environment and must be used to see all logs collected from your environment. Grafana is simple to use yet very powerful in how you can customize the setup for yourself. Your application should be printing logs to STDOUT or STDERR. These logs will be collected automatically by pre-installed Loki and kept available for you to view inside Grafana dashboard.

​
See logs

Grafana dashboard can be opened from Monitoring tab, in Environment page. Logs are collected and kept organised under a Kubernetes namespace. Your application is hosted in a specific Kubernetes namespace using which you can filter and see logs under Explore section.

​
Tail logs from your terminal

Grafana is the place to search and correlate logs across your environment. When you just want to watch one service as it runs - during a deploy, or while reproducing a bug - ops logs streams the same output straight to your terminal:
--env and --svc take the environment and service names shown in your dashboard, or their ids. The stream stays open and prints new lines as they arrive - press Ctrl-C to stop. Every ready pod of the service is read at once, and each line is prefixed with the pod it came from so you can tell replicas apart:
The flags you will reach for most often:
Don’t have the CLI yet? Install it on macOS, Linux or Windows, then run ops login. See CLI usage for the full set of options, including -i to pick a single pod.

​
Custom dashboards

Grafana installation in each environment comes with pre-built dashboards to see infrastructure/system metrics. You can create new dashboards to see logs from different deployments/services in your application as needed.
See Grafana docs to learn more