You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: docs/dyn/monitoring_v3.projects.uptimeCheckConfigs.html
+6
Original file line number
Diff line number
Diff line change
@@ -122,6 +122,7 @@ <h3>Method Details</h3>
122
122
"matcher": "A String", # The type of content matcher that will be applied to the server output, compared to the content string when the check is run.
123
123
},
124
124
],
125
+
"disabled": True or False, # Whether the check is disabled or not.
125
126
"displayName": "A String", # A human-friendly name for the Uptime check configuration. The display name should be unique within a Cloud Monitoring Workspace in order to make it easier to identify; however, uniqueness is not enforced. Required.
126
127
"httpCheck": { # Information involved in an HTTP/HTTPS Uptime check request. # Contains information needed to make an HTTP or HTTPS check.
127
128
"acceptedResponseStatusCodes": [ # If present, the check will only pass if the HTTP response status code is in this set of status codes. If empty, the HTTP status code will only pass if the HTTP status code is 200-299.
@@ -223,6 +224,7 @@ <h3>Method Details</h3>
223
224
"matcher": "A String", # The type of content matcher that will be applied to the server output, compared to the content string when the check is run.
224
225
},
225
226
],
227
+
"disabled": True or False, # Whether the check is disabled or not.
226
228
"displayName": "A String", # A human-friendly name for the Uptime check configuration. The display name should be unique within a Cloud Monitoring Workspace in order to make it easier to identify; however, uniqueness is not enforced. Required.
227
229
"httpCheck": { # Information involved in an HTTP/HTTPS Uptime check request. # Contains information needed to make an HTTP or HTTPS check.
228
230
"acceptedResponseStatusCodes": [ # If present, the check will only pass if the HTTP response status code is in this set of status codes. If empty, the HTTP status code will only pass if the HTTP status code is 200-299.
@@ -349,6 +351,7 @@ <h3>Method Details</h3>
349
351
"matcher": "A String", # The type of content matcher that will be applied to the server output, compared to the content string when the check is run.
350
352
},
351
353
],
354
+
"disabled": True or False, # Whether the check is disabled or not.
352
355
"displayName": "A String", # A human-friendly name for the Uptime check configuration. The display name should be unique within a Cloud Monitoring Workspace in order to make it easier to identify; however, uniqueness is not enforced. Required.
353
356
"httpCheck": { # Information involved in an HTTP/HTTPS Uptime check request. # Contains information needed to make an HTTP or HTTPS check.
354
357
"acceptedResponseStatusCodes": [ # If present, the check will only pass if the HTTP response status code is in this set of status codes. If empty, the HTTP status code will only pass if the HTTP status code is 200-299.
@@ -464,6 +467,7 @@ <h3>Method Details</h3>
464
467
"matcher": "A String", # The type of content matcher that will be applied to the server output, compared to the content string when the check is run.
465
468
},
466
469
],
470
+
"disabled": True or False, # Whether the check is disabled or not.
467
471
"displayName": "A String", # A human-friendly name for the Uptime check configuration. The display name should be unique within a Cloud Monitoring Workspace in order to make it easier to identify; however, uniqueness is not enforced. Required.
468
472
"httpCheck": { # Information involved in an HTTP/HTTPS Uptime check request. # Contains information needed to make an HTTP or HTTPS check.
469
473
"acceptedResponseStatusCodes": [ # If present, the check will only pass if the HTTP response status code is in this set of status codes. If empty, the HTTP status code will only pass if the HTTP status code is 200-299.
@@ -583,6 +587,7 @@ <h3>Method Details</h3>
583
587
"matcher": "A String", # The type of content matcher that will be applied to the server output, compared to the content string when the check is run.
584
588
},
585
589
],
590
+
"disabled": True or False, # Whether the check is disabled or not.
586
591
"displayName": "A String", # A human-friendly name for the Uptime check configuration. The display name should be unique within a Cloud Monitoring Workspace in order to make it easier to identify; however, uniqueness is not enforced. Required.
587
592
"httpCheck": { # Information involved in an HTTP/HTTPS Uptime check request. # Contains information needed to make an HTTP or HTTPS check.
588
593
"acceptedResponseStatusCodes": [ # If present, the check will only pass if the HTTP response status code is in this set of status codes. If empty, the HTTP status code will only pass if the HTTP status code is 200-299.
@@ -685,6 +690,7 @@ <h3>Method Details</h3>
685
690
"matcher": "A String", # The type of content matcher that will be applied to the server output, compared to the content string when the check is run.
686
691
},
687
692
],
693
+
"disabled": True or False, # Whether the check is disabled or not.
688
694
"displayName": "A String", # A human-friendly name for the Uptime check configuration. The display name should be unique within a Cloud Monitoring Workspace in order to make it easier to identify; however, uniqueness is not enforced. Required.
689
695
"httpCheck": { # Information involved in an HTTP/HTTPS Uptime check request. # Contains information needed to make an HTTP or HTTPS check.
690
696
"acceptedResponseStatusCodes": [ # If present, the check will only pass if the HTTP response status code is in this set of status codes. If empty, the HTTP status code will only pass if the HTTP status code is 200-299.
"description": "Whether the check is disabled or not.",
6102
+
"type": "boolean"
6103
+
},
6100
6104
"displayName": {
6101
6105
"description": "A human-friendly name for the Uptime check configuration. The display name should be unique within a Cloud Monitoring Workspace in order to make it easier to identify; however, uniqueness is not enforced. Required.",
0 commit comments