After installing your synthetics job manager, you can keep track of its maintenance and monitoring in several ways:
- Check if the synthetics job manager is healthy and working with the synthetics job manager status endpoint.
- See if a private location is under-provisioned and needs more synthetics job managers.
- Review your Docker logs or Kubernetes logs.
ヒント
You can also get notified of monitor failures with New Relic's alerts.
Check synthetics job manager status using HTTP
Connecting to a running synthetics job manager using HTTP is the easiest way to check if it's healthy and working. The container exposes port 8080. You can check the synthetics job manager with the following endpoints:
:8080/status/check: provides details about internal health checks that the minion performs.HTTP 200means the status is healthy.
Check if your private location requires more synthetics job managers
If your private location has multiple monitor checks queued up and you experience delays, you may need more synthetics job managers available to execute the monitor checks. In Kubernetes, this could be addressed with more ping runtime replicas and higher parallelism settings for API and browser runtimes.
To learn how to verify this, see Does my private location need more synthetics job managers?
Review logs
You can monitor your minion's health by looking at synthetics job manager container logs.
Enable debug logs
If you experience issues with your synthetics job manager, you can enable debug logs to help troubleshoot issues.
The default level of logging is set to only inform the user of key information and actionable errors. If this is insufficient, you can enable a more verbose logging by using the LOG_LEVEL environment variable.
重要
Be careful increasing the log level to DEBUG or TRACE. Higher log levels will record more data—that can help you debug, but also increases the risk of capturing sensitive data and storing sensitive data outside of your approved locations. To ensure data privacy and security, you should limit the types of information New Relic collects.
Retrieve Kubernetes debugging information
If you experience issues with your synthetics job manager in a Kubernetes container orchestration system environment, you can retrieve information about the synthetics job manager pod and the node it is running on to help troubleshoot.
To retrieve information for the synthetics job manager pod:
$kubectl describe pod -n YOUR_NAMESPACE YOUR_JOB_MANAGER_POD_NAMETo retrieve information for the node the synthetics job manager pod is running on, identify the node, and then:
$kubectl describe node NODE_ASSOCIATED_WITH_YOUR_JOB_MANAGER_POD_NAMEMonitor synthetics job managers with New Relic Infrastructure
New Relic's infrastructure monitoring supports advanced Docker monitoring and advanced Kubernetes monitoring.
If you are using the infrastructure agent to monitor these runner containers, configure at least one monitor to run each minute. The infrastructure agent will have more opportunity to notice and collect the above labels from the docker inspect of the container before it is deleted.