Kubernetes Dashboard - Quick Integration

Overview of this Guide

This guide is wallthrough to get started integrating RealOpInsight with Kubernetes in a few minutes using a Docker image. For other installation options, i.e. using binary packages or a virtual machine image, please refer to our complete Installation Guide.

At the end of this guide you will see how RealOpInsight provides easy yet powerful alternative Kubernetes dashboards for operations monitoring.

Before you begin

The below steps assume that:

  • You have a Kubernetes cluster or Minikube setup accessible from your local machine.
  • You can enable a proxy access to the Kubernetes API from your local machine as follows:
$ kubectl proxy --port=8080

Start a RealOpInsight Docker Instance

The following command will start a RealOpInsight Docker instance in background.

    $ docker run -d --name realopinsight --publish 4583:4583 rchakode/realopinsight

Remark that this command allows to bind the RealOpInsight web interface port (4583) to the local machine.

Inside the container, binaries, logs, and many other configuration files are located at /opt/realopinsight/.

Connect to RealOpInsight Interface

The RealOpInsight Web Interface is available at the following URL:

The default administrator credentials are admin/password.

For a prodution setup and must be kept secured the default password must be changed as quick as possible.

Integrate Kubernetes as Monitoring Data Source

You can proceed as follows in order to integrate Kubernetes as a monitoring data source:

  • Log into RealOpInsight as administrator (default credentials: admin/password).
  • Select the menu Monitoring Sources to fill in the monitoring source settings.
  • Set the field Monitoring Source Type to Kubernetes.
  • Set the field Monitor API Base URL to (assuming that you started a proxy access to Kubernetes API as described previously).
  • Leave the other fields as is.
  • Click on the button Add as source.
  • When prompted, select Source0 as Source Id.
  • Click on Apply to save the changes.
  • On success you shall see a message confirming that.

For this quickstart guide a single source is enough, but you can repeat the above steps to add as many monitoring sources as you want to integrate with RealOpInsight.

Introducing Kubernetes Namespace Application Dashboard

After a successful configuration of a Kubernetes source, RealOpInsight automatically discovers all services in Kubernetes and grouped them by namespace in what is called Namespace Application Dashboard. A Namespace Application Dashboard is defined by the set of all services belonging to a given namespace in Kubernetes. It’s organized as a dependency graph where each service is bound to its related pods, which each is in turn bound to the containers that compose it. See an illustration on the figure hereafter.

By this way RealOpInsight provides a high level, yet comprehensive view on services within each namespace. Ultimately, RealOpInsight allows you to build dashboards consisting in one or more namespace views, which you can assign to your operations teams in an effective and intelligent way, in regard of your internal operational processes and policies.

Namespace Application Dashboard

Please read our Overview about RealOpInsight Application Dashboard if needed.

As administrator you can preview and check the Application Dashboard for any single operation view before assigning it for operations.

  • Log into RealOpInsight as administrator.
  • Select the menu Manage Views to see the list of managed views, it shall contain entries related to the namespaces you have in Kubernetes sources you already configured. Each entry is prefixed with the Id of the monitoring source (e.g. Source0:kube-system for namespace kube-system in Source0.
  • Select the menu Preview.
  • Select an entry in the list of managed views (e.g. select Source0:kube-system for this tutorial).
  • Click on Apply to display the Application Dashboard.
  • Click on the button to refresh the views (service map, service tree, message panel).

On our example we can see that there is a problem with a Prometheus pod, which, as shown in the message panel, has been evicted due to low resource on the node). The event impact is easily is highlighted using the tree view, the service map and the event console.

Executive Dashboard

Please read our Introduction about Executive Dashboard if needed.

As illustrated on the figure hereafter, the Executive Dashboard can consist of no, one, or many namespace items. It’s organized like a grid with configurable number of columns. The displayed items should have be explicitely assigned to the logged operator prior to the login. Each item is the grid provides a summary of the status of microsservices within the associated namespace.

The rest of this section will describe how to create Executive Dashboards and use them.

Create a Operator User

  • Log into RealOpInsight as administrator.
  • Select the menu New User.
  • Fill in the user information:
    • Password must have at least six (6) characters in two classes (upper/lower cases, digits, special characters, etc.).
    • Ensure to select Operator as User Role.
    • The property Dashboard Tiles Per Row allows to set the number of columns for the Executive Dashboard.
  • Click on Submit to save the changes.

Assign Operations Views

  • Log into RealOpInsight as administrator.
  • Select the menu Manage Views.
  • Select an operator in the user selection list at left.
  • Select one or several items in the list of business applications at the right.
  • Cick on Assign to apply the changes.

Operate Executive Dashboard

  • Log in as operator
  • On login the operator Executive Dashboard will be displayed with the items assigned to him, as shown on the screenshot below.
  • You can select a business application tile to open the associated Application Dashboard.
  • When an Application Dashboard is active, you can select Executive View to go back to the Executive Dashboard.

This is the end of this quickstart of RealOpInsight, please follow the below links to move forward with advanced use.