Understand how to Check the Status of Services

When: After platform changes

Ensure you know how to check the status of all SAS Viya servers ad hoc at any time

Know how to check whether all your SAS Viya services are running, by looking at the result of one or more tests of the services' health.

It can also be helpful to look at the health of the SAS Viya pods which host those services.

Example tools to use for these checks include:

The status and logs of the SAS Readiness pod. See Assessing SAS Viya Readiness [Blog].
The kubernetes CLI, kubectl [Doc], e.g. kubectl get svc, kubectl get pod and variations which filter the results of those
- Exec-ing into pods to see what processes are running in them, e.g.:
  - kubectl exec -it $(kubectl get pod -l launcher.sas.com/username=some_username --output=jsonpath={.items..metadata.name} ) -- some_bash_command where some_username is the name of a user who has launched a SAS Compute Server running a SAS Compute session, and some_bash_command is a command like top, or ps -ef which can reveal something about processes running inside the pod. Here is that command to look at the top-CPU-consuming processes inside a compute server pod, for a user called geladm:
    kubectl exec -it $(kubectl get pod -l launcher.sas.com/username=geladm --output=jsonpath={.items..metadata.name} ) -- top
SAS Viya Monitoring for Kubernetes [App] includes Grafana dashboards which give some insight into the status of services, pods and nodes on your SAS Viya platform. See also the documentation pages for this project in SAS's Help Center: About SAS Viya Monitoring for Kubernetes [Doc]
Lens [App], OpenLens [App], or K9s [App]
Observability tools provided by your cloud provider. See Monitoring and Logging on Cloud-Provider Platforms [Doc]
SAS Environment Manager includes a Servers page which can indicate the status of CAS servers.