Monitoring and Logs

Logging

Each workload you deploy to your cluster, whether through Juno products or on your own will eventually run in a container.

For workloads within Juno, we provide you with the ability to view workstation logs directly in the web console, as well as related Kubernetes events. Additionally, services that make up Juno can all be viewed in ArgoCD and their logs inspected within it. To get a quick overview, check out this guide

For workloads you run outside of Juno, you can use Kubernetes to inspect the logs.

A container is simply a process that gets confined&contained by the runtime. All of the logs it outputs are gathered and available via the Kubernetes api, using the kubectl logs command. To inspect a workload not managed by Argo or Juno, you would look up the name of the pod and run kubectl logs -n <namespace> <pod name>

This is useful when troubleshooting ArgoCD itself.

To get comfortable navigating your cluster with kubectl, check out our cheatsheet

Monitoring

To better operate your cluster in production, you can leverage a monitoring stack. It will be able to give you insight into performance of your cluster hardware, as well as deployed workloads.

We are working on integrating a full monitoring stack into Juno's Terra store, to provide you an opinionated, out-of-the-box install.

While that's on the way, the Kubernetes ecosystem provides plenty of options - though they do require some setup and each have a learning curve. For workloads outside of Juno, we recommend the kube-prometheus-stack as a good starting point.