lbmonbindings_servicegroup_binding

Last published : Oct 30, 2026
Binding object showing the servicegroup that can be bound to lbmonbindings.
Related information
Configuration

Properties

(click to see Operations )
Name Data Type Permissions Description
monitorname <String> Read-write The name of the monitor.
Minimum length = 1
servicegroupname <String> Read-write The name of the service group.
boundservicegroupsvrstate <String> Read-only The state of the servicegroup.
Possible values = ENABLED, DISABLED
servicetype <String> Read-only The type of service.
Possible values = HTTP, FTP, TCP, UDP, SSL, SSL_BRIDGE, SSL_TCP, DTLS, NNTP, RPCSVR, DNS, ADNS, SNMP, RTSP, DHCPRA, ANY, SIP_UDP, SIP_TCP, SIP_SSL, DNS_TCP, ADNS_TCP, MYSQL, MSSQL, ORACLE, MONGO, MONGO_TLS, RADIUS, RADIUSListener, RDP, DIAMETER, SSL_DIAMETER, TFTP, SMPP, PPTP, GRE, SYSLOGTCP, SYSLOGUDP, FIX, SSL_FIX, USER_TCP, USER_SSL_TCP, QUIC, IPFIX, LOGSTREAM, LOGSTREAM_SSL, MQTT, MQTT_TLS, QUIC_BRIDGE, DOT, ADNS_DOT, HTTP_QUIC, ADNS_DOH, KAFKA_BROKER
monstate <String> Read-only The configured state (enable/disable) of Monitor on this service.
Possible values = ENABLED, DISABLED
__count <Double> Read-only count parameter

Operations

(click to see Properties )
  • GET
  • COUNT
Some options that you can use for each operations:
  • Getting warnings in response: NITRO allows you to get warnings in an operation by specifying the 'warning' query parameter as 'yes'. For example, to get warnings while connecting to the NetScaler appliance, the URL is as follows:
    http:// <netscaler-ip-address> /nitro/v1/config/login?warning=yes
    If any, the warnings are displayed in the response payload with the HTTP code '209 X-NITRO-WARNING'.
  • Authenticated access for individual NITRO operations: NITRO allows you to logon to the NetScaler appliance to perform individual operations. You can use this option instead of creating a NITRO session (using the login object) and then using that session to perform all operations,
    To do this, you must specify the username and password in the request header of the NITRO request as follows:
    X-NITRO-USER: <username>
    X-NITRO-PASS: <password>
    Note: In such cases, make sure that the request header DOES not include the following:
    Cookie:NITRO_AUTH_TOKEN= <tokenvalue>
*Note: * Mandatory parameters are marked in red and placeholder content is marked in green

get

URL: http:// <netscaler-ip-address> /nitro/v1/config/lbmonbindings_servicegroup_binding/ monitorname_value<String> Query-parameters: filter http:// <netscaler-ip-address> /nitro/v1/config/lbmonbindings_servicegroup_binding/ monitorname_value<String> ? filter=property-name1:property-value1,property-name2:property-value2
Use this query-parameter to get the filtered set of lbmonbindings_servicegroup_binding resources configured on NetScaler.Filtering can be done on any of the properties of the resource.
pagination http:// <netscaler-ip-address> /nitro/v1/config/lbmonbindings_servicegroup_binding/ monitorname_value<String> ? pagesize=#no;pageno=#no
Use this query-parameter to get the lbmonbindings_servicegroup_binding resources in chunks.
HTTP Method: GET
Request Headers:
Cookie:NITRO_AUTH_TOKEN= <tokenvalue>
Accept:application/json
Response: HTTP Status Code on Success: 200 OK
HTTP Status Code on Failure: 4xx <string> (for general HTTP errors) or 5xx <string> (for NetScaler-specific errors). The response payload provides details of the error
Response Header:
Content-Type:application/json
Response Payload:
{  "lbmonbindings_servicegroup_binding": [ {
"monitorname":<String_value>,
"servicegroupname":<String_value>,
"boundservicegroupsvrstate":<String_value>,
"servicetype":<String_value>,
"monstate":<String_value>
}]}

count

URL: http:// <netscaler-ip-address> /nitro/v1/config/lbmonbindings_servicegroup_binding/ monitorname_value<String> ? count=yes HTTP Method: GET
Request Headers:
Cookie:NITRO_AUTH_TOKEN= <tokenvalue>
Accept:application/json
Response: HTTP Status Code on Success: 200 OK
HTTP Status Code on Failure: 4xx <string> (for general HTTP errors) or 5xx <string> (for NetScaler-specific errors). The response payload provides details of the error
Response Header:
Content-Type:application/json
Response Payload:
{"lbmonbindings_servicegroup_binding": [ { "__count": "#no"} ] }