The Kafka service might be down

Follow the Prerequisites section to check the status of the Kafka Service

Open

Prerequisites

List of prerequisites that need to be fulfilled to ensure the working of all the features of the synergy product.

Firewall Whitelisting

The list of the endpoints need to be accessible from GV Management Server to keep the system updated.

*.k3s.getvisibility.com

git.rancher.io

docker.io

quay.io

gcr.io

registry.opensource.zalan.do

github.co

storage.googleapis.com

*.k3s.io

github.com

*.amazonaws.com

Following firewall rules should be set. Firewall Port Opening Matrix:

Supporting Services

Below services are involved in supporting the Getvisibility Platform. They need to be up and running

Kafka

Postgresql

Consul

K3s

K3 service is running as systemd service and its status can be known by running “systemctl status k3s” on the CLI of the Getvisibility Management Server.

If the service is not running then execute “sudo systemctl start k3s.service”

The basic level of health checkup of the remaining services can be performed by using the Rancher Web UI.

Status of individual services by following the steps mentioned below

The keyword “Active” is the current status of the service, which means the service is up.

Open

Note: The rancher Web UI link will be shared by the Getvisibility team

Collecting Logs

The logs of the service can be accessed by selecting the service and clicking on it

Click on the triple dot sign present on the right most end of the service and click on the “view logs”

Note: The rancher Web UI link will be shared by the Getvisibility team

Agent’s Service Logs

C:\Windows\ServiceProfiles\LocalService\AppData\Roaming\GVClient.Service\Logs

Agent Service logs

%appdata%\GVClient.Service

%appdata%\GVClient.Plugins

%appdata%\GVClient.UIWPF