MonitoringAppscodeComV1alpha1Api

June 20, 2018 ยท View on GitHub

All URIs are relative to https://localhost

MethodHTTP requestDescription
createNamespacedClusterAlertPOST /apis/monitoring.appscode.com/v1alpha1/namespaces/{namespace}/clusteralerts
createNamespacedIncidentPOST /apis/monitoring.appscode.com/v1alpha1/namespaces/{namespace}/incidents
createNamespacedNodeAlertPOST /apis/monitoring.appscode.com/v1alpha1/namespaces/{namespace}/nodealerts
createNamespacedPodAlertPOST /apis/monitoring.appscode.com/v1alpha1/namespaces/{namespace}/podalerts
createNamespacedSearchlightPluginPOST /apis/monitoring.appscode.com/v1alpha1/namespaces/{namespace}/searchlightplugins
deleteCollectionNamespacedClusterAlertDELETE /apis/monitoring.appscode.com/v1alpha1/namespaces/{namespace}/clusteralerts
deleteCollectionNamespacedIncidentDELETE /apis/monitoring.appscode.com/v1alpha1/namespaces/{namespace}/incidents
deleteCollectionNamespacedNodeAlertDELETE /apis/monitoring.appscode.com/v1alpha1/namespaces/{namespace}/nodealerts
deleteCollectionNamespacedPodAlertDELETE /apis/monitoring.appscode.com/v1alpha1/namespaces/{namespace}/podalerts
deleteCollectionNamespacedSearchlightPluginDELETE /apis/monitoring.appscode.com/v1alpha1/namespaces/{namespace}/searchlightplugins
deleteNamespacedClusterAlertDELETE /apis/monitoring.appscode.com/v1alpha1/namespaces/{namespace}/clusteralerts/{name}
deleteNamespacedIncidentDELETE /apis/monitoring.appscode.com/v1alpha1/namespaces/{namespace}/incidents/{name}
deleteNamespacedNodeAlertDELETE /apis/monitoring.appscode.com/v1alpha1/namespaces/{namespace}/nodealerts/{name}
deleteNamespacedPodAlertDELETE /apis/monitoring.appscode.com/v1alpha1/namespaces/{namespace}/podalerts/{name}
deleteNamespacedSearchlightPluginDELETE /apis/monitoring.appscode.com/v1alpha1/namespaces/{namespace}/searchlightplugins/{name}
getAPIResourcesGET /apis/monitoring.appscode.com/v1alpha1/
listClusterAlertForAllNamespacesGET /apis/monitoring.appscode.com/v1alpha1/clusteralerts
listIncidentForAllNamespacesGET /apis/monitoring.appscode.com/v1alpha1/incidents
listNamespacedClusterAlertGET /apis/monitoring.appscode.com/v1alpha1/namespaces/{namespace}/clusteralerts
listNamespacedIncidentGET /apis/monitoring.appscode.com/v1alpha1/namespaces/{namespace}/incidents
listNamespacedNodeAlertGET /apis/monitoring.appscode.com/v1alpha1/namespaces/{namespace}/nodealerts
listNamespacedPodAlertGET /apis/monitoring.appscode.com/v1alpha1/namespaces/{namespace}/podalerts
listNamespacedSearchlightPluginGET /apis/monitoring.appscode.com/v1alpha1/namespaces/{namespace}/searchlightplugins
listNodeAlertForAllNamespacesGET /apis/monitoring.appscode.com/v1alpha1/nodealerts
listPodAlertForAllNamespacesGET /apis/monitoring.appscode.com/v1alpha1/podalerts
listSearchlightPluginForAllNamespacesGET /apis/monitoring.appscode.com/v1alpha1/searchlightplugins
patchNamespacedClusterAlertPATCH /apis/monitoring.appscode.com/v1alpha1/namespaces/{namespace}/clusteralerts/{name}
patchNamespacedIncidentPATCH /apis/monitoring.appscode.com/v1alpha1/namespaces/{namespace}/incidents/{name}
patchNamespacedNodeAlertPATCH /apis/monitoring.appscode.com/v1alpha1/namespaces/{namespace}/nodealerts/{name}
patchNamespacedPodAlertPATCH /apis/monitoring.appscode.com/v1alpha1/namespaces/{namespace}/podalerts/{name}
patchNamespacedSearchlightPluginPATCH /apis/monitoring.appscode.com/v1alpha1/namespaces/{namespace}/searchlightplugins/{name}
readNamespacedClusterAlertGET /apis/monitoring.appscode.com/v1alpha1/namespaces/{namespace}/clusteralerts/{name}
readNamespacedIncidentGET /apis/monitoring.appscode.com/v1alpha1/namespaces/{namespace}/incidents/{name}
readNamespacedNodeAlertGET /apis/monitoring.appscode.com/v1alpha1/namespaces/{namespace}/nodealerts/{name}
readNamespacedPodAlertGET /apis/monitoring.appscode.com/v1alpha1/namespaces/{namespace}/podalerts/{name}
readNamespacedSearchlightPluginGET /apis/monitoring.appscode.com/v1alpha1/namespaces/{namespace}/searchlightplugins/{name}
replaceNamespacedClusterAlertPUT /apis/monitoring.appscode.com/v1alpha1/namespaces/{namespace}/clusteralerts/{name}
replaceNamespacedIncidentPUT /apis/monitoring.appscode.com/v1alpha1/namespaces/{namespace}/incidents/{name}
replaceNamespacedNodeAlertPUT /apis/monitoring.appscode.com/v1alpha1/namespaces/{namespace}/nodealerts/{name}
replaceNamespacedPodAlertPUT /apis/monitoring.appscode.com/v1alpha1/namespaces/{namespace}/podalerts/{name}
replaceNamespacedSearchlightPluginPUT /apis/monitoring.appscode.com/v1alpha1/namespaces/{namespace}/searchlightplugins/{name}

createNamespacedClusterAlert

V1alpha1ClusterAlert createNamespacedClusterAlert(namespace, body, pretty)

create a ClusterAlert

Example

// Import classes:
//import com.appscode.searchlight.client.ApiException;
//import com.appscode.searchlight.client.apis.MonitoringAppscodeComV1alpha1Api;


MonitoringAppscodeComV1alpha1Api apiInstance = new MonitoringAppscodeComV1alpha1Api();
String namespace = "namespace_example"; // String | object name and auth scope, such as for teams and projects
V1alpha1ClusterAlert body = new V1alpha1ClusterAlert(); // V1alpha1ClusterAlert | 
String pretty = "pretty_example"; // String | If 'true', then the output is pretty printed.
try {
    V1alpha1ClusterAlert result = apiInstance.createNamespacedClusterAlert(namespace, body, pretty);
    System.out.println(result);
} catch (ApiException e) {
    System.err.println("Exception when calling MonitoringAppscodeComV1alpha1Api#createNamespacedClusterAlert");
    e.printStackTrace();
}

Parameters

NameTypeDescriptionNotes
namespaceStringobject name and auth scope, such as for teams and projects
bodyV1alpha1ClusterAlert
prettyStringIf 'true', then the output is pretty printed.[optional]

Return type

V1alpha1ClusterAlert

Authorization

No authorization required

HTTP request headers

  • Content-Type: /
  • Accept: application/json, application/yaml, application/vnd.kubernetes.protobuf

createNamespacedIncident

V1alpha1Incident createNamespacedIncident(namespace, body, pretty)

create an Incident

Example

// Import classes:
//import com.appscode.searchlight.client.ApiException;
//import com.appscode.searchlight.client.apis.MonitoringAppscodeComV1alpha1Api;


MonitoringAppscodeComV1alpha1Api apiInstance = new MonitoringAppscodeComV1alpha1Api();
String namespace = "namespace_example"; // String | object name and auth scope, such as for teams and projects
V1alpha1Incident body = new V1alpha1Incident(); // V1alpha1Incident | 
String pretty = "pretty_example"; // String | If 'true', then the output is pretty printed.
try {
    V1alpha1Incident result = apiInstance.createNamespacedIncident(namespace, body, pretty);
    System.out.println(result);
} catch (ApiException e) {
    System.err.println("Exception when calling MonitoringAppscodeComV1alpha1Api#createNamespacedIncident");
    e.printStackTrace();
}

Parameters

NameTypeDescriptionNotes
namespaceStringobject name and auth scope, such as for teams and projects
bodyV1alpha1Incident
prettyStringIf 'true', then the output is pretty printed.[optional]

Return type

V1alpha1Incident

Authorization

No authorization required

HTTP request headers

  • Content-Type: /
  • Accept: application/json, application/yaml, application/vnd.kubernetes.protobuf

createNamespacedNodeAlert

V1alpha1NodeAlert createNamespacedNodeAlert(namespace, body, pretty)

create a NodeAlert

Example

// Import classes:
//import com.appscode.searchlight.client.ApiException;
//import com.appscode.searchlight.client.apis.MonitoringAppscodeComV1alpha1Api;


MonitoringAppscodeComV1alpha1Api apiInstance = new MonitoringAppscodeComV1alpha1Api();
String namespace = "namespace_example"; // String | object name and auth scope, such as for teams and projects
V1alpha1NodeAlert body = new V1alpha1NodeAlert(); // V1alpha1NodeAlert | 
String pretty = "pretty_example"; // String | If 'true', then the output is pretty printed.
try {
    V1alpha1NodeAlert result = apiInstance.createNamespacedNodeAlert(namespace, body, pretty);
    System.out.println(result);
} catch (ApiException e) {
    System.err.println("Exception when calling MonitoringAppscodeComV1alpha1Api#createNamespacedNodeAlert");
    e.printStackTrace();
}

Parameters

NameTypeDescriptionNotes
namespaceStringobject name and auth scope, such as for teams and projects
bodyV1alpha1NodeAlert
prettyStringIf 'true', then the output is pretty printed.[optional]

Return type

V1alpha1NodeAlert

Authorization

No authorization required

HTTP request headers

  • Content-Type: /
  • Accept: application/json, application/yaml, application/vnd.kubernetes.protobuf

createNamespacedPodAlert

V1alpha1PodAlert createNamespacedPodAlert(namespace, body, pretty)

create a PodAlert

Example

// Import classes:
//import com.appscode.searchlight.client.ApiException;
//import com.appscode.searchlight.client.apis.MonitoringAppscodeComV1alpha1Api;


MonitoringAppscodeComV1alpha1Api apiInstance = new MonitoringAppscodeComV1alpha1Api();
String namespace = "namespace_example"; // String | object name and auth scope, such as for teams and projects
V1alpha1PodAlert body = new V1alpha1PodAlert(); // V1alpha1PodAlert | 
String pretty = "pretty_example"; // String | If 'true', then the output is pretty printed.
try {
    V1alpha1PodAlert result = apiInstance.createNamespacedPodAlert(namespace, body, pretty);
    System.out.println(result);
} catch (ApiException e) {
    System.err.println("Exception when calling MonitoringAppscodeComV1alpha1Api#createNamespacedPodAlert");
    e.printStackTrace();
}

Parameters

NameTypeDescriptionNotes
namespaceStringobject name and auth scope, such as for teams and projects
bodyV1alpha1PodAlert
prettyStringIf 'true', then the output is pretty printed.[optional]

Return type

V1alpha1PodAlert

Authorization

No authorization required

HTTP request headers

  • Content-Type: /
  • Accept: application/json, application/yaml, application/vnd.kubernetes.protobuf

createNamespacedSearchlightPlugin

V1alpha1SearchlightPlugin createNamespacedSearchlightPlugin(namespace, body, pretty)

create a SearchlightPlugin

Example

// Import classes:
//import com.appscode.searchlight.client.ApiException;
//import com.appscode.searchlight.client.apis.MonitoringAppscodeComV1alpha1Api;


MonitoringAppscodeComV1alpha1Api apiInstance = new MonitoringAppscodeComV1alpha1Api();
String namespace = "namespace_example"; // String | object name and auth scope, such as for teams and projects
V1alpha1SearchlightPlugin body = new V1alpha1SearchlightPlugin(); // V1alpha1SearchlightPlugin | 
String pretty = "pretty_example"; // String | If 'true', then the output is pretty printed.
try {
    V1alpha1SearchlightPlugin result = apiInstance.createNamespacedSearchlightPlugin(namespace, body, pretty);
    System.out.println(result);
} catch (ApiException e) {
    System.err.println("Exception when calling MonitoringAppscodeComV1alpha1Api#createNamespacedSearchlightPlugin");
    e.printStackTrace();
}

Parameters

NameTypeDescriptionNotes
namespaceStringobject name and auth scope, such as for teams and projects
bodyV1alpha1SearchlightPlugin
prettyStringIf 'true', then the output is pretty printed.[optional]

Return type

V1alpha1SearchlightPlugin

Authorization

No authorization required

HTTP request headers

  • Content-Type: /
  • Accept: application/json, application/yaml, application/vnd.kubernetes.protobuf

deleteCollectionNamespacedClusterAlert

V1Status deleteCollectionNamespacedClusterAlert(namespace, pretty, _continue, fieldSelector, includeUninitialized, labelSelector, limit, resourceVersion, timeoutSeconds, watch)

delete collection of ClusterAlert

Example

// Import classes:
//import com.appscode.searchlight.client.ApiException;
//import com.appscode.searchlight.client.apis.MonitoringAppscodeComV1alpha1Api;


MonitoringAppscodeComV1alpha1Api apiInstance = new MonitoringAppscodeComV1alpha1Api();
String namespace = "namespace_example"; // String | object name and auth scope, such as for teams and projects
String pretty = "pretty_example"; // String | If 'true', then the output is pretty printed.
String _continue = "_continue_example"; // String | The continue option should be set when retrieving more results from the server. Since this value is server defined, clients may only use the continue value from a previous query result with identical query parameters (except for the value of continue) and the server may reject a continue value it does not recognize. If the specified continue value is no longer valid whether due to expiration (generally five to fifteen minutes) or a configuration change on the server the server will respond with a 410 ResourceExpired error indicating the client must restart their list without the continue field. This field is not supported when watch is true. Clients may start a watch from the last resourceVersion value returned by the server and not miss any modifications.
String fieldSelector = "fieldSelector_example"; // String | A selector to restrict the list of returned objects by their fields. Defaults to everything.
Boolean includeUninitialized = true; // Boolean | If true, partially initialized resources are included in the response.
String labelSelector = "labelSelector_example"; // String | A selector to restrict the list of returned objects by their labels. Defaults to everything.
Integer limit = 56; // Integer | limit is a maximum number of responses to return for a list call. If more items exist, the server will set the `continue` field on the list metadata to a value that can be used with the same initial query to retrieve the next set of results. Setting a limit may return fewer than the requested amount of items (up to zero items) in the event all requested objects are filtered out and clients should only use the presence of the continue field to determine whether more results are available. Servers may choose not to support the limit argument and will return all of the available results. If limit is specified and the continue field is empty, clients may assume that no more results are available. This field is not supported if watch is true.  The server guarantees that the objects returned when using continue will be identical to issuing a single list call without a limit - that is, no objects created, modified, or deleted after the first request is issued will be included in any subsequent continued requests. This is sometimes referred to as a consistent snapshot, and ensures that a client that is using limit to receive smaller chunks of a very large result can ensure they see all possible objects. If objects are updated during a chunked list the version of the object that was present at the time the first list result was calculated is returned.
String resourceVersion = "resourceVersion_example"; // String | When specified with a watch call, shows changes that occur after that particular version of a resource. Defaults to changes from the beginning of history. When specified for list: - if unset, then the result is returned from remote storage based on quorum-read flag; - if it's 0, then we simply return what we currently have in cache, no guarantee; - if set to non zero, then the result is at least as fresh as given rv.
Integer timeoutSeconds = 56; // Integer | Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.
Boolean watch = true; // Boolean | Watch for changes to the described resources and return them as a stream of add, update, and remove notifications. Specify resourceVersion.
try {
    V1Status result = apiInstance.deleteCollectionNamespacedClusterAlert(namespace, pretty, _continue, fieldSelector, includeUninitialized, labelSelector, limit, resourceVersion, timeoutSeconds, watch);
    System.out.println(result);
} catch (ApiException e) {
    System.err.println("Exception when calling MonitoringAppscodeComV1alpha1Api#deleteCollectionNamespacedClusterAlert");
    e.printStackTrace();
}

Parameters

NameTypeDescriptionNotes
namespaceStringobject name and auth scope, such as for teams and projects
prettyStringIf 'true', then the output is pretty printed.[optional]
_continueStringThe continue option should be set when retrieving more results from the server. Since this value is server defined, clients may only use the continue value from a previous query result with identical query parameters (except for the value of continue) and the server may reject a continue value it does not recognize. If the specified continue value is no longer valid whether due to expiration (generally five to fifteen minutes) or a configuration change on the server the server will respond with a 410 ResourceExpired error indicating the client must restart their list without the continue field. This field is not supported when watch is true. Clients may start a watch from the last resourceVersion value returned by the server and not miss any modifications.[optional]
fieldSelectorStringA selector to restrict the list of returned objects by their fields. Defaults to everything.[optional]
includeUninitializedBooleanIf true, partially initialized resources are included in the response.[optional]
labelSelectorStringA selector to restrict the list of returned objects by their labels. Defaults to everything.[optional]
limitIntegerlimit is a maximum number of responses to return for a list call. If more items exist, the server will set the `continue` field on the list metadata to a value that can be used with the same initial query to retrieve the next set of results. Setting a limit may return fewer than the requested amount of items (up to zero items) in the event all requested objects are filtered out and clients should only use the presence of the continue field to determine whether more results are available. Servers may choose not to support the limit argument and will return all of the available results. If limit is specified and the continue field is empty, clients may assume that no more results are available. This field is not supported if watch is true. The server guarantees that the objects returned when using continue will be identical to issuing a single list call without a limit - that is, no objects created, modified, or deleted after the first request is issued will be included in any subsequent continued requests. This is sometimes referred to as a consistent snapshot, and ensures that a client that is using limit to receive smaller chunks of a very large result can ensure they see all possible objects. If objects are updated during a chunked list the version of the object that was present at the time the first list result was calculated is returned.[optional]
resourceVersionStringWhen specified with a watch call, shows changes that occur after that particular version of a resource. Defaults to changes from the beginning of history. When specified for list: - if unset, then the result is returned from remote storage based on quorum-read flag; - if it's 0, then we simply return what we currently have in cache, no guarantee; - if set to non zero, then the result is at least as fresh as given rv.[optional]
timeoutSecondsIntegerTimeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.[optional]
watchBooleanWatch for changes to the described resources and return them as a stream of add, update, and remove notifications. Specify resourceVersion.[optional]

Return type

V1Status

Authorization

No authorization required

HTTP request headers

  • Content-Type: /
  • Accept: application/json, application/yaml, application/vnd.kubernetes.protobuf

deleteCollectionNamespacedIncident

V1Status deleteCollectionNamespacedIncident(namespace, pretty, _continue, fieldSelector, includeUninitialized, labelSelector, limit, resourceVersion, timeoutSeconds, watch)

delete collection of Incident

Example

// Import classes:
//import com.appscode.searchlight.client.ApiException;
//import com.appscode.searchlight.client.apis.MonitoringAppscodeComV1alpha1Api;


MonitoringAppscodeComV1alpha1Api apiInstance = new MonitoringAppscodeComV1alpha1Api();
String namespace = "namespace_example"; // String | object name and auth scope, such as for teams and projects
String pretty = "pretty_example"; // String | If 'true', then the output is pretty printed.
String _continue = "_continue_example"; // String | The continue option should be set when retrieving more results from the server. Since this value is server defined, clients may only use the continue value from a previous query result with identical query parameters (except for the value of continue) and the server may reject a continue value it does not recognize. If the specified continue value is no longer valid whether due to expiration (generally five to fifteen minutes) or a configuration change on the server the server will respond with a 410 ResourceExpired error indicating the client must restart their list without the continue field. This field is not supported when watch is true. Clients may start a watch from the last resourceVersion value returned by the server and not miss any modifications.
String fieldSelector = "fieldSelector_example"; // String | A selector to restrict the list of returned objects by their fields. Defaults to everything.
Boolean includeUninitialized = true; // Boolean | If true, partially initialized resources are included in the response.
String labelSelector = "labelSelector_example"; // String | A selector to restrict the list of returned objects by their labels. Defaults to everything.
Integer limit = 56; // Integer | limit is a maximum number of responses to return for a list call. If more items exist, the server will set the `continue` field on the list metadata to a value that can be used with the same initial query to retrieve the next set of results. Setting a limit may return fewer than the requested amount of items (up to zero items) in the event all requested objects are filtered out and clients should only use the presence of the continue field to determine whether more results are available. Servers may choose not to support the limit argument and will return all of the available results. If limit is specified and the continue field is empty, clients may assume that no more results are available. This field is not supported if watch is true.  The server guarantees that the objects returned when using continue will be identical to issuing a single list call without a limit - that is, no objects created, modified, or deleted after the first request is issued will be included in any subsequent continued requests. This is sometimes referred to as a consistent snapshot, and ensures that a client that is using limit to receive smaller chunks of a very large result can ensure they see all possible objects. If objects are updated during a chunked list the version of the object that was present at the time the first list result was calculated is returned.
String resourceVersion = "resourceVersion_example"; // String | When specified with a watch call, shows changes that occur after that particular version of a resource. Defaults to changes from the beginning of history. When specified for list: - if unset, then the result is returned from remote storage based on quorum-read flag; - if it's 0, then we simply return what we currently have in cache, no guarantee; - if set to non zero, then the result is at least as fresh as given rv.
Integer timeoutSeconds = 56; // Integer | Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.
Boolean watch = true; // Boolean | Watch for changes to the described resources and return them as a stream of add, update, and remove notifications. Specify resourceVersion.
try {
    V1Status result = apiInstance.deleteCollectionNamespacedIncident(namespace, pretty, _continue, fieldSelector, includeUninitialized, labelSelector, limit, resourceVersion, timeoutSeconds, watch);
    System.out.println(result);
} catch (ApiException e) {
    System.err.println("Exception when calling MonitoringAppscodeComV1alpha1Api#deleteCollectionNamespacedIncident");
    e.printStackTrace();
}

Parameters

NameTypeDescriptionNotes
namespaceStringobject name and auth scope, such as for teams and projects
prettyStringIf 'true', then the output is pretty printed.[optional]
_continueStringThe continue option should be set when retrieving more results from the server. Since this value is server defined, clients may only use the continue value from a previous query result with identical query parameters (except for the value of continue) and the server may reject a continue value it does not recognize. If the specified continue value is no longer valid whether due to expiration (generally five to fifteen minutes) or a configuration change on the server the server will respond with a 410 ResourceExpired error indicating the client must restart their list without the continue field. This field is not supported when watch is true. Clients may start a watch from the last resourceVersion value returned by the server and not miss any modifications.[optional]
fieldSelectorStringA selector to restrict the list of returned objects by their fields. Defaults to everything.[optional]
includeUninitializedBooleanIf true, partially initialized resources are included in the response.[optional]
labelSelectorStringA selector to restrict the list of returned objects by their labels. Defaults to everything.[optional]
limitIntegerlimit is a maximum number of responses to return for a list call. If more items exist, the server will set the `continue` field on the list metadata to a value that can be used with the same initial query to retrieve the next set of results. Setting a limit may return fewer than the requested amount of items (up to zero items) in the event all requested objects are filtered out and clients should only use the presence of the continue field to determine whether more results are available. Servers may choose not to support the limit argument and will return all of the available results. If limit is specified and the continue field is empty, clients may assume that no more results are available. This field is not supported if watch is true. The server guarantees that the objects returned when using continue will be identical to issuing a single list call without a limit - that is, no objects created, modified, or deleted after the first request is issued will be included in any subsequent continued requests. This is sometimes referred to as a consistent snapshot, and ensures that a client that is using limit to receive smaller chunks of a very large result can ensure they see all possible objects. If objects are updated during a chunked list the version of the object that was present at the time the first list result was calculated is returned.[optional]
resourceVersionStringWhen specified with a watch call, shows changes that occur after that particular version of a resource. Defaults to changes from the beginning of history. When specified for list: - if unset, then the result is returned from remote storage based on quorum-read flag; - if it's 0, then we simply return what we currently have in cache, no guarantee; - if set to non zero, then the result is at least as fresh as given rv.[optional]
timeoutSecondsIntegerTimeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.[optional]
watchBooleanWatch for changes to the described resources and return them as a stream of add, update, and remove notifications. Specify resourceVersion.[optional]

Return type

V1Status

Authorization

No authorization required

HTTP request headers

  • Content-Type: /
  • Accept: application/json, application/yaml, application/vnd.kubernetes.protobuf

deleteCollectionNamespacedNodeAlert

V1Status deleteCollectionNamespacedNodeAlert(namespace, pretty, _continue, fieldSelector, includeUninitialized, labelSelector, limit, resourceVersion, timeoutSeconds, watch)

delete collection of NodeAlert

Example

// Import classes:
//import com.appscode.searchlight.client.ApiException;
//import com.appscode.searchlight.client.apis.MonitoringAppscodeComV1alpha1Api;


MonitoringAppscodeComV1alpha1Api apiInstance = new MonitoringAppscodeComV1alpha1Api();
String namespace = "namespace_example"; // String | object name and auth scope, such as for teams and projects
String pretty = "pretty_example"; // String | If 'true', then the output is pretty printed.
String _continue = "_continue_example"; // String | The continue option should be set when retrieving more results from the server. Since this value is server defined, clients may only use the continue value from a previous query result with identical query parameters (except for the value of continue) and the server may reject a continue value it does not recognize. If the specified continue value is no longer valid whether due to expiration (generally five to fifteen minutes) or a configuration change on the server the server will respond with a 410 ResourceExpired error indicating the client must restart their list without the continue field. This field is not supported when watch is true. Clients may start a watch from the last resourceVersion value returned by the server and not miss any modifications.
String fieldSelector = "fieldSelector_example"; // String | A selector to restrict the list of returned objects by their fields. Defaults to everything.
Boolean includeUninitialized = true; // Boolean | If true, partially initialized resources are included in the response.
String labelSelector = "labelSelector_example"; // String | A selector to restrict the list of returned objects by their labels. Defaults to everything.
Integer limit = 56; // Integer | limit is a maximum number of responses to return for a list call. If more items exist, the server will set the `continue` field on the list metadata to a value that can be used with the same initial query to retrieve the next set of results. Setting a limit may return fewer than the requested amount of items (up to zero items) in the event all requested objects are filtered out and clients should only use the presence of the continue field to determine whether more results are available. Servers may choose not to support the limit argument and will return all of the available results. If limit is specified and the continue field is empty, clients may assume that no more results are available. This field is not supported if watch is true.  The server guarantees that the objects returned when using continue will be identical to issuing a single list call without a limit - that is, no objects created, modified, or deleted after the first request is issued will be included in any subsequent continued requests. This is sometimes referred to as a consistent snapshot, and ensures that a client that is using limit to receive smaller chunks of a very large result can ensure they see all possible objects. If objects are updated during a chunked list the version of the object that was present at the time the first list result was calculated is returned.
String resourceVersion = "resourceVersion_example"; // String | When specified with a watch call, shows changes that occur after that particular version of a resource. Defaults to changes from the beginning of history. When specified for list: - if unset, then the result is returned from remote storage based on quorum-read flag; - if it's 0, then we simply return what we currently have in cache, no guarantee; - if set to non zero, then the result is at least as fresh as given rv.
Integer timeoutSeconds = 56; // Integer | Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.
Boolean watch = true; // Boolean | Watch for changes to the described resources and return them as a stream of add, update, and remove notifications. Specify resourceVersion.
try {
    V1Status result = apiInstance.deleteCollectionNamespacedNodeAlert(namespace, pretty, _continue, fieldSelector, includeUninitialized, labelSelector, limit, resourceVersion, timeoutSeconds, watch);
    System.out.println(result);
} catch (ApiException e) {
    System.err.println("Exception when calling MonitoringAppscodeComV1alpha1Api#deleteCollectionNamespacedNodeAlert");
    e.printStackTrace();
}

Parameters

NameTypeDescriptionNotes
namespaceStringobject name and auth scope, such as for teams and projects
prettyStringIf 'true', then the output is pretty printed.[optional]
_continueStringThe continue option should be set when retrieving more results from the server. Since this value is server defined, clients may only use the continue value from a previous query result with identical query parameters (except for the value of continue) and the server may reject a continue value it does not recognize. If the specified continue value is no longer valid whether due to expiration (generally five to fifteen minutes) or a configuration change on the server the server will respond with a 410 ResourceExpired error indicating the client must restart their list without the continue field. This field is not supported when watch is true. Clients may start a watch from the last resourceVersion value returned by the server and not miss any modifications.[optional]
fieldSelectorStringA selector to restrict the list of returned objects by their fields. Defaults to everything.[optional]
includeUninitializedBooleanIf true, partially initialized resources are included in the response.[optional]
labelSelectorStringA selector to restrict the list of returned objects by their labels. Defaults to everything.[optional]
limitIntegerlimit is a maximum number of responses to return for a list call. If more items exist, the server will set the `continue` field on the list metadata to a value that can be used with the same initial query to retrieve the next set of results. Setting a limit may return fewer than the requested amount of items (up to zero items) in the event all requested objects are filtered out and clients should only use the presence of the continue field to determine whether more results are available. Servers may choose not to support the limit argument and will return all of the available results. If limit is specified and the continue field is empty, clients may assume that no more results are available. This field is not supported if watch is true. The server guarantees that the objects returned when using continue will be identical to issuing a single list call without a limit - that is, no objects created, modified, or deleted after the first request is issued will be included in any subsequent continued requests. This is sometimes referred to as a consistent snapshot, and ensures that a client that is using limit to receive smaller chunks of a very large result can ensure they see all possible objects. If objects are updated during a chunked list the version of the object that was present at the time the first list result was calculated is returned.[optional]
resourceVersionStringWhen specified with a watch call, shows changes that occur after that particular version of a resource. Defaults to changes from the beginning of history. When specified for list: - if unset, then the result is returned from remote storage based on quorum-read flag; - if it's 0, then we simply return what we currently have in cache, no guarantee; - if set to non zero, then the result is at least as fresh as given rv.[optional]
timeoutSecondsIntegerTimeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.[optional]
watchBooleanWatch for changes to the described resources and return them as a stream of add, update, and remove notifications. Specify resourceVersion.[optional]

Return type

V1Status

Authorization

No authorization required

HTTP request headers

  • Content-Type: /
  • Accept: application/json, application/yaml, application/vnd.kubernetes.protobuf

deleteCollectionNamespacedPodAlert

V1Status deleteCollectionNamespacedPodAlert(namespace, pretty, _continue, fieldSelector, includeUninitialized, labelSelector, limit, resourceVersion, timeoutSeconds, watch)

delete collection of PodAlert

Example

// Import classes:
//import com.appscode.searchlight.client.ApiException;
//import com.appscode.searchlight.client.apis.MonitoringAppscodeComV1alpha1Api;


MonitoringAppscodeComV1alpha1Api apiInstance = new MonitoringAppscodeComV1alpha1Api();
String namespace = "namespace_example"; // String | object name and auth scope, such as for teams and projects
String pretty = "pretty_example"; // String | If 'true', then the output is pretty printed.
String _continue = "_continue_example"; // String | The continue option should be set when retrieving more results from the server. Since this value is server defined, clients may only use the continue value from a previous query result with identical query parameters (except for the value of continue) and the server may reject a continue value it does not recognize. If the specified continue value is no longer valid whether due to expiration (generally five to fifteen minutes) or a configuration change on the server the server will respond with a 410 ResourceExpired error indicating the client must restart their list without the continue field. This field is not supported when watch is true. Clients may start a watch from the last resourceVersion value returned by the server and not miss any modifications.
String fieldSelector = "fieldSelector_example"; // String | A selector to restrict the list of returned objects by their fields. Defaults to everything.
Boolean includeUninitialized = true; // Boolean | If true, partially initialized resources are included in the response.
String labelSelector = "labelSelector_example"; // String | A selector to restrict the list of returned objects by their labels. Defaults to everything.
Integer limit = 56; // Integer | limit is a maximum number of responses to return for a list call. If more items exist, the server will set the `continue` field on the list metadata to a value that can be used with the same initial query to retrieve the next set of results. Setting a limit may return fewer than the requested amount of items (up to zero items) in the event all requested objects are filtered out and clients should only use the presence of the continue field to determine whether more results are available. Servers may choose not to support the limit argument and will return all of the available results. If limit is specified and the continue field is empty, clients may assume that no more results are available. This field is not supported if watch is true.  The server guarantees that the objects returned when using continue will be identical to issuing a single list call without a limit - that is, no objects created, modified, or deleted after the first request is issued will be included in any subsequent continued requests. This is sometimes referred to as a consistent snapshot, and ensures that a client that is using limit to receive smaller chunks of a very large result can ensure they see all possible objects. If objects are updated during a chunked list the version of the object that was present at the time the first list result was calculated is returned.
String resourceVersion = "resourceVersion_example"; // String | When specified with a watch call, shows changes that occur after that particular version of a resource. Defaults to changes from the beginning of history. When specified for list: - if unset, then the result is returned from remote storage based on quorum-read flag; - if it's 0, then we simply return what we currently have in cache, no guarantee; - if set to non zero, then the result is at least as fresh as given rv.
Integer timeoutSeconds = 56; // Integer | Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.
Boolean watch = true; // Boolean | Watch for changes to the described resources and return them as a stream of add, update, and remove notifications. Specify resourceVersion.
try {
    V1Status result = apiInstance.deleteCollectionNamespacedPodAlert(namespace, pretty, _continue, fieldSelector, includeUninitialized, labelSelector, limit, resourceVersion, timeoutSeconds, watch);
    System.out.println(result);
} catch (ApiException e) {
    System.err.println("Exception when calling MonitoringAppscodeComV1alpha1Api#deleteCollectionNamespacedPodAlert");
    e.printStackTrace();
}

Parameters

NameTypeDescriptionNotes
namespaceStringobject name and auth scope, such as for teams and projects
prettyStringIf 'true', then the output is pretty printed.[optional]
_continueStringThe continue option should be set when retrieving more results from the server. Since this value is server defined, clients may only use the continue value from a previous query result with identical query parameters (except for the value of continue) and the server may reject a continue value it does not recognize. If the specified continue value is no longer valid whether due to expiration (generally five to fifteen minutes) or a configuration change on the server the server will respond with a 410 ResourceExpired error indicating the client must restart their list without the continue field. This field is not supported when watch is true. Clients may start a watch from the last resourceVersion value returned by the server and not miss any modifications.[optional]
fieldSelectorStringA selector to restrict the list of returned objects by their fields. Defaults to everything.[optional]
includeUninitializedBooleanIf true, partially initialized resources are included in the response.[optional]
labelSelectorStringA selector to restrict the list of returned objects by their labels. Defaults to everything.[optional]
limitIntegerlimit is a maximum number of responses to return for a list call. If more items exist, the server will set the `continue` field on the list metadata to a value that can be used with the same initial query to retrieve the next set of results. Setting a limit may return fewer than the requested amount of items (up to zero items) in the event all requested objects are filtered out and clients should only use the presence of the continue field to determine whether more results are available. Servers may choose not to support the limit argument and will return all of the available results. If limit is specified and the continue field is empty, clients may assume that no more results are available. This field is not supported if watch is true. The server guarantees that the objects returned when using continue will be identical to issuing a single list call without a limit - that is, no objects created, modified, or deleted after the first request is issued will be included in any subsequent continued requests. This is sometimes referred to as a consistent snapshot, and ensures that a client that is using limit to receive smaller chunks of a very large result can ensure they see all possible objects. If objects are updated during a chunked list the version of the object that was present at the time the first list result was calculated is returned.[optional]
resourceVersionStringWhen specified with a watch call, shows changes that occur after that particular version of a resource. Defaults to changes from the beginning of history. When specified for list: - if unset, then the result is returned from remote storage based on quorum-read flag; - if it's 0, then we simply return what we currently have in cache, no guarantee; - if set to non zero, then the result is at least as fresh as given rv.[optional]
timeoutSecondsIntegerTimeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.[optional]
watchBooleanWatch for changes to the described resources and return them as a stream of add, update, and remove notifications. Specify resourceVersion.[optional]

Return type

V1Status

Authorization

No authorization required

HTTP request headers

  • Content-Type: /
  • Accept: application/json, application/yaml, application/vnd.kubernetes.protobuf

deleteCollectionNamespacedSearchlightPlugin

V1Status deleteCollectionNamespacedSearchlightPlugin(namespace, pretty, _continue, fieldSelector, includeUninitialized, labelSelector, limit, resourceVersion, timeoutSeconds, watch)

delete collection of SearchlightPlugin

Example

// Import classes:
//import com.appscode.searchlight.client.ApiException;
//import com.appscode.searchlight.client.apis.MonitoringAppscodeComV1alpha1Api;


MonitoringAppscodeComV1alpha1Api apiInstance = new MonitoringAppscodeComV1alpha1Api();
String namespace = "namespace_example"; // String | object name and auth scope, such as for teams and projects
String pretty = "pretty_example"; // String | If 'true', then the output is pretty printed.
String _continue = "_continue_example"; // String | The continue option should be set when retrieving more results from the server. Since this value is server defined, clients may only use the continue value from a previous query result with identical query parameters (except for the value of continue) and the server may reject a continue value it does not recognize. If the specified continue value is no longer valid whether due to expiration (generally five to fifteen minutes) or a configuration change on the server the server will respond with a 410 ResourceExpired error indicating the client must restart their list without the continue field. This field is not supported when watch is true. Clients may start a watch from the last resourceVersion value returned by the server and not miss any modifications.
String fieldSelector = "fieldSelector_example"; // String | A selector to restrict the list of returned objects by their fields. Defaults to everything.
Boolean includeUninitialized = true; // Boolean | If true, partially initialized resources are included in the response.
String labelSelector = "labelSelector_example"; // String | A selector to restrict the list of returned objects by their labels. Defaults to everything.
Integer limit = 56; // Integer | limit is a maximum number of responses to return for a list call. If more items exist, the server will set the `continue` field on the list metadata to a value that can be used with the same initial query to retrieve the next set of results. Setting a limit may return fewer than the requested amount of items (up to zero items) in the event all requested objects are filtered out and clients should only use the presence of the continue field to determine whether more results are available. Servers may choose not to support the limit argument and will return all of the available results. If limit is specified and the continue field is empty, clients may assume that no more results are available. This field is not supported if watch is true.  The server guarantees that the objects returned when using continue will be identical to issuing a single list call without a limit - that is, no objects created, modified, or deleted after the first request is issued will be included in any subsequent continued requests. This is sometimes referred to as a consistent snapshot, and ensures that a client that is using limit to receive smaller chunks of a very large result can ensure they see all possible objects. If objects are updated during a chunked list the version of the object that was present at the time the first list result was calculated is returned.
String resourceVersion = "resourceVersion_example"; // String | When specified with a watch call, shows changes that occur after that particular version of a resource. Defaults to changes from the beginning of history. When specified for list: - if unset, then the result is returned from remote storage based on quorum-read flag; - if it's 0, then we simply return what we currently have in cache, no guarantee; - if set to non zero, then the result is at least as fresh as given rv.
Integer timeoutSeconds = 56; // Integer | Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.
Boolean watch = true; // Boolean | Watch for changes to the described resources and return them as a stream of add, update, and remove notifications. Specify resourceVersion.
try {
    V1Status result = apiInstance.deleteCollectionNamespacedSearchlightPlugin(namespace, pretty, _continue, fieldSelector, includeUninitialized, labelSelector, limit, resourceVersion, timeoutSeconds, watch);
    System.out.println(result);
} catch (ApiException e) {
    System.err.println("Exception when calling MonitoringAppscodeComV1alpha1Api#deleteCollectionNamespacedSearchlightPlugin");
    e.printStackTrace();
}

Parameters

NameTypeDescriptionNotes
namespaceStringobject name and auth scope, such as for teams and projects
prettyStringIf 'true', then the output is pretty printed.[optional]
_continueStringThe continue option should be set when retrieving more results from the server. Since this value is server defined, clients may only use the continue value from a previous query result with identical query parameters (except for the value of continue) and the server may reject a continue value it does not recognize. If the specified continue value is no longer valid whether due to expiration (generally five to fifteen minutes) or a configuration change on the server the server will respond with a 410 ResourceExpired error indicating the client must restart their list without the continue field. This field is not supported when watch is true. Clients may start a watch from the last resourceVersion value returned by the server and not miss any modifications.[optional]
fieldSelectorStringA selector to restrict the list of returned objects by their fields. Defaults to everything.[optional]
includeUninitializedBooleanIf true, partially initialized resources are included in the response.[optional]
labelSelectorStringA selector to restrict the list of returned objects by their labels. Defaults to everything.[optional]
limitIntegerlimit is a maximum number of responses to return for a list call. If more items exist, the server will set the `continue` field on the list metadata to a value that can be used with the same initial query to retrieve the next set of results. Setting a limit may return fewer than the requested amount of items (up to zero items) in the event all requested objects are filtered out and clients should only use the presence of the continue field to determine whether more results are available. Servers may choose not to support the limit argument and will return all of the available results. If limit is specified and the continue field is empty, clients may assume that no more results are available. This field is not supported if watch is true. The server guarantees that the objects returned when using continue will be identical to issuing a single list call without a limit - that is, no objects created, modified, or deleted after the first request is issued will be included in any subsequent continued requests. This is sometimes referred to as a consistent snapshot, and ensures that a client that is using limit to receive smaller chunks of a very large result can ensure they see all possible objects. If objects are updated during a chunked list the version of the object that was present at the time the first list result was calculated is returned.[optional]
resourceVersionStringWhen specified with a watch call, shows changes that occur after that particular version of a resource. Defaults to changes from the beginning of history. When specified for list: - if unset, then the result is returned from remote storage based on quorum-read flag; - if it's 0, then we simply return what we currently have in cache, no guarantee; - if set to non zero, then the result is at least as fresh as given rv.[optional]
timeoutSecondsIntegerTimeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.[optional]
watchBooleanWatch for changes to the described resources and return them as a stream of add, update, and remove notifications. Specify resourceVersion.[optional]

Return type

V1Status

Authorization

No authorization required

HTTP request headers

  • Content-Type: /
  • Accept: application/json, application/yaml, application/vnd.kubernetes.protobuf

deleteNamespacedClusterAlert

V1Status deleteNamespacedClusterAlert(name, namespace, body, pretty, gracePeriodSeconds, orphanDependents, propagationPolicy)

delete a ClusterAlert

Example

// Import classes:
//import com.appscode.searchlight.client.ApiException;
//import com.appscode.searchlight.client.apis.MonitoringAppscodeComV1alpha1Api;


MonitoringAppscodeComV1alpha1Api apiInstance = new MonitoringAppscodeComV1alpha1Api();
String name = "name_example"; // String | name of the ClusterAlert
String namespace = "namespace_example"; // String | object name and auth scope, such as for teams and projects
V1DeleteOptions body = new V1DeleteOptions(); // V1DeleteOptions | 
String pretty = "pretty_example"; // String | If 'true', then the output is pretty printed.
Integer gracePeriodSeconds = 56; // Integer | The duration in seconds before the object should be deleted. Value must be non-negative integer. The value zero indicates delete immediately. If this value is nil, the default grace period for the specified type will be used. Defaults to a per object value if not specified. zero means delete immediately.
Boolean orphanDependents = true; // Boolean | Deprecated: please use the PropagationPolicy, this field will be deprecated in 1.7. Should the dependent objects be orphaned. If true/false, the \"orphan\" finalizer will be added to/removed from the object's finalizers list. Either this field or PropagationPolicy may be set, but not both.
String propagationPolicy = "propagationPolicy_example"; // String | Whether and how garbage collection will be performed. Either this field or OrphanDependents may be set, but not both. The default policy is decided by the existing finalizer set in the metadata.finalizers and the resource-specific default policy. Acceptable values are: 'Orphan' - orphan the dependents; 'Background' - allow the garbage collector to delete the dependents in the background; 'Foreground' - a cascading policy that deletes all dependents in the foreground.
try {
    V1Status result = apiInstance.deleteNamespacedClusterAlert(name, namespace, body, pretty, gracePeriodSeconds, orphanDependents, propagationPolicy);
    System.out.println(result);
} catch (ApiException e) {
    System.err.println("Exception when calling MonitoringAppscodeComV1alpha1Api#deleteNamespacedClusterAlert");
    e.printStackTrace();
}

Parameters

NameTypeDescriptionNotes
nameStringname of the ClusterAlert
namespaceStringobject name and auth scope, such as for teams and projects
bodyV1DeleteOptions
prettyStringIf 'true', then the output is pretty printed.[optional]
gracePeriodSecondsIntegerThe duration in seconds before the object should be deleted. Value must be non-negative integer. The value zero indicates delete immediately. If this value is nil, the default grace period for the specified type will be used. Defaults to a per object value if not specified. zero means delete immediately.[optional]
orphanDependentsBooleanDeprecated: please use the PropagationPolicy, this field will be deprecated in 1.7. Should the dependent objects be orphaned. If true/false, the "orphan" finalizer will be added to/removed from the object's finalizers list. Either this field or PropagationPolicy may be set, but not both.[optional]
propagationPolicyStringWhether and how garbage collection will be performed. Either this field or OrphanDependents may be set, but not both. The default policy is decided by the existing finalizer set in the metadata.finalizers and the resource-specific default policy. Acceptable values are: 'Orphan' - orphan the dependents; 'Background' - allow the garbage collector to delete the dependents in the background; 'Foreground' - a cascading policy that deletes all dependents in the foreground.[optional]

Return type

V1Status

Authorization

No authorization required

HTTP request headers

  • Content-Type: /
  • Accept: application/json, application/yaml, application/vnd.kubernetes.protobuf

deleteNamespacedIncident

V1Status deleteNamespacedIncident(name, namespace, body, pretty, gracePeriodSeconds, orphanDependents, propagationPolicy)

delete an Incident

Example

// Import classes:
//import com.appscode.searchlight.client.ApiException;
//import com.appscode.searchlight.client.apis.MonitoringAppscodeComV1alpha1Api;


MonitoringAppscodeComV1alpha1Api apiInstance = new MonitoringAppscodeComV1alpha1Api();
String name = "name_example"; // String | name of the Incident
String namespace = "namespace_example"; // String | object name and auth scope, such as for teams and projects
V1DeleteOptions body = new V1DeleteOptions(); // V1DeleteOptions | 
String pretty = "pretty_example"; // String | If 'true', then the output is pretty printed.
Integer gracePeriodSeconds = 56; // Integer | The duration in seconds before the object should be deleted. Value must be non-negative integer. The value zero indicates delete immediately. If this value is nil, the default grace period for the specified type will be used. Defaults to a per object value if not specified. zero means delete immediately.
Boolean orphanDependents = true; // Boolean | Deprecated: please use the PropagationPolicy, this field will be deprecated in 1.7. Should the dependent objects be orphaned. If true/false, the \"orphan\" finalizer will be added to/removed from the object's finalizers list. Either this field or PropagationPolicy may be set, but not both.
String propagationPolicy = "propagationPolicy_example"; // String | Whether and how garbage collection will be performed. Either this field or OrphanDependents may be set, but not both. The default policy is decided by the existing finalizer set in the metadata.finalizers and the resource-specific default policy. Acceptable values are: 'Orphan' - orphan the dependents; 'Background' - allow the garbage collector to delete the dependents in the background; 'Foreground' - a cascading policy that deletes all dependents in the foreground.
try {
    V1Status result = apiInstance.deleteNamespacedIncident(name, namespace, body, pretty, gracePeriodSeconds, orphanDependents, propagationPolicy);
    System.out.println(result);
} catch (ApiException e) {
    System.err.println("Exception when calling MonitoringAppscodeComV1alpha1Api#deleteNamespacedIncident");
    e.printStackTrace();
}

Parameters

NameTypeDescriptionNotes
nameStringname of the Incident
namespaceStringobject name and auth scope, such as for teams and projects
bodyV1DeleteOptions
prettyStringIf 'true', then the output is pretty printed.[optional]
gracePeriodSecondsIntegerThe duration in seconds before the object should be deleted. Value must be non-negative integer. The value zero indicates delete immediately. If this value is nil, the default grace period for the specified type will be used. Defaults to a per object value if not specified. zero means delete immediately.[optional]
orphanDependentsBooleanDeprecated: please use the PropagationPolicy, this field will be deprecated in 1.7. Should the dependent objects be orphaned. If true/false, the "orphan" finalizer will be added to/removed from the object's finalizers list. Either this field or PropagationPolicy may be set, but not both.[optional]
propagationPolicyStringWhether and how garbage collection will be performed. Either this field or OrphanDependents may be set, but not both. The default policy is decided by the existing finalizer set in the metadata.finalizers and the resource-specific default policy. Acceptable values are: 'Orphan' - orphan the dependents; 'Background' - allow the garbage collector to delete the dependents in the background; 'Foreground' - a cascading policy that deletes all dependents in the foreground.[optional]

Return type

V1Status

Authorization

No authorization required

HTTP request headers

  • Content-Type: /
  • Accept: application/json, application/yaml, application/vnd.kubernetes.protobuf

deleteNamespacedNodeAlert

V1Status deleteNamespacedNodeAlert(name, namespace, body, pretty, gracePeriodSeconds, orphanDependents, propagationPolicy)

delete a NodeAlert

Example

// Import classes:
//import com.appscode.searchlight.client.ApiException;
//import com.appscode.searchlight.client.apis.MonitoringAppscodeComV1alpha1Api;


MonitoringAppscodeComV1alpha1Api apiInstance = new MonitoringAppscodeComV1alpha1Api();
String name = "name_example"; // String | name of the NodeAlert
String namespace = "namespace_example"; // String | object name and auth scope, such as for teams and projects
V1DeleteOptions body = new V1DeleteOptions(); // V1DeleteOptions | 
String pretty = "pretty_example"; // String | If 'true', then the output is pretty printed.
Integer gracePeriodSeconds = 56; // Integer | The duration in seconds before the object should be deleted. Value must be non-negative integer. The value zero indicates delete immediately. If this value is nil, the default grace period for the specified type will be used. Defaults to a per object value if not specified. zero means delete immediately.
Boolean orphanDependents = true; // Boolean | Deprecated: please use the PropagationPolicy, this field will be deprecated in 1.7. Should the dependent objects be orphaned. If true/false, the \"orphan\" finalizer will be added to/removed from the object's finalizers list. Either this field or PropagationPolicy may be set, but not both.
String propagationPolicy = "propagationPolicy_example"; // String | Whether and how garbage collection will be performed. Either this field or OrphanDependents may be set, but not both. The default policy is decided by the existing finalizer set in the metadata.finalizers and the resource-specific default policy. Acceptable values are: 'Orphan' - orphan the dependents; 'Background' - allow the garbage collector to delete the dependents in the background; 'Foreground' - a cascading policy that deletes all dependents in the foreground.
try {
    V1Status result = apiInstance.deleteNamespacedNodeAlert(name, namespace, body, pretty, gracePeriodSeconds, orphanDependents, propagationPolicy);
    System.out.println(result);
} catch (ApiException e) {
    System.err.println("Exception when calling MonitoringAppscodeComV1alpha1Api#deleteNamespacedNodeAlert");
    e.printStackTrace();
}

Parameters

NameTypeDescriptionNotes
nameStringname of the NodeAlert
namespaceStringobject name and auth scope, such as for teams and projects
bodyV1DeleteOptions
prettyStringIf 'true', then the output is pretty printed.[optional]
gracePeriodSecondsIntegerThe duration in seconds before the object should be deleted. Value must be non-negative integer. The value zero indicates delete immediately. If this value is nil, the default grace period for the specified type will be used. Defaults to a per object value if not specified. zero means delete immediately.[optional]
orphanDependentsBooleanDeprecated: please use the PropagationPolicy, this field will be deprecated in 1.7. Should the dependent objects be orphaned. If true/false, the "orphan" finalizer will be added to/removed from the object's finalizers list. Either this field or PropagationPolicy may be set, but not both.[optional]
propagationPolicyStringWhether and how garbage collection will be performed. Either this field or OrphanDependents may be set, but not both. The default policy is decided by the existing finalizer set in the metadata.finalizers and the resource-specific default policy. Acceptable values are: 'Orphan' - orphan the dependents; 'Background' - allow the garbage collector to delete the dependents in the background; 'Foreground' - a cascading policy that deletes all dependents in the foreground.[optional]

Return type

V1Status

Authorization

No authorization required

HTTP request headers

  • Content-Type: /
  • Accept: application/json, application/yaml, application/vnd.kubernetes.protobuf

deleteNamespacedPodAlert

V1Status deleteNamespacedPodAlert(name, namespace, body, pretty, gracePeriodSeconds, orphanDependents, propagationPolicy)

delete a PodAlert

Example

// Import classes:
//import com.appscode.searchlight.client.ApiException;
//import com.appscode.searchlight.client.apis.MonitoringAppscodeComV1alpha1Api;


MonitoringAppscodeComV1alpha1Api apiInstance = new MonitoringAppscodeComV1alpha1Api();
String name = "name_example"; // String | name of the PodAlert
String namespace = "namespace_example"; // String | object name and auth scope, such as for teams and projects
V1DeleteOptions body = new V1DeleteOptions(); // V1DeleteOptions | 
String pretty = "pretty_example"; // String | If 'true', then the output is pretty printed.
Integer gracePeriodSeconds = 56; // Integer | The duration in seconds before the object should be deleted. Value must be non-negative integer. The value zero indicates delete immediately. If this value is nil, the default grace period for the specified type will be used. Defaults to a per object value if not specified. zero means delete immediately.
Boolean orphanDependents = true; // Boolean | Deprecated: please use the PropagationPolicy, this field will be deprecated in 1.7. Should the dependent objects be orphaned. If true/false, the \"orphan\" finalizer will be added to/removed from the object's finalizers list. Either this field or PropagationPolicy may be set, but not both.
String propagationPolicy = "propagationPolicy_example"; // String | Whether and how garbage collection will be performed. Either this field or OrphanDependents may be set, but not both. The default policy is decided by the existing finalizer set in the metadata.finalizers and the resource-specific default policy. Acceptable values are: 'Orphan' - orphan the dependents; 'Background' - allow the garbage collector to delete the dependents in the background; 'Foreground' - a cascading policy that deletes all dependents in the foreground.
try {
    V1Status result = apiInstance.deleteNamespacedPodAlert(name, namespace, body, pretty, gracePeriodSeconds, orphanDependents, propagationPolicy);
    System.out.println(result);
} catch (ApiException e) {
    System.err.println("Exception when calling MonitoringAppscodeComV1alpha1Api#deleteNamespacedPodAlert");
    e.printStackTrace();
}

Parameters

NameTypeDescriptionNotes
nameStringname of the PodAlert
namespaceStringobject name and auth scope, such as for teams and projects
bodyV1DeleteOptions
prettyStringIf 'true', then the output is pretty printed.[optional]
gracePeriodSecondsIntegerThe duration in seconds before the object should be deleted. Value must be non-negative integer. The value zero indicates delete immediately. If this value is nil, the default grace period for the specified type will be used. Defaults to a per object value if not specified. zero means delete immediately.[optional]
orphanDependentsBooleanDeprecated: please use the PropagationPolicy, this field will be deprecated in 1.7. Should the dependent objects be orphaned. If true/false, the "orphan" finalizer will be added to/removed from the object's finalizers list. Either this field or PropagationPolicy may be set, but not both.[optional]
propagationPolicyStringWhether and how garbage collection will be performed. Either this field or OrphanDependents may be set, but not both. The default policy is decided by the existing finalizer set in the metadata.finalizers and the resource-specific default policy. Acceptable values are: 'Orphan' - orphan the dependents; 'Background' - allow the garbage collector to delete the dependents in the background; 'Foreground' - a cascading policy that deletes all dependents in the foreground.[optional]

Return type

V1Status

Authorization

No authorization required

HTTP request headers

  • Content-Type: /
  • Accept: application/json, application/yaml, application/vnd.kubernetes.protobuf

deleteNamespacedSearchlightPlugin

V1Status deleteNamespacedSearchlightPlugin(name, namespace, body, pretty, gracePeriodSeconds, orphanDependents, propagationPolicy)

delete a SearchlightPlugin

Example

// Import classes:
//import com.appscode.searchlight.client.ApiException;
//import com.appscode.searchlight.client.apis.MonitoringAppscodeComV1alpha1Api;


MonitoringAppscodeComV1alpha1Api apiInstance = new MonitoringAppscodeComV1alpha1Api();
String name = "name_example"; // String | name of the SearchlightPlugin
String namespace = "namespace_example"; // String | object name and auth scope, such as for teams and projects
V1DeleteOptions body = new V1DeleteOptions(); // V1DeleteOptions | 
String pretty = "pretty_example"; // String | If 'true', then the output is pretty printed.
Integer gracePeriodSeconds = 56; // Integer | The duration in seconds before the object should be deleted. Value must be non-negative integer. The value zero indicates delete immediately. If this value is nil, the default grace period for the specified type will be used. Defaults to a per object value if not specified. zero means delete immediately.
Boolean orphanDependents = true; // Boolean | Deprecated: please use the PropagationPolicy, this field will be deprecated in 1.7. Should the dependent objects be orphaned. If true/false, the \"orphan\" finalizer will be added to/removed from the object's finalizers list. Either this field or PropagationPolicy may be set, but not both.
String propagationPolicy = "propagationPolicy_example"; // String | Whether and how garbage collection will be performed. Either this field or OrphanDependents may be set, but not both. The default policy is decided by the existing finalizer set in the metadata.finalizers and the resource-specific default policy. Acceptable values are: 'Orphan' - orphan the dependents; 'Background' - allow the garbage collector to delete the dependents in the background; 'Foreground' - a cascading policy that deletes all dependents in the foreground.
try {
    V1Status result = apiInstance.deleteNamespacedSearchlightPlugin(name, namespace, body, pretty, gracePeriodSeconds, orphanDependents, propagationPolicy);
    System.out.println(result);
} catch (ApiException e) {
    System.err.println("Exception when calling MonitoringAppscodeComV1alpha1Api#deleteNamespacedSearchlightPlugin");
    e.printStackTrace();
}

Parameters

NameTypeDescriptionNotes
nameStringname of the SearchlightPlugin
namespaceStringobject name and auth scope, such as for teams and projects
bodyV1DeleteOptions
prettyStringIf 'true', then the output is pretty printed.[optional]
gracePeriodSecondsIntegerThe duration in seconds before the object should be deleted. Value must be non-negative integer. The value zero indicates delete immediately. If this value is nil, the default grace period for the specified type will be used. Defaults to a per object value if not specified. zero means delete immediately.[optional]
orphanDependentsBooleanDeprecated: please use the PropagationPolicy, this field will be deprecated in 1.7. Should the dependent objects be orphaned. If true/false, the "orphan" finalizer will be added to/removed from the object's finalizers list. Either this field or PropagationPolicy may be set, but not both.[optional]
propagationPolicyStringWhether and how garbage collection will be performed. Either this field or OrphanDependents may be set, but not both. The default policy is decided by the existing finalizer set in the metadata.finalizers and the resource-specific default policy. Acceptable values are: 'Orphan' - orphan the dependents; 'Background' - allow the garbage collector to delete the dependents in the background; 'Foreground' - a cascading policy that deletes all dependents in the foreground.[optional]

Return type

V1Status

Authorization

No authorization required

HTTP request headers

  • Content-Type: /
  • Accept: application/json, application/yaml, application/vnd.kubernetes.protobuf

getAPIResources

V1APIResourceList getAPIResources()

get available resources

Example

// Import classes:
//import com.appscode.searchlight.client.ApiException;
//import com.appscode.searchlight.client.apis.MonitoringAppscodeComV1alpha1Api;


MonitoringAppscodeComV1alpha1Api apiInstance = new MonitoringAppscodeComV1alpha1Api();
try {
    V1APIResourceList result = apiInstance.getAPIResources();
    System.out.println(result);
} catch (ApiException e) {
    System.err.println("Exception when calling MonitoringAppscodeComV1alpha1Api#getAPIResources");
    e.printStackTrace();
}

Parameters

This endpoint does not need any parameter.

Return type

V1APIResourceList

Authorization

No authorization required

HTTP request headers

  • Content-Type: application/json, application/yaml, application/vnd.kubernetes.protobuf
  • Accept: application/json, application/yaml, application/vnd.kubernetes.protobuf

listClusterAlertForAllNamespaces

V1alpha1ClusterAlertList listClusterAlertForAllNamespaces(_continue, fieldSelector, includeUninitialized, labelSelector, limit, pretty, resourceVersion, timeoutSeconds, watch)

list or watch objects of kind ClusterAlert

Example

// Import classes:
//import com.appscode.searchlight.client.ApiException;
//import com.appscode.searchlight.client.apis.MonitoringAppscodeComV1alpha1Api;


MonitoringAppscodeComV1alpha1Api apiInstance = new MonitoringAppscodeComV1alpha1Api();
String _continue = "_continue_example"; // String | The continue option should be set when retrieving more results from the server. Since this value is server defined, clients may only use the continue value from a previous query result with identical query parameters (except for the value of continue) and the server may reject a continue value it does not recognize. If the specified continue value is no longer valid whether due to expiration (generally five to fifteen minutes) or a configuration change on the server the server will respond with a 410 ResourceExpired error indicating the client must restart their list without the continue field. This field is not supported when watch is true. Clients may start a watch from the last resourceVersion value returned by the server and not miss any modifications.
String fieldSelector = "fieldSelector_example"; // String | A selector to restrict the list of returned objects by their fields. Defaults to everything.
Boolean includeUninitialized = true; // Boolean | If true, partially initialized resources are included in the response.
String labelSelector = "labelSelector_example"; // String | A selector to restrict the list of returned objects by their labels. Defaults to everything.
Integer limit = 56; // Integer | limit is a maximum number of responses to return for a list call. If more items exist, the server will set the `continue` field on the list metadata to a value that can be used with the same initial query to retrieve the next set of results. Setting a limit may return fewer than the requested amount of items (up to zero items) in the event all requested objects are filtered out and clients should only use the presence of the continue field to determine whether more results are available. Servers may choose not to support the limit argument and will return all of the available results. If limit is specified and the continue field is empty, clients may assume that no more results are available. This field is not supported if watch is true.  The server guarantees that the objects returned when using continue will be identical to issuing a single list call without a limit - that is, no objects created, modified, or deleted after the first request is issued will be included in any subsequent continued requests. This is sometimes referred to as a consistent snapshot, and ensures that a client that is using limit to receive smaller chunks of a very large result can ensure they see all possible objects. If objects are updated during a chunked list the version of the object that was present at the time the first list result was calculated is returned.
String pretty = "pretty_example"; // String | If 'true', then the output is pretty printed.
String resourceVersion = "resourceVersion_example"; // String | When specified with a watch call, shows changes that occur after that particular version of a resource. Defaults to changes from the beginning of history. When specified for list: - if unset, then the result is returned from remote storage based on quorum-read flag; - if it's 0, then we simply return what we currently have in cache, no guarantee; - if set to non zero, then the result is at least as fresh as given rv.
Integer timeoutSeconds = 56; // Integer | Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.
Boolean watch = true; // Boolean | Watch for changes to the described resources and return them as a stream of add, update, and remove notifications. Specify resourceVersion.
try {
    V1alpha1ClusterAlertList result = apiInstance.listClusterAlertForAllNamespaces(_continue, fieldSelector, includeUninitialized, labelSelector, limit, pretty, resourceVersion, timeoutSeconds, watch);
    System.out.println(result);
} catch (ApiException e) {
    System.err.println("Exception when calling MonitoringAppscodeComV1alpha1Api#listClusterAlertForAllNamespaces");
    e.printStackTrace();
}

Parameters

NameTypeDescriptionNotes
_continueStringThe continue option should be set when retrieving more results from the server. Since this value is server defined, clients may only use the continue value from a previous query result with identical query parameters (except for the value of continue) and the server may reject a continue value it does not recognize. If the specified continue value is no longer valid whether due to expiration (generally five to fifteen minutes) or a configuration change on the server the server will respond with a 410 ResourceExpired error indicating the client must restart their list without the continue field. This field is not supported when watch is true. Clients may start a watch from the last resourceVersion value returned by the server and not miss any modifications.[optional]
fieldSelectorStringA selector to restrict the list of returned objects by their fields. Defaults to everything.[optional]
includeUninitializedBooleanIf true, partially initialized resources are included in the response.[optional]
labelSelectorStringA selector to restrict the list of returned objects by their labels. Defaults to everything.[optional]
limitIntegerlimit is a maximum number of responses to return for a list call. If more items exist, the server will set the `continue` field on the list metadata to a value that can be used with the same initial query to retrieve the next set of results. Setting a limit may return fewer than the requested amount of items (up to zero items) in the event all requested objects are filtered out and clients should only use the presence of the continue field to determine whether more results are available. Servers may choose not to support the limit argument and will return all of the available results. If limit is specified and the continue field is empty, clients may assume that no more results are available. This field is not supported if watch is true. The server guarantees that the objects returned when using continue will be identical to issuing a single list call without a limit - that is, no objects created, modified, or deleted after the first request is issued will be included in any subsequent continued requests. This is sometimes referred to as a consistent snapshot, and ensures that a client that is using limit to receive smaller chunks of a very large result can ensure they see all possible objects. If objects are updated during a chunked list the version of the object that was present at the time the first list result was calculated is returned.[optional]
prettyStringIf 'true', then the output is pretty printed.[optional]
resourceVersionStringWhen specified with a watch call, shows changes that occur after that particular version of a resource. Defaults to changes from the beginning of history. When specified for list: - if unset, then the result is returned from remote storage based on quorum-read flag; - if it's 0, then we simply return what we currently have in cache, no guarantee; - if set to non zero, then the result is at least as fresh as given rv.[optional]
timeoutSecondsIntegerTimeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.[optional]
watchBooleanWatch for changes to the described resources and return them as a stream of add, update, and remove notifications. Specify resourceVersion.[optional]

Return type

V1alpha1ClusterAlertList

Authorization

No authorization required

HTTP request headers

  • Content-Type: /
  • Accept: application/json, application/yaml, application/vnd.kubernetes.protobuf, application/json;stream=watch, application/vnd.kubernetes.protobuf;stream=watch

listIncidentForAllNamespaces

V1alpha1IncidentList listIncidentForAllNamespaces(_continue, fieldSelector, includeUninitialized, labelSelector, limit, pretty, resourceVersion, timeoutSeconds, watch)

list or watch objects of kind Incident

Example

// Import classes:
//import com.appscode.searchlight.client.ApiException;
//import com.appscode.searchlight.client.apis.MonitoringAppscodeComV1alpha1Api;


MonitoringAppscodeComV1alpha1Api apiInstance = new MonitoringAppscodeComV1alpha1Api();
String _continue = "_continue_example"; // String | The continue option should be set when retrieving more results from the server. Since this value is server defined, clients may only use the continue value from a previous query result with identical query parameters (except for the value of continue) and the server may reject a continue value it does not recognize. If the specified continue value is no longer valid whether due to expiration (generally five to fifteen minutes) or a configuration change on the server the server will respond with a 410 ResourceExpired error indicating the client must restart their list without the continue field. This field is not supported when watch is true. Clients may start a watch from the last resourceVersion value returned by the server and not miss any modifications.
String fieldSelector = "fieldSelector_example"; // String | A selector to restrict the list of returned objects by their fields. Defaults to everything.
Boolean includeUninitialized = true; // Boolean | If true, partially initialized resources are included in the response.
String labelSelector = "labelSelector_example"; // String | A selector to restrict the list of returned objects by their labels. Defaults to everything.
Integer limit = 56; // Integer | limit is a maximum number of responses to return for a list call. If more items exist, the server will set the `continue` field on the list metadata to a value that can be used with the same initial query to retrieve the next set of results. Setting a limit may return fewer than the requested amount of items (up to zero items) in the event all requested objects are filtered out and clients should only use the presence of the continue field to determine whether more results are available. Servers may choose not to support the limit argument and will return all of the available results. If limit is specified and the continue field is empty, clients may assume that no more results are available. This field is not supported if watch is true.  The server guarantees that the objects returned when using continue will be identical to issuing a single list call without a limit - that is, no objects created, modified, or deleted after the first request is issued will be included in any subsequent continued requests. This is sometimes referred to as a consistent snapshot, and ensures that a client that is using limit to receive smaller chunks of a very large result can ensure they see all possible objects. If objects are updated during a chunked list the version of the object that was present at the time the first list result was calculated is returned.
String pretty = "pretty_example"; // String | If 'true', then the output is pretty printed.
String resourceVersion = "resourceVersion_example"; // String | When specified with a watch call, shows changes that occur after that particular version of a resource. Defaults to changes from the beginning of history. When specified for list: - if unset, then the result is returned from remote storage based on quorum-read flag; - if it's 0, then we simply return what we currently have in cache, no guarantee; - if set to non zero, then the result is at least as fresh as given rv.
Integer timeoutSeconds = 56; // Integer | Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.
Boolean watch = true; // Boolean | Watch for changes to the described resources and return them as a stream of add, update, and remove notifications. Specify resourceVersion.
try {
    V1alpha1IncidentList result = apiInstance.listIncidentForAllNamespaces(_continue, fieldSelector, includeUninitialized, labelSelector, limit, pretty, resourceVersion, timeoutSeconds, watch);
    System.out.println(result);
} catch (ApiException e) {
    System.err.println("Exception when calling MonitoringAppscodeComV1alpha1Api#listIncidentForAllNamespaces");
    e.printStackTrace();
}

Parameters

NameTypeDescriptionNotes
_continueStringThe continue option should be set when retrieving more results from the server. Since this value is server defined, clients may only use the continue value from a previous query result with identical query parameters (except for the value of continue) and the server may reject a continue value it does not recognize. If the specified continue value is no longer valid whether due to expiration (generally five to fifteen minutes) or a configuration change on the server the server will respond with a 410 ResourceExpired error indicating the client must restart their list without the continue field. This field is not supported when watch is true. Clients may start a watch from the last resourceVersion value returned by the server and not miss any modifications.[optional]
fieldSelectorStringA selector to restrict the list of returned objects by their fields. Defaults to everything.[optional]
includeUninitializedBooleanIf true, partially initialized resources are included in the response.[optional]
labelSelectorStringA selector to restrict the list of returned objects by their labels. Defaults to everything.[optional]
limitIntegerlimit is a maximum number of responses to return for a list call. If more items exist, the server will set the `continue` field on the list metadata to a value that can be used with the same initial query to retrieve the next set of results. Setting a limit may return fewer than the requested amount of items (up to zero items) in the event all requested objects are filtered out and clients should only use the presence of the continue field to determine whether more results are available. Servers may choose not to support the limit argument and will return all of the available results. If limit is specified and the continue field is empty, clients may assume that no more results are available. This field is not supported if watch is true. The server guarantees that the objects returned when using continue will be identical to issuing a single list call without a limit - that is, no objects created, modified, or deleted after the first request is issued will be included in any subsequent continued requests. This is sometimes referred to as a consistent snapshot, and ensures that a client that is using limit to receive smaller chunks of a very large result can ensure they see all possible objects. If objects are updated during a chunked list the version of the object that was present at the time the first list result was calculated is returned.[optional]
prettyStringIf 'true', then the output is pretty printed.[optional]
resourceVersionStringWhen specified with a watch call, shows changes that occur after that particular version of a resource. Defaults to changes from the beginning of history. When specified for list: - if unset, then the result is returned from remote storage based on quorum-read flag; - if it's 0, then we simply return what we currently have in cache, no guarantee; - if set to non zero, then the result is at least as fresh as given rv.[optional]
timeoutSecondsIntegerTimeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.[optional]
watchBooleanWatch for changes to the described resources and return them as a stream of add, update, and remove notifications. Specify resourceVersion.[optional]

Return type

V1alpha1IncidentList

Authorization

No authorization required

HTTP request headers

  • Content-Type: /
  • Accept: application/json, application/yaml, application/vnd.kubernetes.protobuf, application/json;stream=watch, application/vnd.kubernetes.protobuf;stream=watch

listNamespacedClusterAlert

V1alpha1ClusterAlertList listNamespacedClusterAlert(namespace, pretty, _continue, fieldSelector, includeUninitialized, labelSelector, limit, resourceVersion, timeoutSeconds, watch)

list or watch objects of kind ClusterAlert

Example

// Import classes:
//import com.appscode.searchlight.client.ApiException;
//import com.appscode.searchlight.client.apis.MonitoringAppscodeComV1alpha1Api;


MonitoringAppscodeComV1alpha1Api apiInstance = new MonitoringAppscodeComV1alpha1Api();
String namespace = "namespace_example"; // String | object name and auth scope, such as for teams and projects
String pretty = "pretty_example"; // String | If 'true', then the output is pretty printed.
String _continue = "_continue_example"; // String | The continue option should be set when retrieving more results from the server. Since this value is server defined, clients may only use the continue value from a previous query result with identical query parameters (except for the value of continue) and the server may reject a continue value it does not recognize. If the specified continue value is no longer valid whether due to expiration (generally five to fifteen minutes) or a configuration change on the server the server will respond with a 410 ResourceExpired error indicating the client must restart their list without the continue field. This field is not supported when watch is true. Clients may start a watch from the last resourceVersion value returned by the server and not miss any modifications.
String fieldSelector = "fieldSelector_example"; // String | A selector to restrict the list of returned objects by their fields. Defaults to everything.
Boolean includeUninitialized = true; // Boolean | If true, partially initialized resources are included in the response.
String labelSelector = "labelSelector_example"; // String | A selector to restrict the list of returned objects by their labels. Defaults to everything.
Integer limit = 56; // Integer | limit is a maximum number of responses to return for a list call. If more items exist, the server will set the `continue` field on the list metadata to a value that can be used with the same initial query to retrieve the next set of results. Setting a limit may return fewer than the requested amount of items (up to zero items) in the event all requested objects are filtered out and clients should only use the presence of the continue field to determine whether more results are available. Servers may choose not to support the limit argument and will return all of the available results. If limit is specified and the continue field is empty, clients may assume that no more results are available. This field is not supported if watch is true.  The server guarantees that the objects returned when using continue will be identical to issuing a single list call without a limit - that is, no objects created, modified, or deleted after the first request is issued will be included in any subsequent continued requests. This is sometimes referred to as a consistent snapshot, and ensures that a client that is using limit to receive smaller chunks of a very large result can ensure they see all possible objects. If objects are updated during a chunked list the version of the object that was present at the time the first list result was calculated is returned.
String resourceVersion = "resourceVersion_example"; // String | When specified with a watch call, shows changes that occur after that particular version of a resource. Defaults to changes from the beginning of history. When specified for list: - if unset, then the result is returned from remote storage based on quorum-read flag; - if it's 0, then we simply return what we currently have in cache, no guarantee; - if set to non zero, then the result is at least as fresh as given rv.
Integer timeoutSeconds = 56; // Integer | Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.
Boolean watch = true; // Boolean | Watch for changes to the described resources and return them as a stream of add, update, and remove notifications. Specify resourceVersion.
try {
    V1alpha1ClusterAlertList result = apiInstance.listNamespacedClusterAlert(namespace, pretty, _continue, fieldSelector, includeUninitialized, labelSelector, limit, resourceVersion, timeoutSeconds, watch);
    System.out.println(result);
} catch (ApiException e) {
    System.err.println("Exception when calling MonitoringAppscodeComV1alpha1Api#listNamespacedClusterAlert");
    e.printStackTrace();
}

Parameters

NameTypeDescriptionNotes
namespaceStringobject name and auth scope, such as for teams and projects
prettyStringIf 'true', then the output is pretty printed.[optional]
_continueStringThe continue option should be set when retrieving more results from the server. Since this value is server defined, clients may only use the continue value from a previous query result with identical query parameters (except for the value of continue) and the server may reject a continue value it does not recognize. If the specified continue value is no longer valid whether due to expiration (generally five to fifteen minutes) or a configuration change on the server the server will respond with a 410 ResourceExpired error indicating the client must restart their list without the continue field. This field is not supported when watch is true. Clients may start a watch from the last resourceVersion value returned by the server and not miss any modifications.[optional]
fieldSelectorStringA selector to restrict the list of returned objects by their fields. Defaults to everything.[optional]
includeUninitializedBooleanIf true, partially initialized resources are included in the response.[optional]
labelSelectorStringA selector to restrict the list of returned objects by their labels. Defaults to everything.[optional]
limitIntegerlimit is a maximum number of responses to return for a list call. If more items exist, the server will set the `continue` field on the list metadata to a value that can be used with the same initial query to retrieve the next set of results. Setting a limit may return fewer than the requested amount of items (up to zero items) in the event all requested objects are filtered out and clients should only use the presence of the continue field to determine whether more results are available. Servers may choose not to support the limit argument and will return all of the available results. If limit is specified and the continue field is empty, clients may assume that no more results are available. This field is not supported if watch is true. The server guarantees that the objects returned when using continue will be identical to issuing a single list call without a limit - that is, no objects created, modified, or deleted after the first request is issued will be included in any subsequent continued requests. This is sometimes referred to as a consistent snapshot, and ensures that a client that is using limit to receive smaller chunks of a very large result can ensure they see all possible objects. If objects are updated during a chunked list the version of the object that was present at the time the first list result was calculated is returned.[optional]
resourceVersionStringWhen specified with a watch call, shows changes that occur after that particular version of a resource. Defaults to changes from the beginning of history. When specified for list: - if unset, then the result is returned from remote storage based on quorum-read flag; - if it's 0, then we simply return what we currently have in cache, no guarantee; - if set to non zero, then the result is at least as fresh as given rv.[optional]
timeoutSecondsIntegerTimeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.[optional]
watchBooleanWatch for changes to the described resources and return them as a stream of add, update, and remove notifications. Specify resourceVersion.[optional]

Return type

V1alpha1ClusterAlertList

Authorization

No authorization required

HTTP request headers

  • Content-Type: /
  • Accept: application/json, application/yaml, application/vnd.kubernetes.protobuf, application/json;stream=watch, application/vnd.kubernetes.protobuf;stream=watch

listNamespacedIncident

V1alpha1IncidentList listNamespacedIncident(namespace, pretty, _continue, fieldSelector, includeUninitialized, labelSelector, limit, resourceVersion, timeoutSeconds, watch)

list or watch objects of kind Incident

Example

// Import classes:
//import com.appscode.searchlight.client.ApiException;
//import com.appscode.searchlight.client.apis.MonitoringAppscodeComV1alpha1Api;


MonitoringAppscodeComV1alpha1Api apiInstance = new MonitoringAppscodeComV1alpha1Api();
String namespace = "namespace_example"; // String | object name and auth scope, such as for teams and projects
String pretty = "pretty_example"; // String | If 'true', then the output is pretty printed.
String _continue = "_continue_example"; // String | The continue option should be set when retrieving more results from the server. Since this value is server defined, clients may only use the continue value from a previous query result with identical query parameters (except for the value of continue) and the server may reject a continue value it does not recognize. If the specified continue value is no longer valid whether due to expiration (generally five to fifteen minutes) or a configuration change on the server the server will respond with a 410 ResourceExpired error indicating the client must restart their list without the continue field. This field is not supported when watch is true. Clients may start a watch from the last resourceVersion value returned by the server and not miss any modifications.
String fieldSelector = "fieldSelector_example"; // String | A selector to restrict the list of returned objects by their fields. Defaults to everything.
Boolean includeUninitialized = true; // Boolean | If true, partially initialized resources are included in the response.
String labelSelector = "labelSelector_example"; // String | A selector to restrict the list of returned objects by their labels. Defaults to everything.
Integer limit = 56; // Integer | limit is a maximum number of responses to return for a list call. If more items exist, the server will set the `continue` field on the list metadata to a value that can be used with the same initial query to retrieve the next set of results. Setting a limit may return fewer than the requested amount of items (up to zero items) in the event all requested objects are filtered out and clients should only use the presence of the continue field to determine whether more results are available. Servers may choose not to support the limit argument and will return all of the available results. If limit is specified and the continue field is empty, clients may assume that no more results are available. This field is not supported if watch is true.  The server guarantees that the objects returned when using continue will be identical to issuing a single list call without a limit - that is, no objects created, modified, or deleted after the first request is issued will be included in any subsequent continued requests. This is sometimes referred to as a consistent snapshot, and ensures that a client that is using limit to receive smaller chunks of a very large result can ensure they see all possible objects. If objects are updated during a chunked list the version of the object that was present at the time the first list result was calculated is returned.
String resourceVersion = "resourceVersion_example"; // String | When specified with a watch call, shows changes that occur after that particular version of a resource. Defaults to changes from the beginning of history. When specified for list: - if unset, then the result is returned from remote storage based on quorum-read flag; - if it's 0, then we simply return what we currently have in cache, no guarantee; - if set to non zero, then the result is at least as fresh as given rv.
Integer timeoutSeconds = 56; // Integer | Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.
Boolean watch = true; // Boolean | Watch for changes to the described resources and return them as a stream of add, update, and remove notifications. Specify resourceVersion.
try {
    V1alpha1IncidentList result = apiInstance.listNamespacedIncident(namespace, pretty, _continue, fieldSelector, includeUninitialized, labelSelector, limit, resourceVersion, timeoutSeconds, watch);
    System.out.println(result);
} catch (ApiException e) {
    System.err.println("Exception when calling MonitoringAppscodeComV1alpha1Api#listNamespacedIncident");
    e.printStackTrace();
}

Parameters

NameTypeDescriptionNotes
namespaceStringobject name and auth scope, such as for teams and projects
prettyStringIf 'true', then the output is pretty printed.[optional]
_continueStringThe continue option should be set when retrieving more results from the server. Since this value is server defined, clients may only use the continue value from a previous query result with identical query parameters (except for the value of continue) and the server may reject a continue value it does not recognize. If the specified continue value is no longer valid whether due to expiration (generally five to fifteen minutes) or a configuration change on the server the server will respond with a 410 ResourceExpired error indicating the client must restart their list without the continue field. This field is not supported when watch is true. Clients may start a watch from the last resourceVersion value returned by the server and not miss any modifications.[optional]
fieldSelectorStringA selector to restrict the list of returned objects by their fields. Defaults to everything.[optional]
includeUninitializedBooleanIf true, partially initialized resources are included in the response.[optional]
labelSelectorStringA selector to restrict the list of returned objects by their labels. Defaults to everything.[optional]
limitIntegerlimit is a maximum number of responses to return for a list call. If more items exist, the server will set the `continue` field on the list metadata to a value that can be used with the same initial query to retrieve the next set of results. Setting a limit may return fewer than the requested amount of items (up to zero items) in the event all requested objects are filtered out and clients should only use the presence of the continue field to determine whether more results are available. Servers may choose not to support the limit argument and will return all of the available results. If limit is specified and the continue field is empty, clients may assume that no more results are available. This field is not supported if watch is true. The server guarantees that the objects returned when using continue will be identical to issuing a single list call without a limit - that is, no objects created, modified, or deleted after the first request is issued will be included in any subsequent continued requests. This is sometimes referred to as a consistent snapshot, and ensures that a client that is using limit to receive smaller chunks of a very large result can ensure they see all possible objects. If objects are updated during a chunked list the version of the object that was present at the time the first list result was calculated is returned.[optional]
resourceVersionStringWhen specified with a watch call, shows changes that occur after that particular version of a resource. Defaults to changes from the beginning of history. When specified for list: - if unset, then the result is returned from remote storage based on quorum-read flag; - if it's 0, then we simply return what we currently have in cache, no guarantee; - if set to non zero, then the result is at least as fresh as given rv.[optional]
timeoutSecondsIntegerTimeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.[optional]
watchBooleanWatch for changes to the described resources and return them as a stream of add, update, and remove notifications. Specify resourceVersion.[optional]

Return type

V1alpha1IncidentList

Authorization

No authorization required

HTTP request headers

  • Content-Type: /
  • Accept: application/json, application/yaml, application/vnd.kubernetes.protobuf, application/json;stream=watch, application/vnd.kubernetes.protobuf;stream=watch

listNamespacedNodeAlert

V1alpha1NodeAlertList listNamespacedNodeAlert(namespace, pretty, _continue, fieldSelector, includeUninitialized, labelSelector, limit, resourceVersion, timeoutSeconds, watch)

list or watch objects of kind NodeAlert

Example

// Import classes:
//import com.appscode.searchlight.client.ApiException;
//import com.appscode.searchlight.client.apis.MonitoringAppscodeComV1alpha1Api;


MonitoringAppscodeComV1alpha1Api apiInstance = new MonitoringAppscodeComV1alpha1Api();
String namespace = "namespace_example"; // String | object name and auth scope, such as for teams and projects
String pretty = "pretty_example"; // String | If 'true', then the output is pretty printed.
String _continue = "_continue_example"; // String | The continue option should be set when retrieving more results from the server. Since this value is server defined, clients may only use the continue value from a previous query result with identical query parameters (except for the value of continue) and the server may reject a continue value it does not recognize. If the specified continue value is no longer valid whether due to expiration (generally five to fifteen minutes) or a configuration change on the server the server will respond with a 410 ResourceExpired error indicating the client must restart their list without the continue field. This field is not supported when watch is true. Clients may start a watch from the last resourceVersion value returned by the server and not miss any modifications.
String fieldSelector = "fieldSelector_example"; // String | A selector to restrict the list of returned objects by their fields. Defaults to everything.
Boolean includeUninitialized = true; // Boolean | If true, partially initialized resources are included in the response.
String labelSelector = "labelSelector_example"; // String | A selector to restrict the list of returned objects by their labels. Defaults to everything.
Integer limit = 56; // Integer | limit is a maximum number of responses to return for a list call. If more items exist, the server will set the `continue` field on the list metadata to a value that can be used with the same initial query to retrieve the next set of results. Setting a limit may return fewer than the requested amount of items (up to zero items) in the event all requested objects are filtered out and clients should only use the presence of the continue field to determine whether more results are available. Servers may choose not to support the limit argument and will return all of the available results. If limit is specified and the continue field is empty, clients may assume that no more results are available. This field is not supported if watch is true.  The server guarantees that the objects returned when using continue will be identical to issuing a single list call without a limit - that is, no objects created, modified, or deleted after the first request is issued will be included in any subsequent continued requests. This is sometimes referred to as a consistent snapshot, and ensures that a client that is using limit to receive smaller chunks of a very large result can ensure they see all possible objects. If objects are updated during a chunked list the version of the object that was present at the time the first list result was calculated is returned.
String resourceVersion = "resourceVersion_example"; // String | When specified with a watch call, shows changes that occur after that particular version of a resource. Defaults to changes from the beginning of history. When specified for list: - if unset, then the result is returned from remote storage based on quorum-read flag; - if it's 0, then we simply return what we currently have in cache, no guarantee; - if set to non zero, then the result is at least as fresh as given rv.
Integer timeoutSeconds = 56; // Integer | Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.
Boolean watch = true; // Boolean | Watch for changes to the described resources and return them as a stream of add, update, and remove notifications. Specify resourceVersion.
try {
    V1alpha1NodeAlertList result = apiInstance.listNamespacedNodeAlert(namespace, pretty, _continue, fieldSelector, includeUninitialized, labelSelector, limit, resourceVersion, timeoutSeconds, watch);
    System.out.println(result);
} catch (ApiException e) {
    System.err.println("Exception when calling MonitoringAppscodeComV1alpha1Api#listNamespacedNodeAlert");
    e.printStackTrace();
}

Parameters

NameTypeDescriptionNotes
namespaceStringobject name and auth scope, such as for teams and projects
prettyStringIf 'true', then the output is pretty printed.[optional]
_continueStringThe continue option should be set when retrieving more results from the server. Since this value is server defined, clients may only use the continue value from a previous query result with identical query parameters (except for the value of continue) and the server may reject a continue value it does not recognize. If the specified continue value is no longer valid whether due to expiration (generally five to fifteen minutes) or a configuration change on the server the server will respond with a 410 ResourceExpired error indicating the client must restart their list without the continue field. This field is not supported when watch is true. Clients may start a watch from the last resourceVersion value returned by the server and not miss any modifications.[optional]
fieldSelectorStringA selector to restrict the list of returned objects by their fields. Defaults to everything.[optional]
includeUninitializedBooleanIf true, partially initialized resources are included in the response.[optional]
labelSelectorStringA selector to restrict the list of returned objects by their labels. Defaults to everything.[optional]
limitIntegerlimit is a maximum number of responses to return for a list call. If more items exist, the server will set the `continue` field on the list metadata to a value that can be used with the same initial query to retrieve the next set of results. Setting a limit may return fewer than the requested amount of items (up to zero items) in the event all requested objects are filtered out and clients should only use the presence of the continue field to determine whether more results are available. Servers may choose not to support the limit argument and will return all of the available results. If limit is specified and the continue field is empty, clients may assume that no more results are available. This field is not supported if watch is true. The server guarantees that the objects returned when using continue will be identical to issuing a single list call without a limit - that is, no objects created, modified, or deleted after the first request is issued will be included in any subsequent continued requests. This is sometimes referred to as a consistent snapshot, and ensures that a client that is using limit to receive smaller chunks of a very large result can ensure they see all possible objects. If objects are updated during a chunked list the version of the object that was present at the time the first list result was calculated is returned.[optional]
resourceVersionStringWhen specified with a watch call, shows changes that occur after that particular version of a resource. Defaults to changes from the beginning of history. When specified for list: - if unset, then the result is returned from remote storage based on quorum-read flag; - if it's 0, then we simply return what we currently have in cache, no guarantee; - if set to non zero, then the result is at least as fresh as given rv.[optional]
timeoutSecondsIntegerTimeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.[optional]
watchBooleanWatch for changes to the described resources and return them as a stream of add, update, and remove notifications. Specify resourceVersion.[optional]

Return type

V1alpha1NodeAlertList

Authorization

No authorization required

HTTP request headers

  • Content-Type: /
  • Accept: application/json, application/yaml, application/vnd.kubernetes.protobuf, application/json;stream=watch, application/vnd.kubernetes.protobuf;stream=watch

listNamespacedPodAlert

V1alpha1PodAlertList listNamespacedPodAlert(namespace, pretty, _continue, fieldSelector, includeUninitialized, labelSelector, limit, resourceVersion, timeoutSeconds, watch)

list or watch objects of kind PodAlert

Example

// Import classes:
//import com.appscode.searchlight.client.ApiException;
//import com.appscode.searchlight.client.apis.MonitoringAppscodeComV1alpha1Api;


MonitoringAppscodeComV1alpha1Api apiInstance = new MonitoringAppscodeComV1alpha1Api();
String namespace = "namespace_example"; // String | object name and auth scope, such as for teams and projects
String pretty = "pretty_example"; // String | If 'true', then the output is pretty printed.
String _continue = "_continue_example"; // String | The continue option should be set when retrieving more results from the server. Since this value is server defined, clients may only use the continue value from a previous query result with identical query parameters (except for the value of continue) and the server may reject a continue value it does not recognize. If the specified continue value is no longer valid whether due to expiration (generally five to fifteen minutes) or a configuration change on the server the server will respond with a 410 ResourceExpired error indicating the client must restart their list without the continue field. This field is not supported when watch is true. Clients may start a watch from the last resourceVersion value returned by the server and not miss any modifications.
String fieldSelector = "fieldSelector_example"; // String | A selector to restrict the list of returned objects by their fields. Defaults to everything.
Boolean includeUninitialized = true; // Boolean | If true, partially initialized resources are included in the response.
String labelSelector = "labelSelector_example"; // String | A selector to restrict the list of returned objects by their labels. Defaults to everything.
Integer limit = 56; // Integer | limit is a maximum number of responses to return for a list call. If more items exist, the server will set the `continue` field on the list metadata to a value that can be used with the same initial query to retrieve the next set of results. Setting a limit may return fewer than the requested amount of items (up to zero items) in the event all requested objects are filtered out and clients should only use the presence of the continue field to determine whether more results are available. Servers may choose not to support the limit argument and will return all of the available results. If limit is specified and the continue field is empty, clients may assume that no more results are available. This field is not supported if watch is true.  The server guarantees that the objects returned when using continue will be identical to issuing a single list call without a limit - that is, no objects created, modified, or deleted after the first request is issued will be included in any subsequent continued requests. This is sometimes referred to as a consistent snapshot, and ensures that a client that is using limit to receive smaller chunks of a very large result can ensure they see all possible objects. If objects are updated during a chunked list the version of the object that was present at the time the first list result was calculated is returned.
String resourceVersion = "resourceVersion_example"; // String | When specified with a watch call, shows changes that occur after that particular version of a resource. Defaults to changes from the beginning of history. When specified for list: - if unset, then the result is returned from remote storage based on quorum-read flag; - if it's 0, then we simply return what we currently have in cache, no guarantee; - if set to non zero, then the result is at least as fresh as given rv.
Integer timeoutSeconds = 56; // Integer | Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.
Boolean watch = true; // Boolean | Watch for changes to the described resources and return them as a stream of add, update, and remove notifications. Specify resourceVersion.
try {
    V1alpha1PodAlertList result = apiInstance.listNamespacedPodAlert(namespace, pretty, _continue, fieldSelector, includeUninitialized, labelSelector, limit, resourceVersion, timeoutSeconds, watch);
    System.out.println(result);
} catch (ApiException e) {
    System.err.println("Exception when calling MonitoringAppscodeComV1alpha1Api#listNamespacedPodAlert");
    e.printStackTrace();
}

Parameters

NameTypeDescriptionNotes
namespaceStringobject name and auth scope, such as for teams and projects
prettyStringIf 'true', then the output is pretty printed.[optional]
_continueStringThe continue option should be set when retrieving more results from the server. Since this value is server defined, clients may only use the continue value from a previous query result with identical query parameters (except for the value of continue) and the server may reject a continue value it does not recognize. If the specified continue value is no longer valid whether due to expiration (generally five to fifteen minutes) or a configuration change on the server the server will respond with a 410 ResourceExpired error indicating the client must restart their list without the continue field. This field is not supported when watch is true. Clients may start a watch from the last resourceVersion value returned by the server and not miss any modifications.[optional]
fieldSelectorStringA selector to restrict the list of returned objects by their fields. Defaults to everything.[optional]
includeUninitializedBooleanIf true, partially initialized resources are included in the response.[optional]
labelSelectorStringA selector to restrict the list of returned objects by their labels. Defaults to everything.[optional]
limitIntegerlimit is a maximum number of responses to return for a list call. If more items exist, the server will set the `continue` field on the list metadata to a value that can be used with the same initial query to retrieve the next set of results. Setting a limit may return fewer than the requested amount of items (up to zero items) in the event all requested objects are filtered out and clients should only use the presence of the continue field to determine whether more results are available. Servers may choose not to support the limit argument and will return all of the available results. If limit is specified and the continue field is empty, clients may assume that no more results are available. This field is not supported if watch is true. The server guarantees that the objects returned when using continue will be identical to issuing a single list call without a limit - that is, no objects created, modified, or deleted after the first request is issued will be included in any subsequent continued requests. This is sometimes referred to as a consistent snapshot, and ensures that a client that is using limit to receive smaller chunks of a very large result can ensure they see all possible objects. If objects are updated during a chunked list the version of the object that was present at the time the first list result was calculated is returned.[optional]
resourceVersionStringWhen specified with a watch call, shows changes that occur after that particular version of a resource. Defaults to changes from the beginning of history. When specified for list: - if unset, then the result is returned from remote storage based on quorum-read flag; - if it's 0, then we simply return what we currently have in cache, no guarantee; - if set to non zero, then the result is at least as fresh as given rv.[optional]
timeoutSecondsIntegerTimeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.[optional]
watchBooleanWatch for changes to the described resources and return them as a stream of add, update, and remove notifications. Specify resourceVersion.[optional]

Return type

V1alpha1PodAlertList

Authorization

No authorization required

HTTP request headers

  • Content-Type: /
  • Accept: application/json, application/yaml, application/vnd.kubernetes.protobuf, application/json;stream=watch, application/vnd.kubernetes.protobuf;stream=watch

listNamespacedSearchlightPlugin

V1alpha1SearchlightPluginList listNamespacedSearchlightPlugin(namespace, pretty, _continue, fieldSelector, includeUninitialized, labelSelector, limit, resourceVersion, timeoutSeconds, watch)

list or watch objects of kind SearchlightPlugin

Example

// Import classes:
//import com.appscode.searchlight.client.ApiException;
//import com.appscode.searchlight.client.apis.MonitoringAppscodeComV1alpha1Api;


MonitoringAppscodeComV1alpha1Api apiInstance = new MonitoringAppscodeComV1alpha1Api();
String namespace = "namespace_example"; // String | object name and auth scope, such as for teams and projects
String pretty = "pretty_example"; // String | If 'true', then the output is pretty printed.
String _continue = "_continue_example"; // String | The continue option should be set when retrieving more results from the server. Since this value is server defined, clients may only use the continue value from a previous query result with identical query parameters (except for the value of continue) and the server may reject a continue value it does not recognize. If the specified continue value is no longer valid whether due to expiration (generally five to fifteen minutes) or a configuration change on the server the server will respond with a 410 ResourceExpired error indicating the client must restart their list without the continue field. This field is not supported when watch is true. Clients may start a watch from the last resourceVersion value returned by the server and not miss any modifications.
String fieldSelector = "fieldSelector_example"; // String | A selector to restrict the list of returned objects by their fields. Defaults to everything.
Boolean includeUninitialized = true; // Boolean | If true, partially initialized resources are included in the response.
String labelSelector = "labelSelector_example"; // String | A selector to restrict the list of returned objects by their labels. Defaults to everything.
Integer limit = 56; // Integer | limit is a maximum number of responses to return for a list call. If more items exist, the server will set the `continue` field on the list metadata to a value that can be used with the same initial query to retrieve the next set of results. Setting a limit may return fewer than the requested amount of items (up to zero items) in the event all requested objects are filtered out and clients should only use the presence of the continue field to determine whether more results are available. Servers may choose not to support the limit argument and will return all of the available results. If limit is specified and the continue field is empty, clients may assume that no more results are available. This field is not supported if watch is true.  The server guarantees that the objects returned when using continue will be identical to issuing a single list call without a limit - that is, no objects created, modified, or deleted after the first request is issued will be included in any subsequent continued requests. This is sometimes referred to as a consistent snapshot, and ensures that a client that is using limit to receive smaller chunks of a very large result can ensure they see all possible objects. If objects are updated during a chunked list the version of the object that was present at the time the first list result was calculated is returned.
String resourceVersion = "resourceVersion_example"; // String | When specified with a watch call, shows changes that occur after that particular version of a resource. Defaults to changes from the beginning of history. When specified for list: - if unset, then the result is returned from remote storage based on quorum-read flag; - if it's 0, then we simply return what we currently have in cache, no guarantee; - if set to non zero, then the result is at least as fresh as given rv.
Integer timeoutSeconds = 56; // Integer | Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.
Boolean watch = true; // Boolean | Watch for changes to the described resources and return them as a stream of add, update, and remove notifications. Specify resourceVersion.
try {
    V1alpha1SearchlightPluginList result = apiInstance.listNamespacedSearchlightPlugin(namespace, pretty, _continue, fieldSelector, includeUninitialized, labelSelector, limit, resourceVersion, timeoutSeconds, watch);
    System.out.println(result);
} catch (ApiException e) {
    System.err.println("Exception when calling MonitoringAppscodeComV1alpha1Api#listNamespacedSearchlightPlugin");
    e.printStackTrace();
}

Parameters

NameTypeDescriptionNotes
namespaceStringobject name and auth scope, such as for teams and projects
prettyStringIf 'true', then the output is pretty printed.[optional]
_continueStringThe continue option should be set when retrieving more results from the server. Since this value is server defined, clients may only use the continue value from a previous query result with identical query parameters (except for the value of continue) and the server may reject a continue value it does not recognize. If the specified continue value is no longer valid whether due to expiration (generally five to fifteen minutes) or a configuration change on the server the server will respond with a 410 ResourceExpired error indicating the client must restart their list without the continue field. This field is not supported when watch is true. Clients may start a watch from the last resourceVersion value returned by the server and not miss any modifications.[optional]
fieldSelectorStringA selector to restrict the list of returned objects by their fields. Defaults to everything.[optional]
includeUninitializedBooleanIf true, partially initialized resources are included in the response.[optional]
labelSelectorStringA selector to restrict the list of returned objects by their labels. Defaults to everything.[optional]
limitIntegerlimit is a maximum number of responses to return for a list call. If more items exist, the server will set the `continue` field on the list metadata to a value that can be used with the same initial query to retrieve the next set of results. Setting a limit may return fewer than the requested amount of items (up to zero items) in the event all requested objects are filtered out and clients should only use the presence of the continue field to determine whether more results are available. Servers may choose not to support the limit argument and will return all of the available results. If limit is specified and the continue field is empty, clients may assume that no more results are available. This field is not supported if watch is true. The server guarantees that the objects returned when using continue will be identical to issuing a single list call without a limit - that is, no objects created, modified, or deleted after the first request is issued will be included in any subsequent continued requests. This is sometimes referred to as a consistent snapshot, and ensures that a client that is using limit to receive smaller chunks of a very large result can ensure they see all possible objects. If objects are updated during a chunked list the version of the object that was present at the time the first list result was calculated is returned.[optional]
resourceVersionStringWhen specified with a watch call, shows changes that occur after that particular version of a resource. Defaults to changes from the beginning of history. When specified for list: - if unset, then the result is returned from remote storage based on quorum-read flag; - if it's 0, then we simply return what we currently have in cache, no guarantee; - if set to non zero, then the result is at least as fresh as given rv.[optional]
timeoutSecondsIntegerTimeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.[optional]
watchBooleanWatch for changes to the described resources and return them as a stream of add, update, and remove notifications. Specify resourceVersion.[optional]

Return type

V1alpha1SearchlightPluginList

Authorization

No authorization required

HTTP request headers

  • Content-Type: /
  • Accept: application/json, application/yaml, application/vnd.kubernetes.protobuf, application/json;stream=watch, application/vnd.kubernetes.protobuf;stream=watch

listNodeAlertForAllNamespaces

V1alpha1NodeAlertList listNodeAlertForAllNamespaces(_continue, fieldSelector, includeUninitialized, labelSelector, limit, pretty, resourceVersion, timeoutSeconds, watch)

list or watch objects of kind NodeAlert

Example

// Import classes:
//import com.appscode.searchlight.client.ApiException;
//import com.appscode.searchlight.client.apis.MonitoringAppscodeComV1alpha1Api;


MonitoringAppscodeComV1alpha1Api apiInstance = new MonitoringAppscodeComV1alpha1Api();
String _continue = "_continue_example"; // String | The continue option should be set when retrieving more results from the server. Since this value is server defined, clients may only use the continue value from a previous query result with identical query parameters (except for the value of continue) and the server may reject a continue value it does not recognize. If the specified continue value is no longer valid whether due to expiration (generally five to fifteen minutes) or a configuration change on the server the server will respond with a 410 ResourceExpired error indicating the client must restart their list without the continue field. This field is not supported when watch is true. Clients may start a watch from the last resourceVersion value returned by the server and not miss any modifications.
String fieldSelector = "fieldSelector_example"; // String | A selector to restrict the list of returned objects by their fields. Defaults to everything.
Boolean includeUninitialized = true; // Boolean | If true, partially initialized resources are included in the response.
String labelSelector = "labelSelector_example"; // String | A selector to restrict the list of returned objects by their labels. Defaults to everything.
Integer limit = 56; // Integer | limit is a maximum number of responses to return for a list call. If more items exist, the server will set the `continue` field on the list metadata to a value that can be used with the same initial query to retrieve the next set of results. Setting a limit may return fewer than the requested amount of items (up to zero items) in the event all requested objects are filtered out and clients should only use the presence of the continue field to determine whether more results are available. Servers may choose not to support the limit argument and will return all of the available results. If limit is specified and the continue field is empty, clients may assume that no more results are available. This field is not supported if watch is true.  The server guarantees that the objects returned when using continue will be identical to issuing a single list call without a limit - that is, no objects created, modified, or deleted after the first request is issued will be included in any subsequent continued requests. This is sometimes referred to as a consistent snapshot, and ensures that a client that is using limit to receive smaller chunks of a very large result can ensure they see all possible objects. If objects are updated during a chunked list the version of the object that was present at the time the first list result was calculated is returned.
String pretty = "pretty_example"; // String | If 'true', then the output is pretty printed.
String resourceVersion = "resourceVersion_example"; // String | When specified with a watch call, shows changes that occur after that particular version of a resource. Defaults to changes from the beginning of history. When specified for list: - if unset, then the result is returned from remote storage based on quorum-read flag; - if it's 0, then we simply return what we currently have in cache, no guarantee; - if set to non zero, then the result is at least as fresh as given rv.
Integer timeoutSeconds = 56; // Integer | Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.
Boolean watch = true; // Boolean | Watch for changes to the described resources and return them as a stream of add, update, and remove notifications. Specify resourceVersion.
try {
    V1alpha1NodeAlertList result = apiInstance.listNodeAlertForAllNamespaces(_continue, fieldSelector, includeUninitialized, labelSelector, limit, pretty, resourceVersion, timeoutSeconds, watch);
    System.out.println(result);
} catch (ApiException e) {
    System.err.println("Exception when calling MonitoringAppscodeComV1alpha1Api#listNodeAlertForAllNamespaces");
    e.printStackTrace();
}

Parameters

NameTypeDescriptionNotes
_continueStringThe continue option should be set when retrieving more results from the server. Since this value is server defined, clients may only use the continue value from a previous query result with identical query parameters (except for the value of continue) and the server may reject a continue value it does not recognize. If the specified continue value is no longer valid whether due to expiration (generally five to fifteen minutes) or a configuration change on the server the server will respond with a 410 ResourceExpired error indicating the client must restart their list without the continue field. This field is not supported when watch is true. Clients may start a watch from the last resourceVersion value returned by the server and not miss any modifications.[optional]
fieldSelectorStringA selector to restrict the list of returned objects by their fields. Defaults to everything.[optional]
includeUninitializedBooleanIf true, partially initialized resources are included in the response.[optional]
labelSelectorStringA selector to restrict the list of returned objects by their labels. Defaults to everything.[optional]
limitIntegerlimit is a maximum number of responses to return for a list call. If more items exist, the server will set the `continue` field on the list metadata to a value that can be used with the same initial query to retrieve the next set of results. Setting a limit may return fewer than the requested amount of items (up to zero items) in the event all requested objects are filtered out and clients should only use the presence of the continue field to determine whether more results are available. Servers may choose not to support the limit argument and will return all of the available results. If limit is specified and the continue field is empty, clients may assume that no more results are available. This field is not supported if watch is true. The server guarantees that the objects returned when using continue will be identical to issuing a single list call without a limit - that is, no objects created, modified, or deleted after the first request is issued will be included in any subsequent continued requests. This is sometimes referred to as a consistent snapshot, and ensures that a client that is using limit to receive smaller chunks of a very large result can ensure they see all possible objects. If objects are updated during a chunked list the version of the object that was present at the time the first list result was calculated is returned.[optional]
prettyStringIf 'true', then the output is pretty printed.[optional]
resourceVersionStringWhen specified with a watch call, shows changes that occur after that particular version of a resource. Defaults to changes from the beginning of history. When specified for list: - if unset, then the result is returned from remote storage based on quorum-read flag; - if it's 0, then we simply return what we currently have in cache, no guarantee; - if set to non zero, then the result is at least as fresh as given rv.[optional]
timeoutSecondsIntegerTimeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.[optional]
watchBooleanWatch for changes to the described resources and return them as a stream of add, update, and remove notifications. Specify resourceVersion.[optional]

Return type

V1alpha1NodeAlertList

Authorization

No authorization required

HTTP request headers

  • Content-Type: /
  • Accept: application/json, application/yaml, application/vnd.kubernetes.protobuf, application/json;stream=watch, application/vnd.kubernetes.protobuf;stream=watch

listPodAlertForAllNamespaces

V1alpha1PodAlertList listPodAlertForAllNamespaces(_continue, fieldSelector, includeUninitialized, labelSelector, limit, pretty, resourceVersion, timeoutSeconds, watch)

list or watch objects of kind PodAlert

Example

// Import classes:
//import com.appscode.searchlight.client.ApiException;
//import com.appscode.searchlight.client.apis.MonitoringAppscodeComV1alpha1Api;


MonitoringAppscodeComV1alpha1Api apiInstance = new MonitoringAppscodeComV1alpha1Api();
String _continue = "_continue_example"; // String | The continue option should be set when retrieving more results from the server. Since this value is server defined, clients may only use the continue value from a previous query result with identical query parameters (except for the value of continue) and the server may reject a continue value it does not recognize. If the specified continue value is no longer valid whether due to expiration (generally five to fifteen minutes) or a configuration change on the server the server will respond with a 410 ResourceExpired error indicating the client must restart their list without the continue field. This field is not supported when watch is true. Clients may start a watch from the last resourceVersion value returned by the server and not miss any modifications.
String fieldSelector = "fieldSelector_example"; // String | A selector to restrict the list of returned objects by their fields. Defaults to everything.
Boolean includeUninitialized = true; // Boolean | If true, partially initialized resources are included in the response.
String labelSelector = "labelSelector_example"; // String | A selector to restrict the list of returned objects by their labels. Defaults to everything.
Integer limit = 56; // Integer | limit is a maximum number of responses to return for a list call. If more items exist, the server will set the `continue` field on the list metadata to a value that can be used with the same initial query to retrieve the next set of results. Setting a limit may return fewer than the requested amount of items (up to zero items) in the event all requested objects are filtered out and clients should only use the presence of the continue field to determine whether more results are available. Servers may choose not to support the limit argument and will return all of the available results. If limit is specified and the continue field is empty, clients may assume that no more results are available. This field is not supported if watch is true.  The server guarantees that the objects returned when using continue will be identical to issuing a single list call without a limit - that is, no objects created, modified, or deleted after the first request is issued will be included in any subsequent continued requests. This is sometimes referred to as a consistent snapshot, and ensures that a client that is using limit to receive smaller chunks of a very large result can ensure they see all possible objects. If objects are updated during a chunked list the version of the object that was present at the time the first list result was calculated is returned.
String pretty = "pretty_example"; // String | If 'true', then the output is pretty printed.
String resourceVersion = "resourceVersion_example"; // String | When specified with a watch call, shows changes that occur after that particular version of a resource. Defaults to changes from the beginning of history. When specified for list: - if unset, then the result is returned from remote storage based on quorum-read flag; - if it's 0, then we simply return what we currently have in cache, no guarantee; - if set to non zero, then the result is at least as fresh as given rv.
Integer timeoutSeconds = 56; // Integer | Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.
Boolean watch = true; // Boolean | Watch for changes to the described resources and return them as a stream of add, update, and remove notifications. Specify resourceVersion.
try {
    V1alpha1PodAlertList result = apiInstance.listPodAlertForAllNamespaces(_continue, fieldSelector, includeUninitialized, labelSelector, limit, pretty, resourceVersion, timeoutSeconds, watch);
    System.out.println(result);
} catch (ApiException e) {
    System.err.println("Exception when calling MonitoringAppscodeComV1alpha1Api#listPodAlertForAllNamespaces");
    e.printStackTrace();
}

Parameters

NameTypeDescriptionNotes
_continueStringThe continue option should be set when retrieving more results from the server. Since this value is server defined, clients may only use the continue value from a previous query result with identical query parameters (except for the value of continue) and the server may reject a continue value it does not recognize. If the specified continue value is no longer valid whether due to expiration (generally five to fifteen minutes) or a configuration change on the server the server will respond with a 410 ResourceExpired error indicating the client must restart their list without the continue field. This field is not supported when watch is true. Clients may start a watch from the last resourceVersion value returned by the server and not miss any modifications.[optional]
fieldSelectorStringA selector to restrict the list of returned objects by their fields. Defaults to everything.[optional]
includeUninitializedBooleanIf true, partially initialized resources are included in the response.[optional]
labelSelectorStringA selector to restrict the list of returned objects by their labels. Defaults to everything.[optional]
limitIntegerlimit is a maximum number of responses to return for a list call. If more items exist, the server will set the `continue` field on the list metadata to a value that can be used with the same initial query to retrieve the next set of results. Setting a limit may return fewer than the requested amount of items (up to zero items) in the event all requested objects are filtered out and clients should only use the presence of the continue field to determine whether more results are available. Servers may choose not to support the limit argument and will return all of the available results. If limit is specified and the continue field is empty, clients may assume that no more results are available. This field is not supported if watch is true. The server guarantees that the objects returned when using continue will be identical to issuing a single list call without a limit - that is, no objects created, modified, or deleted after the first request is issued will be included in any subsequent continued requests. This is sometimes referred to as a consistent snapshot, and ensures that a client that is using limit to receive smaller chunks of a very large result can ensure they see all possible objects. If objects are updated during a chunked list the version of the object that was present at the time the first list result was calculated is returned.[optional]
prettyStringIf 'true', then the output is pretty printed.[optional]
resourceVersionStringWhen specified with a watch call, shows changes that occur after that particular version of a resource. Defaults to changes from the beginning of history. When specified for list: - if unset, then the result is returned from remote storage based on quorum-read flag; - if it's 0, then we simply return what we currently have in cache, no guarantee; - if set to non zero, then the result is at least as fresh as given rv.[optional]
timeoutSecondsIntegerTimeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.[optional]
watchBooleanWatch for changes to the described resources and return them as a stream of add, update, and remove notifications. Specify resourceVersion.[optional]

Return type

V1alpha1PodAlertList

Authorization

No authorization required

HTTP request headers

  • Content-Type: /
  • Accept: application/json, application/yaml, application/vnd.kubernetes.protobuf, application/json;stream=watch, application/vnd.kubernetes.protobuf;stream=watch

listSearchlightPluginForAllNamespaces

V1alpha1SearchlightPluginList listSearchlightPluginForAllNamespaces(_continue, fieldSelector, includeUninitialized, labelSelector, limit, pretty, resourceVersion, timeoutSeconds, watch)

list or watch objects of kind SearchlightPlugin

Example

// Import classes:
//import com.appscode.searchlight.client.ApiException;
//import com.appscode.searchlight.client.apis.MonitoringAppscodeComV1alpha1Api;


MonitoringAppscodeComV1alpha1Api apiInstance = new MonitoringAppscodeComV1alpha1Api();
String _continue = "_continue_example"; // String | The continue option should be set when retrieving more results from the server. Since this value is server defined, clients may only use the continue value from a previous query result with identical query parameters (except for the value of continue) and the server may reject a continue value it does not recognize. If the specified continue value is no longer valid whether due to expiration (generally five to fifteen minutes) or a configuration change on the server the server will respond with a 410 ResourceExpired error indicating the client must restart their list without the continue field. This field is not supported when watch is true. Clients may start a watch from the last resourceVersion value returned by the server and not miss any modifications.
String fieldSelector = "fieldSelector_example"; // String | A selector to restrict the list of returned objects by their fields. Defaults to everything.
Boolean includeUninitialized = true; // Boolean | If true, partially initialized resources are included in the response.
String labelSelector = "labelSelector_example"; // String | A selector to restrict the list of returned objects by their labels. Defaults to everything.
Integer limit = 56; // Integer | limit is a maximum number of responses to return for a list call. If more items exist, the server will set the `continue` field on the list metadata to a value that can be used with the same initial query to retrieve the next set of results. Setting a limit may return fewer than the requested amount of items (up to zero items) in the event all requested objects are filtered out and clients should only use the presence of the continue field to determine whether more results are available. Servers may choose not to support the limit argument and will return all of the available results. If limit is specified and the continue field is empty, clients may assume that no more results are available. This field is not supported if watch is true.  The server guarantees that the objects returned when using continue will be identical to issuing a single list call without a limit - that is, no objects created, modified, or deleted after the first request is issued will be included in any subsequent continued requests. This is sometimes referred to as a consistent snapshot, and ensures that a client that is using limit to receive smaller chunks of a very large result can ensure they see all possible objects. If objects are updated during a chunked list the version of the object that was present at the time the first list result was calculated is returned.
String pretty = "pretty_example"; // String | If 'true', then the output is pretty printed.
String resourceVersion = "resourceVersion_example"; // String | When specified with a watch call, shows changes that occur after that particular version of a resource. Defaults to changes from the beginning of history. When specified for list: - if unset, then the result is returned from remote storage based on quorum-read flag; - if it's 0, then we simply return what we currently have in cache, no guarantee; - if set to non zero, then the result is at least as fresh as given rv.
Integer timeoutSeconds = 56; // Integer | Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.
Boolean watch = true; // Boolean | Watch for changes to the described resources and return them as a stream of add, update, and remove notifications. Specify resourceVersion.
try {
    V1alpha1SearchlightPluginList result = apiInstance.listSearchlightPluginForAllNamespaces(_continue, fieldSelector, includeUninitialized, labelSelector, limit, pretty, resourceVersion, timeoutSeconds, watch);
    System.out.println(result);
} catch (ApiException e) {
    System.err.println("Exception when calling MonitoringAppscodeComV1alpha1Api#listSearchlightPluginForAllNamespaces");
    e.printStackTrace();
}

Parameters

NameTypeDescriptionNotes
_continueStringThe continue option should be set when retrieving more results from the server. Since this value is server defined, clients may only use the continue value from a previous query result with identical query parameters (except for the value of continue) and the server may reject a continue value it does not recognize. If the specified continue value is no longer valid whether due to expiration (generally five to fifteen minutes) or a configuration change on the server the server will respond with a 410 ResourceExpired error indicating the client must restart their list without the continue field. This field is not supported when watch is true. Clients may start a watch from the last resourceVersion value returned by the server and not miss any modifications.[optional]
fieldSelectorStringA selector to restrict the list of returned objects by their fields. Defaults to everything.[optional]
includeUninitializedBooleanIf true, partially initialized resources are included in the response.[optional]
labelSelectorStringA selector to restrict the list of returned objects by their labels. Defaults to everything.[optional]
limitIntegerlimit is a maximum number of responses to return for a list call. If more items exist, the server will set the `continue` field on the list metadata to a value that can be used with the same initial query to retrieve the next set of results. Setting a limit may return fewer than the requested amount of items (up to zero items) in the event all requested objects are filtered out and clients should only use the presence of the continue field to determine whether more results are available. Servers may choose not to support the limit argument and will return all of the available results. If limit is specified and the continue field is empty, clients may assume that no more results are available. This field is not supported if watch is true. The server guarantees that the objects returned when using continue will be identical to issuing a single list call without a limit - that is, no objects created, modified, or deleted after the first request is issued will be included in any subsequent continued requests. This is sometimes referred to as a consistent snapshot, and ensures that a client that is using limit to receive smaller chunks of a very large result can ensure they see all possible objects. If objects are updated during a chunked list the version of the object that was present at the time the first list result was calculated is returned.[optional]
prettyStringIf 'true', then the output is pretty printed.[optional]
resourceVersionStringWhen specified with a watch call, shows changes that occur after that particular version of a resource. Defaults to changes from the beginning of history. When specified for list: - if unset, then the result is returned from remote storage based on quorum-read flag; - if it's 0, then we simply return what we currently have in cache, no guarantee; - if set to non zero, then the result is at least as fresh as given rv.[optional]
timeoutSecondsIntegerTimeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.[optional]
watchBooleanWatch for changes to the described resources and return them as a stream of add, update, and remove notifications. Specify resourceVersion.[optional]

Return type

V1alpha1SearchlightPluginList

Authorization

No authorization required

HTTP request headers

  • Content-Type: /
  • Accept: application/json, application/yaml, application/vnd.kubernetes.protobuf, application/json;stream=watch, application/vnd.kubernetes.protobuf;stream=watch

patchNamespacedClusterAlert

V1alpha1ClusterAlert patchNamespacedClusterAlert(name, namespace, body, pretty)

partially update the specified ClusterAlert

Example

// Import classes:
//import com.appscode.searchlight.client.ApiException;
//import com.appscode.searchlight.client.apis.MonitoringAppscodeComV1alpha1Api;


MonitoringAppscodeComV1alpha1Api apiInstance = new MonitoringAppscodeComV1alpha1Api();
String name = "name_example"; // String | name of the ClusterAlert
String namespace = "namespace_example"; // String | object name and auth scope, such as for teams and projects
Object body = null; // Object | 
String pretty = "pretty_example"; // String | If 'true', then the output is pretty printed.
try {
    V1alpha1ClusterAlert result = apiInstance.patchNamespacedClusterAlert(name, namespace, body, pretty);
    System.out.println(result);
} catch (ApiException e) {
    System.err.println("Exception when calling MonitoringAppscodeComV1alpha1Api#patchNamespacedClusterAlert");
    e.printStackTrace();
}

Parameters

NameTypeDescriptionNotes
nameStringname of the ClusterAlert
namespaceStringobject name and auth scope, such as for teams and projects
bodyObject
prettyStringIf 'true', then the output is pretty printed.[optional]

Return type

V1alpha1ClusterAlert

Authorization

No authorization required

HTTP request headers

  • Content-Type: application/json-patch+json, application/merge-patch+json, application/strategic-merge-patch+json
  • Accept: application/json, application/yaml, application/vnd.kubernetes.protobuf

patchNamespacedIncident

V1alpha1Incident patchNamespacedIncident(name, namespace, body, pretty)

partially update the specified Incident

Example

// Import classes:
//import com.appscode.searchlight.client.ApiException;
//import com.appscode.searchlight.client.apis.MonitoringAppscodeComV1alpha1Api;


MonitoringAppscodeComV1alpha1Api apiInstance = new MonitoringAppscodeComV1alpha1Api();
String name = "name_example"; // String | name of the Incident
String namespace = "namespace_example"; // String | object name and auth scope, such as for teams and projects
Object body = null; // Object | 
String pretty = "pretty_example"; // String | If 'true', then the output is pretty printed.
try {
    V1alpha1Incident result = apiInstance.patchNamespacedIncident(name, namespace, body, pretty);
    System.out.println(result);
} catch (ApiException e) {
    System.err.println("Exception when calling MonitoringAppscodeComV1alpha1Api#patchNamespacedIncident");
    e.printStackTrace();
}

Parameters

NameTypeDescriptionNotes
nameStringname of the Incident
namespaceStringobject name and auth scope, such as for teams and projects
bodyObject
prettyStringIf 'true', then the output is pretty printed.[optional]

Return type

V1alpha1Incident

Authorization

No authorization required

HTTP request headers

  • Content-Type: application/json-patch+json, application/merge-patch+json, application/strategic-merge-patch+json
  • Accept: application/json, application/yaml, application/vnd.kubernetes.protobuf

patchNamespacedNodeAlert

V1alpha1NodeAlert patchNamespacedNodeAlert(name, namespace, body, pretty)

partially update the specified NodeAlert

Example

// Import classes:
//import com.appscode.searchlight.client.ApiException;
//import com.appscode.searchlight.client.apis.MonitoringAppscodeComV1alpha1Api;


MonitoringAppscodeComV1alpha1Api apiInstance = new MonitoringAppscodeComV1alpha1Api();
String name = "name_example"; // String | name of the NodeAlert
String namespace = "namespace_example"; // String | object name and auth scope, such as for teams and projects
Object body = null; // Object | 
String pretty = "pretty_example"; // String | If 'true', then the output is pretty printed.
try {
    V1alpha1NodeAlert result = apiInstance.patchNamespacedNodeAlert(name, namespace, body, pretty);
    System.out.println(result);
} catch (ApiException e) {
    System.err.println("Exception when calling MonitoringAppscodeComV1alpha1Api#patchNamespacedNodeAlert");
    e.printStackTrace();
}

Parameters

NameTypeDescriptionNotes
nameStringname of the NodeAlert
namespaceStringobject name and auth scope, such as for teams and projects
bodyObject
prettyStringIf 'true', then the output is pretty printed.[optional]

Return type

V1alpha1NodeAlert

Authorization

No authorization required

HTTP request headers

  • Content-Type: application/json-patch+json, application/merge-patch+json, application/strategic-merge-patch+json
  • Accept: application/json, application/yaml, application/vnd.kubernetes.protobuf

patchNamespacedPodAlert

V1alpha1PodAlert patchNamespacedPodAlert(name, namespace, body, pretty)

partially update the specified PodAlert

Example

// Import classes:
//import com.appscode.searchlight.client.ApiException;
//import com.appscode.searchlight.client.apis.MonitoringAppscodeComV1alpha1Api;


MonitoringAppscodeComV1alpha1Api apiInstance = new MonitoringAppscodeComV1alpha1Api();
String name = "name_example"; // String | name of the PodAlert
String namespace = "namespace_example"; // String | object name and auth scope, such as for teams and projects
Object body = null; // Object | 
String pretty = "pretty_example"; // String | If 'true', then the output is pretty printed.
try {
    V1alpha1PodAlert result = apiInstance.patchNamespacedPodAlert(name, namespace, body, pretty);
    System.out.println(result);
} catch (ApiException e) {
    System.err.println("Exception when calling MonitoringAppscodeComV1alpha1Api#patchNamespacedPodAlert");
    e.printStackTrace();
}

Parameters

NameTypeDescriptionNotes
nameStringname of the PodAlert
namespaceStringobject name and auth scope, such as for teams and projects
bodyObject
prettyStringIf 'true', then the output is pretty printed.[optional]

Return type

V1alpha1PodAlert

Authorization

No authorization required

HTTP request headers

  • Content-Type: application/json-patch+json, application/merge-patch+json, application/strategic-merge-patch+json
  • Accept: application/json, application/yaml, application/vnd.kubernetes.protobuf

patchNamespacedSearchlightPlugin

V1alpha1SearchlightPlugin patchNamespacedSearchlightPlugin(name, namespace, body, pretty)

partially update the specified SearchlightPlugin

Example

// Import classes:
//import com.appscode.searchlight.client.ApiException;
//import com.appscode.searchlight.client.apis.MonitoringAppscodeComV1alpha1Api;


MonitoringAppscodeComV1alpha1Api apiInstance = new MonitoringAppscodeComV1alpha1Api();
String name = "name_example"; // String | name of the SearchlightPlugin
String namespace = "namespace_example"; // String | object name and auth scope, such as for teams and projects
Object body = null; // Object | 
String pretty = "pretty_example"; // String | If 'true', then the output is pretty printed.
try {
    V1alpha1SearchlightPlugin result = apiInstance.patchNamespacedSearchlightPlugin(name, namespace, body, pretty);
    System.out.println(result);
} catch (ApiException e) {
    System.err.println("Exception when calling MonitoringAppscodeComV1alpha1Api#patchNamespacedSearchlightPlugin");
    e.printStackTrace();
}

Parameters

NameTypeDescriptionNotes
nameStringname of the SearchlightPlugin
namespaceStringobject name and auth scope, such as for teams and projects
bodyObject
prettyStringIf 'true', then the output is pretty printed.[optional]

Return type

V1alpha1SearchlightPlugin

Authorization

No authorization required

HTTP request headers

  • Content-Type: application/json-patch+json, application/merge-patch+json, application/strategic-merge-patch+json
  • Accept: application/json, application/yaml, application/vnd.kubernetes.protobuf

readNamespacedClusterAlert

V1alpha1ClusterAlert readNamespacedClusterAlert(name, namespace, pretty)

read the specified ClusterAlert

Example

// Import classes:
//import com.appscode.searchlight.client.ApiException;
//import com.appscode.searchlight.client.apis.MonitoringAppscodeComV1alpha1Api;


MonitoringAppscodeComV1alpha1Api apiInstance = new MonitoringAppscodeComV1alpha1Api();
String name = "name_example"; // String | name of the ClusterAlert
String namespace = "namespace_example"; // String | object name and auth scope, such as for teams and projects
String pretty = "pretty_example"; // String | If 'true', then the output is pretty printed.
try {
    V1alpha1ClusterAlert result = apiInstance.readNamespacedClusterAlert(name, namespace, pretty);
    System.out.println(result);
} catch (ApiException e) {
    System.err.println("Exception when calling MonitoringAppscodeComV1alpha1Api#readNamespacedClusterAlert");
    e.printStackTrace();
}

Parameters

NameTypeDescriptionNotes
nameStringname of the ClusterAlert
namespaceStringobject name and auth scope, such as for teams and projects
prettyStringIf 'true', then the output is pretty printed.[optional]

Return type

V1alpha1ClusterAlert

Authorization

No authorization required

HTTP request headers

  • Content-Type: /
  • Accept: application/json, application/yaml, application/vnd.kubernetes.protobuf

readNamespacedIncident

V1alpha1Incident readNamespacedIncident(name, namespace, pretty)

read the specified Incident

Example

// Import classes:
//import com.appscode.searchlight.client.ApiException;
//import com.appscode.searchlight.client.apis.MonitoringAppscodeComV1alpha1Api;


MonitoringAppscodeComV1alpha1Api apiInstance = new MonitoringAppscodeComV1alpha1Api();
String name = "name_example"; // String | name of the Incident
String namespace = "namespace_example"; // String | object name and auth scope, such as for teams and projects
String pretty = "pretty_example"; // String | If 'true', then the output is pretty printed.
try {
    V1alpha1Incident result = apiInstance.readNamespacedIncident(name, namespace, pretty);
    System.out.println(result);
} catch (ApiException e) {
    System.err.println("Exception when calling MonitoringAppscodeComV1alpha1Api#readNamespacedIncident");
    e.printStackTrace();
}

Parameters

NameTypeDescriptionNotes
nameStringname of the Incident
namespaceStringobject name and auth scope, such as for teams and projects
prettyStringIf 'true', then the output is pretty printed.[optional]

Return type

V1alpha1Incident

Authorization

No authorization required

HTTP request headers

  • Content-Type: /
  • Accept: application/json, application/yaml, application/vnd.kubernetes.protobuf

readNamespacedNodeAlert

V1alpha1NodeAlert readNamespacedNodeAlert(name, namespace, pretty)

read the specified NodeAlert

Example

// Import classes:
//import com.appscode.searchlight.client.ApiException;
//import com.appscode.searchlight.client.apis.MonitoringAppscodeComV1alpha1Api;


MonitoringAppscodeComV1alpha1Api apiInstance = new MonitoringAppscodeComV1alpha1Api();
String name = "name_example"; // String | name of the NodeAlert
String namespace = "namespace_example"; // String | object name and auth scope, such as for teams and projects
String pretty = "pretty_example"; // String | If 'true', then the output is pretty printed.
try {
    V1alpha1NodeAlert result = apiInstance.readNamespacedNodeAlert(name, namespace, pretty);
    System.out.println(result);
} catch (ApiException e) {
    System.err.println("Exception when calling MonitoringAppscodeComV1alpha1Api#readNamespacedNodeAlert");
    e.printStackTrace();
}

Parameters

NameTypeDescriptionNotes
nameStringname of the NodeAlert
namespaceStringobject name and auth scope, such as for teams and projects
prettyStringIf 'true', then the output is pretty printed.[optional]

Return type

V1alpha1NodeAlert

Authorization

No authorization required

HTTP request headers

  • Content-Type: /
  • Accept: application/json, application/yaml, application/vnd.kubernetes.protobuf

readNamespacedPodAlert

V1alpha1PodAlert readNamespacedPodAlert(name, namespace, pretty)

read the specified PodAlert

Example

// Import classes:
//import com.appscode.searchlight.client.ApiException;
//import com.appscode.searchlight.client.apis.MonitoringAppscodeComV1alpha1Api;


MonitoringAppscodeComV1alpha1Api apiInstance = new MonitoringAppscodeComV1alpha1Api();
String name = "name_example"; // String | name of the PodAlert
String namespace = "namespace_example"; // String | object name and auth scope, such as for teams and projects
String pretty = "pretty_example"; // String | If 'true', then the output is pretty printed.
try {
    V1alpha1PodAlert result = apiInstance.readNamespacedPodAlert(name, namespace, pretty);
    System.out.println(result);
} catch (ApiException e) {
    System.err.println("Exception when calling MonitoringAppscodeComV1alpha1Api#readNamespacedPodAlert");
    e.printStackTrace();
}

Parameters

NameTypeDescriptionNotes
nameStringname of the PodAlert
namespaceStringobject name and auth scope, such as for teams and projects
prettyStringIf 'true', then the output is pretty printed.[optional]

Return type

V1alpha1PodAlert

Authorization

No authorization required

HTTP request headers

  • Content-Type: /
  • Accept: application/json, application/yaml, application/vnd.kubernetes.protobuf

readNamespacedSearchlightPlugin

V1alpha1SearchlightPlugin readNamespacedSearchlightPlugin(name, namespace, pretty)

read the specified SearchlightPlugin

Example

// Import classes:
//import com.appscode.searchlight.client.ApiException;
//import com.appscode.searchlight.client.apis.MonitoringAppscodeComV1alpha1Api;


MonitoringAppscodeComV1alpha1Api apiInstance = new MonitoringAppscodeComV1alpha1Api();
String name = "name_example"; // String | name of the SearchlightPlugin
String namespace = "namespace_example"; // String | object name and auth scope, such as for teams and projects
String pretty = "pretty_example"; // String | If 'true', then the output is pretty printed.
try {
    V1alpha1SearchlightPlugin result = apiInstance.readNamespacedSearchlightPlugin(name, namespace, pretty);
    System.out.println(result);
} catch (ApiException e) {
    System.err.println("Exception when calling MonitoringAppscodeComV1alpha1Api#readNamespacedSearchlightPlugin");
    e.printStackTrace();
}

Parameters

NameTypeDescriptionNotes
nameStringname of the SearchlightPlugin
namespaceStringobject name and auth scope, such as for teams and projects
prettyStringIf 'true', then the output is pretty printed.[optional]

Return type

V1alpha1SearchlightPlugin

Authorization

No authorization required

HTTP request headers

  • Content-Type: /
  • Accept: application/json, application/yaml, application/vnd.kubernetes.protobuf

replaceNamespacedClusterAlert

V1alpha1ClusterAlert replaceNamespacedClusterAlert(name, namespace, body, pretty)

replace the specified ClusterAlert

Example

// Import classes:
//import com.appscode.searchlight.client.ApiException;
//import com.appscode.searchlight.client.apis.MonitoringAppscodeComV1alpha1Api;


MonitoringAppscodeComV1alpha1Api apiInstance = new MonitoringAppscodeComV1alpha1Api();
String name = "name_example"; // String | name of the ClusterAlert
String namespace = "namespace_example"; // String | object name and auth scope, such as for teams and projects
V1alpha1ClusterAlert body = new V1alpha1ClusterAlert(); // V1alpha1ClusterAlert | 
String pretty = "pretty_example"; // String | If 'true', then the output is pretty printed.
try {
    V1alpha1ClusterAlert result = apiInstance.replaceNamespacedClusterAlert(name, namespace, body, pretty);
    System.out.println(result);
} catch (ApiException e) {
    System.err.println("Exception when calling MonitoringAppscodeComV1alpha1Api#replaceNamespacedClusterAlert");
    e.printStackTrace();
}

Parameters

NameTypeDescriptionNotes
nameStringname of the ClusterAlert
namespaceStringobject name and auth scope, such as for teams and projects
bodyV1alpha1ClusterAlert
prettyStringIf 'true', then the output is pretty printed.[optional]

Return type

V1alpha1ClusterAlert

Authorization

No authorization required

HTTP request headers

  • Content-Type: /
  • Accept: application/json, application/yaml, application/vnd.kubernetes.protobuf

replaceNamespacedIncident

V1alpha1Incident replaceNamespacedIncident(name, namespace, body, pretty)

replace the specified Incident

Example

// Import classes:
//import com.appscode.searchlight.client.ApiException;
//import com.appscode.searchlight.client.apis.MonitoringAppscodeComV1alpha1Api;


MonitoringAppscodeComV1alpha1Api apiInstance = new MonitoringAppscodeComV1alpha1Api();
String name = "name_example"; // String | name of the Incident
String namespace = "namespace_example"; // String | object name and auth scope, such as for teams and projects
V1alpha1Incident body = new V1alpha1Incident(); // V1alpha1Incident | 
String pretty = "pretty_example"; // String | If 'true', then the output is pretty printed.
try {
    V1alpha1Incident result = apiInstance.replaceNamespacedIncident(name, namespace, body, pretty);
    System.out.println(result);
} catch (ApiException e) {
    System.err.println("Exception when calling MonitoringAppscodeComV1alpha1Api#replaceNamespacedIncident");
    e.printStackTrace();
}

Parameters

NameTypeDescriptionNotes
nameStringname of the Incident
namespaceStringobject name and auth scope, such as for teams and projects
bodyV1alpha1Incident
prettyStringIf 'true', then the output is pretty printed.[optional]

Return type

V1alpha1Incident

Authorization

No authorization required

HTTP request headers

  • Content-Type: /
  • Accept: application/json, application/yaml, application/vnd.kubernetes.protobuf

replaceNamespacedNodeAlert

V1alpha1NodeAlert replaceNamespacedNodeAlert(name, namespace, body, pretty)

replace the specified NodeAlert

Example

// Import classes:
//import com.appscode.searchlight.client.ApiException;
//import com.appscode.searchlight.client.apis.MonitoringAppscodeComV1alpha1Api;


MonitoringAppscodeComV1alpha1Api apiInstance = new MonitoringAppscodeComV1alpha1Api();
String name = "name_example"; // String | name of the NodeAlert
String namespace = "namespace_example"; // String | object name and auth scope, such as for teams and projects
V1alpha1NodeAlert body = new V1alpha1NodeAlert(); // V1alpha1NodeAlert | 
String pretty = "pretty_example"; // String | If 'true', then the output is pretty printed.
try {
    V1alpha1NodeAlert result = apiInstance.replaceNamespacedNodeAlert(name, namespace, body, pretty);
    System.out.println(result);
} catch (ApiException e) {
    System.err.println("Exception when calling MonitoringAppscodeComV1alpha1Api#replaceNamespacedNodeAlert");
    e.printStackTrace();
}

Parameters

NameTypeDescriptionNotes
nameStringname of the NodeAlert
namespaceStringobject name and auth scope, such as for teams and projects
bodyV1alpha1NodeAlert
prettyStringIf 'true', then the output is pretty printed.[optional]

Return type

V1alpha1NodeAlert

Authorization

No authorization required

HTTP request headers

  • Content-Type: /
  • Accept: application/json, application/yaml, application/vnd.kubernetes.protobuf

replaceNamespacedPodAlert

V1alpha1PodAlert replaceNamespacedPodAlert(name, namespace, body, pretty)

replace the specified PodAlert

Example

// Import classes:
//import com.appscode.searchlight.client.ApiException;
//import com.appscode.searchlight.client.apis.MonitoringAppscodeComV1alpha1Api;


MonitoringAppscodeComV1alpha1Api apiInstance = new MonitoringAppscodeComV1alpha1Api();
String name = "name_example"; // String | name of the PodAlert
String namespace = "namespace_example"; // String | object name and auth scope, such as for teams and projects
V1alpha1PodAlert body = new V1alpha1PodAlert(); // V1alpha1PodAlert | 
String pretty = "pretty_example"; // String | If 'true', then the output is pretty printed.
try {
    V1alpha1PodAlert result = apiInstance.replaceNamespacedPodAlert(name, namespace, body, pretty);
    System.out.println(result);
} catch (ApiException e) {
    System.err.println("Exception when calling MonitoringAppscodeComV1alpha1Api#replaceNamespacedPodAlert");
    e.printStackTrace();
}

Parameters

NameTypeDescriptionNotes
nameStringname of the PodAlert
namespaceStringobject name and auth scope, such as for teams and projects
bodyV1alpha1PodAlert
prettyStringIf 'true', then the output is pretty printed.[optional]

Return type

V1alpha1PodAlert

Authorization

No authorization required

HTTP request headers

  • Content-Type: /
  • Accept: application/json, application/yaml, application/vnd.kubernetes.protobuf

replaceNamespacedSearchlightPlugin

V1alpha1SearchlightPlugin replaceNamespacedSearchlightPlugin(name, namespace, body, pretty)

replace the specified SearchlightPlugin

Example

// Import classes:
//import com.appscode.searchlight.client.ApiException;
//import com.appscode.searchlight.client.apis.MonitoringAppscodeComV1alpha1Api;


MonitoringAppscodeComV1alpha1Api apiInstance = new MonitoringAppscodeComV1alpha1Api();
String name = "name_example"; // String | name of the SearchlightPlugin
String namespace = "namespace_example"; // String | object name and auth scope, such as for teams and projects
V1alpha1SearchlightPlugin body = new V1alpha1SearchlightPlugin(); // V1alpha1SearchlightPlugin | 
String pretty = "pretty_example"; // String | If 'true', then the output is pretty printed.
try {
    V1alpha1SearchlightPlugin result = apiInstance.replaceNamespacedSearchlightPlugin(name, namespace, body, pretty);
    System.out.println(result);
} catch (ApiException e) {
    System.err.println("Exception when calling MonitoringAppscodeComV1alpha1Api#replaceNamespacedSearchlightPlugin");
    e.printStackTrace();
}

Parameters

NameTypeDescriptionNotes
nameStringname of the SearchlightPlugin
namespaceStringobject name and auth scope, such as for teams and projects
bodyV1alpha1SearchlightPlugin
prettyStringIf 'true', then the output is pretty printed.[optional]

Return type

V1alpha1SearchlightPlugin

Authorization

No authorization required

HTTP request headers

  • Content-Type: /
  • Accept: application/json, application/yaml, application/vnd.kubernetes.protobuf