Comprehensive monitoring of NetScaler load balancing devices via Zabbix

NetScaler is the industry-leading service delivery platform. NetScaler supports a wide range of platforms with comprehensive application security settings, acceleration, and load balancing (including GSLB) capabilities. The main advantages of NetScaler are as follows:
1) Powerful load balancing: The NetScaler has a powerful L4/L7 load balancing function that sends application requests to the appropriate application resources and integrates global load balancing (GSLB) capabilities to intelligently direct client requests to the world's best available geographic location.
2) Web application Acceleration: NetScaler uses advanced optimization techniques such as dynamic caching, such as client and server TCP optimizations. Accelerate Web application performance by up to 5 times times or more.
3) Application Security: NetScaler provides SSL-based data encryption technology, as well as comprehensive L7 content filtering and L4/L7 dos protection to ensure that legitimate users can access the application at any time. In addition, NetScaler application Firewall provides a comprehensive application-layer attack defense against threats such as cross-site scripting attacks, SQL injection vulnerabilities, and cookie poisoning.
NetScaler monitoring mainly includes the system level (NETSCALERCPU, memory utilization, etc.) and application level (NetScaler vserver response time, return code, etc.) monitoring. System-level monitoring can be monitored via SNMP protocol, click to view the official NetScaler SNMP OID manual and its documentation.
Application-level monitoring is monitored from the business level through Shell/python scripts, either as agents or Zabbix trapper.
The system level mainly includes the following performance indicators:
1) NetScaler CPU usage percentage, CPU oid:1.3.6.1.4.1.5951.4.1.1.41.1.0.

650) this.width=650; "src=" Http://s3.51cto.com/wyfs02/M00/6C/E0/wKioL1VVWpfwrc32AAQMJ6vZO9g699.jpg "title=" Ns1.jpg "alt=" wkiol1vvwpfwrc32aaqmj6vzo9g699.jpg "/>2" NetScaler memory usage percentage, memories OID: 1.3.6.1.4.1.5951.4.1.1.41.2.0.

650) this.width=650; "src=" Http://s3.51cto.com/wyfs02/M01/6C/E5/wKiom1VVWS_TCDvEAAKJd2sbR30501.jpg "title=" Ns2.jpg "alt=" Wkiom1vvws_tcdveaakjd2sbr30501.jpg "/>

3) Number of NetScaler connections.

650) this.width=650; "src=" Http://s3.51cto.com/wyfs02/M01/6C/E0/wKioL1VVWrnDaIYwAAPCP_BunCA365.jpg "title=" Ns3.jpg "alt=" wkiol1vvwrndaiywaapcp_bunca365.jpg "/>tcpactiveserverconn:number of connections currently serving Requests
Tcpcurclientconn:number of client connections in NetScaler
Tcpcurserverconn:number of server connections in NetScaler
4) Number of NetScaler requests.

650) this.width=650; "src=" Http://s3.51cto.com/wyfs02/M01/6C/E5/wKiom1VVWVXw3WLVAAOwzEgEabY213.jpg "title=" Ns4.jpg "alt=" Wkiom1vvwvxw3wlvaaowzegeaby213.jpg "/>httptot11requests:http/1.1 requests received
httptot11responses:http/1.1 Responses Sent
Httptotrequests:http requests received, including http/1.0 and http/1.1 requests.
5) NetScaler port traffic, is generally a gigabit mouth, when the traffic is fast to reach the gigabit should have alarm.

650) this.width=650; "src=" Http://s3.51cto.com/wyfs02/M00/6C/E5/wKiom1VVWdfBWbtuAAP3Gb7R61Q388.jpg "title=" Ns5.jpg "alt=" wkiom1vvwdfbwbtuaap3gb7r61q388.jpg "/>6) NetScaler Vserver traffic.

650) this.width=650; "src=" Http://s3.51cto.com/wyfs02/M01/6C/E1/wKioL1VVW2WyQLcMAASBli1YqR8946.jpg "title=" Ns6.jpg "alt=" wkiol1vvw2wyqlcmaasbli1yqr8946.jpg "/>vsvrtotalresponsebytes:number of response bytes received on This service/vserver.
Vsvrtotalrequestbytes:the total number of the request bytes received on this service/vserver.
7) Number of NetScaler Vserver requests.

650) this.width=650; "src=" Http://s3.51cto.com/wyfs02/M02/6C/E6/wKiom1VVWfygDgJNAAR6_9oCCZc229.jpg "title=" Ns7.jpg "alt=" wkiom1vvwfygdgjnaar6_9occzc229.jpg "/>vsvrtotalrequests:the total number of requests received on this Service/vserver (this was applicable for Http/ssl servicetype).
Vsvrcursrvrconnections:the number of connections to the real servers behind the vSERVER.
Vsvrcurclntconnections:the number of current client connections.
8) NetScaler online monitoring.

NetScaler Online monitoring is mainly through ping to detect whether NetScaler online normal business.

The application level mainly includes the following performance indicators:

NetScaler Vserver HTTP response time and status is implemented primarily through the Python Pycurl module, placing all monitored vsrever domain names in a list listing and then looping through each Vserver response time and status code, Sent to Zabbix server by means of Zabbix trapper. This method is simpler and more efficient than the Zabbix method.

1) NetScaler Vserver HTTP response time.

650) this.width=650; "src=" Http://s3.51cto.com/wyfs02/M02/6C/E6/wKiom1VVXxvR_Uj2AATi5zMNKfI275.jpg "title=" Ns8.jpg "alt=" Wkiom1vvxxvr_uj2aati5zmnkfi275.jpg "/>

2) NetScaler Vserver HTTP status code.

650) this.width=650; "src=" Http://s3.51cto.com/wyfs02/M01/6C/E1/wKioL1VVYKWTzFuBAANPKLs-Ud4120.jpg "title=" Ns9.jpg "alt=" Wkiol1vvykwtzfubaanpkls-ud4120.jpg "/>

NetScaler vserver The following host HTTP response time and status is mainly achieved through Zabbix custom monitoring entries and Zabbix internal detection.

For Linux systems, it is implemented through custom monitoring items.

Userparameter=http.time,/usr/bin/curl--connect-timeout 10-o/dev/null-s-w%{time_total} "\ n" "http://127.0.0.1" Userparameter=http.code,/usr/bin/curl--connect-timeout 10-o/dev/null-s-w%{http_code} "\ n" "http://127.0.0.1"

For Windows systems, implemented through Zabbix internal instrumentation.

650) this.width=650; "src=" Http://s3.51cto.com/wyfs02/M01/6C/E6/wKiom1VVZS_wUgcCAAMHYmoubUY330.jpg "title=" Iis1.jpg "alt=" Wkiom1vvzs_wugccaamhymoubuy330.jpg "/>

3) NetScaler vSERVER the host HTTP response time below.

650) this.width=650; "src=" Http://s3.51cto.com/wyfs02/M00/6C/E1/wKioL1VVYZ_jPzxCAAQmWh93fGU090.jpg "title=" Ns10.jpg "alt=" Wkiol1vvyz_jpzxcaaqmwh93fgu090.jpg "/>

4) NetScaler Vserver below host HTTP status code.

650) this.width=650; "src=" Http://s3.51cto.com/wyfs02/M00/6C/E6/wKiom1VVYDKAkTlkAAMwbHGKASI573.jpg "title=" Ns11.jpg "alt=" Wkiom1vvydkaktlkaamwbhgkasi573.jpg "/>

Summary: The purpose of NetScaler vSERVER HTTP monitoring is to be able to record HTTP performance indicators in real time, to provide historical reference data for post-site performance optimization and fault troubleshooting, and to report timely when the website is abnormal. and NetScaler vSERVER under the host HTTP performance monitoring can promptly find due to program anomalies or other problems caused by a series of problems timely notify the system administrator. If you need a NetScaler monitoring template, please leave a message to request.

This article is from the "Simple Dreamer" blog, please be sure to keep this source http://sfzhang88.blog.51cto.com/4995876/1651513

Comprehensive monitoring of NetScaler load balancing devices via Zabbix