HTTP/2 service monitoring

Last published : Sep 22, 2026
NetScaler appliance supports HTTP/2 monitors for monitoring the health status of HTTP/2 services.
HTTP/2 monitor can be configured in two different ways. Depending on the traffic type, you can configure an HTTP/2 monitor.
  • HTTP/2 Direct. You can configure HTTP/2 Direct for monitoring non-secure HTTP/2 services.
  • HTTP/2 SSL. You can configure HTTP/2 SSL for monitoring secure traffic over SSL. Enable the secure flag parameter in the HTTP/2 to monitor the SSL traffic.
The http2direct and http2ssl are the two different built-in monitors that are supported for the HTTP/2 protocol.
The following table lists the configuration types, and monitoring processes associated with each type.
Configuration type Probe Success criteria
HTTP/2 Direct TCP Connection; HTTP2 Connection preface & Settings Negotiation; HTTP2 Request HTTP/2 response status code must match the configured response code.
HTTP/2 SSL TCP Connection; SSL Handshake; HTTP2 Connection preface & Settings Negotiation; HTTP2 Request The server must always select ALPN with the HTTP/2 protocol and the HTTP/2 response status code must match the configured response code.
Related information

Bind the HTTP/2 monitor to a service by using the CLI

At the command prompt, type:
  • bind service <servicename> -monitorName <name>
  • bind service <servicename> -monitorName <name>
Example:
  • bind service s1 -monitorName http2direct
  • bind service s2 -monitorName http2ssl