Access agent pod and share logs for troubleshooting

How to access agent pod and share logs for troubleshooting?

  1. Log in to your Kubernetes cluster.
  2. Get the agent pods using the below command:
    kubectl get pods --selector=app=site24x7-agent
  3. Access the pods,which you want to troubleshoot using the below command:
    kubectl exec -it {pod_name} -- /bin/bash
  4. Navigate to the agent logs folder: cd /opt/site24x7/monagent/logs
  5. Zip them and send it to support@site24x7.com


    • Related Articles

    • How to identify and resolve conflicts between other APM products and the APM Insight .NET agent

      Problem statement: You are experiencing either of the below issues and suspect that another APM product is interfering with the Site24x7 .NET agent. 1. The .NET monitor is not created under APM > APM Insight > Applications, even after the .NET agent ...

    • Troubleshooting false positive alerts in monitoring

      Problem False positive alerts are being generated. Possible cause The monitoring system is down in some locations. The Website monitor might be configured for one location, such as Seattle, but may appear down when accessed from another location, ...

    • Troubleshoot the Error 404 and Error 99 for RabbitMQ

      When installing the RabbitMQ plugin, you may encounter the following errors: HTTP Error 404: Not Found: This error usually occurs when Site24x7's RabbitMQ monitoring plugin attempts to access the /api/overview page of RabbitMQ, but the resource ...

    • Possible reasons for website unavailability

      Site24x7 monitors the availability of your website by sending an HTTP request to the webserver and checks the status code of the returned response. A 200 OK success response indicates that the website is available. We will consider a website ...

    • Troubleshooting steps when no data is received from the SQL server

      As we use "Perfmon" to fetch data for Microsoft SQL monitoring, please check if the counters related to SQL are present in the user's perfmon. Please follow the steps below: Open the server machine in which the issue is occurring. Start -> Run and ...