While Kubernetes provides a number of ways to monitor the Pods and services, you can use the GigaSpaces administration tools to monitor the data grid (Spaces and Processing Units).
You can open the GigaSpaces REST Manager API and verify that your data grid was set up properly. You can access it from the minikube on your local machine or VM.
To get the IP address of your minikube, type the
minikube ip command in the command window. Then type the following URL (using the minikube IP address) in your browser to access the REST Manager API, with the port dependent on the service being used:
- Default LoadBalancer service
For information on how to use the REST Manager API, see the Administration Tools section of the documentation.
You can use the GigaSpaces CLI to monitor and administer the data grid.
To access the CLI, click the EXEC button in the Kubernetes dashboard to open a shell into the Management Pod. Next, navigate to the
/opt/gigaspaces/bin directory and start the GigaSpaces CLI.
At this point, you can use the CLI commands to monitor the data grid, making sure to set the –server with the Manager Headless Service name.
To view a list of Spaces, type the following command:
./insightedge --server=test-space-xap-manager-hs space list
To view the Data Type statistics, type the following command:
./insightedge --server=test-space-xap-manager-hs space info --type-stats test-space
For more information about the GigaSpaces CLI and available commands, see the Administration Tools section of the documentation.
You can monitor the status of the various Kubernetes components using the Kubernetes dashboard or kubectl, as described in Getting Started with GigaSpaces in Kubernetes .
The test-space-xap-manager-hs is one of the Kubernetes services. To list all of the Kubernetes services and exposed ports, type the following command:
kubectl get services
For more information on using the Kubernetes monitoring tools, refer to the Kubernetes documentation.
If the Kubernetes environment doesn't launch properly, you can investigate by checking the Init Container logs. An init container is always run before a GigaSpaces Pod is started. After the init container runs to completion, Kubernetes deploys the actual Pod (such as a Management Pod, Data Pod, etc.). So when you deploy a Space, for example, an init container runs first to verify that the Platform Manager is available, and then the Data Pod with the Space is created.
You can access this log in the Kubernetes dashboard, or run the following kubectl command to print the init container log in the command window:
kubectl logs test-xap-space-1-0 -c check-manager-ready