URL monitoring is a module of JD’s unified monitoring. This short article mainly explains how to make good use of URL monitoring.
Let's first understand the two common WEB application network architectures on JD.com (except CDN):
No matter what kind of WEB application network architecture or its variants, it includes the following nodes: DNS server, VIP, NGINX, omcat; then how can we monitor the health of each node itself through the URL monitoring module of the JD unified monitoring system:
Monitoring Tomcat
There are many abnormal manifestations of Tomcat: abnormal startup, JVM process suspended animation, etc. Some of them can be monitored by the system survival alarm, and some cannot be monitored by the system survival alarm; The following configuration methods monitor tomcat exceptions:
The monitoring address replaces the domain name with the ip+: + http protocol port of tomcat where tomcat is located to ensure that the monitoring function can access tomcat.
monitor nginx
Nginx starts abnormally or the server in the upstream instruction is marked as the down attribute (and there is no backup node), which will cause nginx access abnormality. We can perform the following configuration to monitor this aspect:
A few points to note are: it must be requested by domain name, and specified as the host that needs to be configured, ip is the ip where nginx is located.
Monitor VIPs
When the VIP fails, our general method is to change the domain name resolution to quickly recover. The whole process is relatively simple, but how to quickly locate the VIP is more important. The following is the monitoring of the VIP with the help of URL monitoring. method:
The entire configuration method is not much different from the configuration of monitoring nginx. The only difference is that when monitoring VIP, the IP filled in is only VIP.
Monitor DNS
DNS is currently the most difficult to monitor. Some tool websites can borrow http://tool.chinaz.com/map.aspx, but there is no good effect. Monitoring through URL can only monitor the health status of the DNS service where the monitoring machine is located. , the following is the specific monitoring configuration:
Be sure to remember to check that you do not need to configure Host.
Here I recommend an architecture learning exchange group to everyone. Communication and learning group number: 744642380, which will share some
video recordings recorded by senior architects: Spring, MyBatis, Netty source code analysis, high concurrency, high performance, distributed, principles of microservice architecture, JVM
performance optimization, distributed architecture Wait for these to become the necessary knowledge system for architects. You can also receive free learning resources, which are currently benefiting