The Site24x7 Kubernetes Operator automates deployment and management of monitoring resources, eliminating manual YAML configuration and agent setup. It monitors your custom resources, provisions agents, and instruments new pods automatically. Use the troubleshooting tips below to resolve common issues quickly.

1. How do I check if the Operator is running?

   To ensure the Operator is running correctly, check the status of the pods in the site24x7 namespace:

   kubectl get pods -n site24x7

   You should see the following resources, based on the selected monitoring type:

   • site24x7-operator deployment pod
   • site24x7-agent DaemonSet pods
   • site24x7-kube-state-metrics deployment pod
   • site24x7-cluster-agent deployment, based on node count
   • site24x7-apminsight-dataexporter-daemonset pods, if Full-Stack Observability is selected
   • site24x7-csi-driver DaemonSet pods, if Full-Stack Observability is selected

   
   To view the Operator logs, run:

   kubectl logs <operator-pod-name> -n site24x7

   This helps confirm that the Operator pod is active and that there are no errors during startup.

2. How can I verify my custom resource configurations?

   Make sure the configurations selected in the site24x7k8s custom resource are created and configured correctly.

   kubectl get site24x7k8s site24x7k8s-resource -n
   site24x7 -o yaml

   This allows you to verify the configurations specified in the site24x7k8s custom resource.

3. How do I check if APM agents are injected into pods?

   To confirm that APM agents are injected into application pods:

   kubectl describe pod <pod-name> -n <namespace>

   Look for the site24x7-apminsight-csi volume, volume mounts in each container, and APMINSIGHT-related environment variables added by the mutating webhook. These indicate that your application pod has been successfully mutated and injected with the required APM configurations.

4. How can I view agent logs inside a pod?

   Access the pod to check agent files and configurations:

   kubectl exec -it <pod-name> -n <namespace> --
   /bin/bash

   Agent logs can be found at:

   /opt/site24x7/apminsight/agents

Common issues and fixes

• The pods are not monitored: Verify the monitorAllPods setting. If it’s disabled, ensure the includePodLabels or excludePodLabels are correctly configured and that your pods have the appropriate labels applied.
• The Operator pod is not running: Ensure that your cluster administrator has the required permissions to deploy the Site24x7 Operator and its resources. For more information, refer to the Site24x7 Kubernetes Operator documentation.
• The metrics are missing in the Site24x7 console: Ensure that all the relevant monitoring pods are running successfully. For information on the pods deployed by the Site24x7 Operator and how to verify their status, refer to question 1.

Related articles

• Site24x7 Kubernetes Operator
• Site24x7K8s Custom resource specification reference
• Migrate from traditional Kubernetes monitoring to the Site24x7 Kubernetes Operator