Untab documentation
  • Overview
  • Architecture
  • Compatibility
  • Collected information
  • Authentication
  • Setup
    • First steps
    • Installing using the basic manifest
    • Installing using Helm
    • Checking agent status
    • Configuring access to cloud providers (optional)
    • Setting up access on AWS
    • Setting up access on Google Cloud Platform
  • Management
    • Managing user access
    • Troubleshooting
Powered by GitBook
On this page
  • Checking agent status via kubectl
  • Checking cluster status in the dashboard

Was this helpful?

  1. Setup

Checking agent status

PreviousInstalling using HelmNextConfiguring access to cloud providers (optional)

Last updated 5 years ago

Was this helpful?

Checking agent status via kubectl

You can check the agent status in the cluster by running:

kubectl get pods -n untab

You should see output like this:

NAME                          READY   STATUS    RESTARTS   AGE
node-exporter-gzxpj           2/2     Running   0          10s
node-exporter-jtqs6           2/2     Running   0          10s
node-exporter-pshll           2/2     Running   0          10s
...
untab-agent-fd5744b64-bgfjd   3/3     Running   0          10s

There should be one node-exporter pod per node, as well as the untab-agent pod. If you see a different output, please see the troubleshooting section (link below).

Checking cluster status in the dashboard

The Untab dashboard shows the status of each cluster. To see this, navigate to the "Status" page via the menu on the left-hand side of the screen.

A cluster will appear on this screen as soon as the agent starts running in the cluster. The icon and color of each cluster card indicates whether Untab is receiving all of the necessary data from the agent. A healthy cluster looks like this:

It takes about 15 minutes for all of the data to start flowing from the agent. During this time the cluster may appear in a "warning" state (yellow).

An unhealthy cluster would be yellow or red. If you are seeing this, please consult the troubleshooting section or .

contact us for help
Troubleshooting
Troubleshooting