public static final class SearchSignalsRequest.Builder extends GeneratedMessageV3.Builder<SearchSignalsRequest.Builder> implements SearchSignalsRequestOrBuilder
Request for the SearchSignals method.Protobuf type
google.cloud.irm.v1alpha2.SearchSignalsRequestgetAllFields, getField, getFieldBuilder, getOneofFieldDescriptor, getParentForChildren, getRepeatedField, getRepeatedFieldBuilder, getRepeatedFieldCount, getUnknownFields, hasField, hasOneof, internalGetMapField, internalGetMutableMapField, isClean, markClean, newBuilderForField, onBuilt, onChanged, setUnknownFieldsProto3findInitializationErrors, getInitializationErrorString, internalMergeFrom, mergeDelimitedFrom, mergeDelimitedFrom, mergeFrom, mergeFrom, mergeFrom, mergeFrom, mergeFrom, mergeFrom, mergeFrom, mergeFrom, mergeFrom, newUninitializedMessageException, toStringaddAll, addAll, mergeFrom, newUninitializedMessageExceptionequals, finalize, getClass, hashCode, notify, notifyAll, wait, wait, waitfindInitializationErrors, getAllFields, getField, getInitializationErrorString, getOneofFieldDescriptor, getRepeatedField, getRepeatedFieldCount, getUnknownFields, hasField, hasOneofmergeFrompublic static final Descriptors.Descriptor getDescriptor()
protected GeneratedMessageV3.FieldAccessorTable internalGetFieldAccessorTable()
internalGetFieldAccessorTable in class GeneratedMessageV3.Builder<SearchSignalsRequest.Builder>public SearchSignalsRequest.Builder clear()
clear in interface Message.Builderclear in interface MessageLite.Builderclear in class GeneratedMessageV3.Builder<SearchSignalsRequest.Builder>public Descriptors.Descriptor getDescriptorForType()
getDescriptorForType in interface Message.BuildergetDescriptorForType in interface MessageOrBuildergetDescriptorForType in class GeneratedMessageV3.Builder<SearchSignalsRequest.Builder>public SearchSignalsRequest getDefaultInstanceForType()
getDefaultInstanceForType in interface MessageLiteOrBuildergetDefaultInstanceForType in interface MessageOrBuilderpublic SearchSignalsRequest build()
build in interface Message.Builderbuild in interface MessageLite.Builderpublic SearchSignalsRequest buildPartial()
buildPartial in interface Message.BuilderbuildPartial in interface MessageLite.Builderpublic SearchSignalsRequest.Builder clone()
clone in interface Message.Builderclone in interface MessageLite.Builderclone in class GeneratedMessageV3.Builder<SearchSignalsRequest.Builder>public SearchSignalsRequest.Builder setField(Descriptors.FieldDescriptor field, Object value)
setField in interface Message.BuildersetField in class GeneratedMessageV3.Builder<SearchSignalsRequest.Builder>public SearchSignalsRequest.Builder clearField(Descriptors.FieldDescriptor field)
clearField in interface Message.BuilderclearField in class GeneratedMessageV3.Builder<SearchSignalsRequest.Builder>public SearchSignalsRequest.Builder clearOneof(Descriptors.OneofDescriptor oneof)
clearOneof in interface Message.BuilderclearOneof in class GeneratedMessageV3.Builder<SearchSignalsRequest.Builder>public SearchSignalsRequest.Builder setRepeatedField(Descriptors.FieldDescriptor field, int index, Object value)
setRepeatedField in interface Message.BuildersetRepeatedField in class GeneratedMessageV3.Builder<SearchSignalsRequest.Builder>public SearchSignalsRequest.Builder addRepeatedField(Descriptors.FieldDescriptor field, Object value)
addRepeatedField in interface Message.BuilderaddRepeatedField in class GeneratedMessageV3.Builder<SearchSignalsRequest.Builder>public SearchSignalsRequest.Builder mergeFrom(Message other)
mergeFrom in interface Message.BuildermergeFrom in class AbstractMessage.Builder<SearchSignalsRequest.Builder>public SearchSignalsRequest.Builder mergeFrom(SearchSignalsRequest other)
public final boolean isInitialized()
isInitialized in interface MessageLiteOrBuilderisInitialized in class GeneratedMessageV3.Builder<SearchSignalsRequest.Builder>public SearchSignalsRequest.Builder mergeFrom(CodedInputStream input, ExtensionRegistryLite extensionRegistry) throws IOException
mergeFrom in interface Message.BuildermergeFrom in interface MessageLite.BuildermergeFrom in class AbstractMessage.Builder<SearchSignalsRequest.Builder>IOExceptionpublic String getParent()
Required. The resource name of the hosting Stackdriver project which requested incidents belong to.
string parent = 1 [(.google.api.field_behavior) = REQUIRED, (.google.api.resource_reference) = { ... }
getParent in interface SearchSignalsRequestOrBuilderpublic ByteString getParentBytes()
Required. The resource name of the hosting Stackdriver project which requested incidents belong to.
string parent = 1 [(.google.api.field_behavior) = REQUIRED, (.google.api.resource_reference) = { ... }
getParentBytes in interface SearchSignalsRequestOrBuilderpublic SearchSignalsRequest.Builder setParent(String value)
Required. The resource name of the hosting Stackdriver project which requested incidents belong to.
string parent = 1 [(.google.api.field_behavior) = REQUIRED, (.google.api.resource_reference) = { ... }
value - The parent to set.public SearchSignalsRequest.Builder clearParent()
Required. The resource name of the hosting Stackdriver project which requested incidents belong to.
string parent = 1 [(.google.api.field_behavior) = REQUIRED, (.google.api.resource_reference) = { ... }
public SearchSignalsRequest.Builder setParentBytes(ByteString value)
Required. The resource name of the hosting Stackdriver project which requested incidents belong to.
string parent = 1 [(.google.api.field_behavior) = REQUIRED, (.google.api.resource_reference) = { ... }
value - The bytes for parent to set.public String getQuery()
An expression that defines which signals to return. Search atoms can be used to match certain specific fields. Otherwise, plain text will match text fields in the signal. Search atoms: * `start` - (timestamp) The time the signal was created. * `title` - The title of the signal. * `signal_state` - `open` or `closed`. State of the signal. (e.g., `signal_state:open`) Timestamp formats: * yyyy-MM-dd - an absolute date, treated as a calendar-day-wide window. In other words, the "<" operator will match dates before that date, the ">" operator will match dates after that date, and the ":" operator will match the entire day. * yyyy-MM-ddTHH:mm - Same as above, but with minute resolution. * yyyy-MM-ddTHH:mm:ss - Same as above, but with second resolution. * Nd (e.g. 7d) - a relative number of days ago, treated as a moment in time (as opposed to a day-wide span) a multiple of 24 hours ago (as opposed to calendar days). In the case of daylight savings time, it will apply the current timezone to both ends of the range. Note that exact matching (e.g. `start:7d`) is unlikely to be useful because that would only match signals created precisely at a particular instant in time. The absolute timestamp formats (everything starting with a year) can optionally be followed with a UTC offset in +/-hh:mm format. Also, the 'T' separating dates and times can optionally be replaced with a space. Note that any timestamp containing a space or colon will need to be quoted. Examples: * `foo` - matches signals containing the word "foo" * `"foo bar"` - matches signals containing the phrase "foo bar" * `foo bar` or `foo AND bar` - matches signals containing the words "foo" and "bar" * `foo -bar` or `foo AND NOT bar` - matches signals containing the word "foo" but not the word "bar" * `foo OR bar` - matches signals containing the word "foo" or the word "bar" * `start>2018-11-28` - matches signals which started after November 11, 2018. * `start<=2018-11-28` - matches signals which started on or before November 11, 2018. * `start:2018-11-28` - matches signals which started on November 11, 2018. * `start>"2018-11-28 01:02:03+04:00"` - matches signals which started after November 11, 2018 at 1:02:03 AM according to the UTC+04 time zone. * `start>7d` - matches signals which started after the point in time 7*24 hours ago * `start>180d` - similar to 7d, but likely to cross the daylight savings time boundary, so the end time will be 1 hour different from "now." * `foo AND start>90d AND stage<resolved` - unresolved signals from the past 90 days containing the word "foo"
string query = 2;getQuery in interface SearchSignalsRequestOrBuilderpublic ByteString getQueryBytes()
An expression that defines which signals to return. Search atoms can be used to match certain specific fields. Otherwise, plain text will match text fields in the signal. Search atoms: * `start` - (timestamp) The time the signal was created. * `title` - The title of the signal. * `signal_state` - `open` or `closed`. State of the signal. (e.g., `signal_state:open`) Timestamp formats: * yyyy-MM-dd - an absolute date, treated as a calendar-day-wide window. In other words, the "<" operator will match dates before that date, the ">" operator will match dates after that date, and the ":" operator will match the entire day. * yyyy-MM-ddTHH:mm - Same as above, but with minute resolution. * yyyy-MM-ddTHH:mm:ss - Same as above, but with second resolution. * Nd (e.g. 7d) - a relative number of days ago, treated as a moment in time (as opposed to a day-wide span) a multiple of 24 hours ago (as opposed to calendar days). In the case of daylight savings time, it will apply the current timezone to both ends of the range. Note that exact matching (e.g. `start:7d`) is unlikely to be useful because that would only match signals created precisely at a particular instant in time. The absolute timestamp formats (everything starting with a year) can optionally be followed with a UTC offset in +/-hh:mm format. Also, the 'T' separating dates and times can optionally be replaced with a space. Note that any timestamp containing a space or colon will need to be quoted. Examples: * `foo` - matches signals containing the word "foo" * `"foo bar"` - matches signals containing the phrase "foo bar" * `foo bar` or `foo AND bar` - matches signals containing the words "foo" and "bar" * `foo -bar` or `foo AND NOT bar` - matches signals containing the word "foo" but not the word "bar" * `foo OR bar` - matches signals containing the word "foo" or the word "bar" * `start>2018-11-28` - matches signals which started after November 11, 2018. * `start<=2018-11-28` - matches signals which started on or before November 11, 2018. * `start:2018-11-28` - matches signals which started on November 11, 2018. * `start>"2018-11-28 01:02:03+04:00"` - matches signals which started after November 11, 2018 at 1:02:03 AM according to the UTC+04 time zone. * `start>7d` - matches signals which started after the point in time 7*24 hours ago * `start>180d` - similar to 7d, but likely to cross the daylight savings time boundary, so the end time will be 1 hour different from "now." * `foo AND start>90d AND stage<resolved` - unresolved signals from the past 90 days containing the word "foo"
string query = 2;getQueryBytes in interface SearchSignalsRequestOrBuilderpublic SearchSignalsRequest.Builder setQuery(String value)
An expression that defines which signals to return. Search atoms can be used to match certain specific fields. Otherwise, plain text will match text fields in the signal. Search atoms: * `start` - (timestamp) The time the signal was created. * `title` - The title of the signal. * `signal_state` - `open` or `closed`. State of the signal. (e.g., `signal_state:open`) Timestamp formats: * yyyy-MM-dd - an absolute date, treated as a calendar-day-wide window. In other words, the "<" operator will match dates before that date, the ">" operator will match dates after that date, and the ":" operator will match the entire day. * yyyy-MM-ddTHH:mm - Same as above, but with minute resolution. * yyyy-MM-ddTHH:mm:ss - Same as above, but with second resolution. * Nd (e.g. 7d) - a relative number of days ago, treated as a moment in time (as opposed to a day-wide span) a multiple of 24 hours ago (as opposed to calendar days). In the case of daylight savings time, it will apply the current timezone to both ends of the range. Note that exact matching (e.g. `start:7d`) is unlikely to be useful because that would only match signals created precisely at a particular instant in time. The absolute timestamp formats (everything starting with a year) can optionally be followed with a UTC offset in +/-hh:mm format. Also, the 'T' separating dates and times can optionally be replaced with a space. Note that any timestamp containing a space or colon will need to be quoted. Examples: * `foo` - matches signals containing the word "foo" * `"foo bar"` - matches signals containing the phrase "foo bar" * `foo bar` or `foo AND bar` - matches signals containing the words "foo" and "bar" * `foo -bar` or `foo AND NOT bar` - matches signals containing the word "foo" but not the word "bar" * `foo OR bar` - matches signals containing the word "foo" or the word "bar" * `start>2018-11-28` - matches signals which started after November 11, 2018. * `start<=2018-11-28` - matches signals which started on or before November 11, 2018. * `start:2018-11-28` - matches signals which started on November 11, 2018. * `start>"2018-11-28 01:02:03+04:00"` - matches signals which started after November 11, 2018 at 1:02:03 AM according to the UTC+04 time zone. * `start>7d` - matches signals which started after the point in time 7*24 hours ago * `start>180d` - similar to 7d, but likely to cross the daylight savings time boundary, so the end time will be 1 hour different from "now." * `foo AND start>90d AND stage<resolved` - unresolved signals from the past 90 days containing the word "foo"
string query = 2;value - The query to set.public SearchSignalsRequest.Builder clearQuery()
An expression that defines which signals to return. Search atoms can be used to match certain specific fields. Otherwise, plain text will match text fields in the signal. Search atoms: * `start` - (timestamp) The time the signal was created. * `title` - The title of the signal. * `signal_state` - `open` or `closed`. State of the signal. (e.g., `signal_state:open`) Timestamp formats: * yyyy-MM-dd - an absolute date, treated as a calendar-day-wide window. In other words, the "<" operator will match dates before that date, the ">" operator will match dates after that date, and the ":" operator will match the entire day. * yyyy-MM-ddTHH:mm - Same as above, but with minute resolution. * yyyy-MM-ddTHH:mm:ss - Same as above, but with second resolution. * Nd (e.g. 7d) - a relative number of days ago, treated as a moment in time (as opposed to a day-wide span) a multiple of 24 hours ago (as opposed to calendar days). In the case of daylight savings time, it will apply the current timezone to both ends of the range. Note that exact matching (e.g. `start:7d`) is unlikely to be useful because that would only match signals created precisely at a particular instant in time. The absolute timestamp formats (everything starting with a year) can optionally be followed with a UTC offset in +/-hh:mm format. Also, the 'T' separating dates and times can optionally be replaced with a space. Note that any timestamp containing a space or colon will need to be quoted. Examples: * `foo` - matches signals containing the word "foo" * `"foo bar"` - matches signals containing the phrase "foo bar" * `foo bar` or `foo AND bar` - matches signals containing the words "foo" and "bar" * `foo -bar` or `foo AND NOT bar` - matches signals containing the word "foo" but not the word "bar" * `foo OR bar` - matches signals containing the word "foo" or the word "bar" * `start>2018-11-28` - matches signals which started after November 11, 2018. * `start<=2018-11-28` - matches signals which started on or before November 11, 2018. * `start:2018-11-28` - matches signals which started on November 11, 2018. * `start>"2018-11-28 01:02:03+04:00"` - matches signals which started after November 11, 2018 at 1:02:03 AM according to the UTC+04 time zone. * `start>7d` - matches signals which started after the point in time 7*24 hours ago * `start>180d` - similar to 7d, but likely to cross the daylight savings time boundary, so the end time will be 1 hour different from "now." * `foo AND start>90d AND stage<resolved` - unresolved signals from the past 90 days containing the word "foo"
string query = 2;public SearchSignalsRequest.Builder setQueryBytes(ByteString value)
An expression that defines which signals to return. Search atoms can be used to match certain specific fields. Otherwise, plain text will match text fields in the signal. Search atoms: * `start` - (timestamp) The time the signal was created. * `title` - The title of the signal. * `signal_state` - `open` or `closed`. State of the signal. (e.g., `signal_state:open`) Timestamp formats: * yyyy-MM-dd - an absolute date, treated as a calendar-day-wide window. In other words, the "<" operator will match dates before that date, the ">" operator will match dates after that date, and the ":" operator will match the entire day. * yyyy-MM-ddTHH:mm - Same as above, but with minute resolution. * yyyy-MM-ddTHH:mm:ss - Same as above, but with second resolution. * Nd (e.g. 7d) - a relative number of days ago, treated as a moment in time (as opposed to a day-wide span) a multiple of 24 hours ago (as opposed to calendar days). In the case of daylight savings time, it will apply the current timezone to both ends of the range. Note that exact matching (e.g. `start:7d`) is unlikely to be useful because that would only match signals created precisely at a particular instant in time. The absolute timestamp formats (everything starting with a year) can optionally be followed with a UTC offset in +/-hh:mm format. Also, the 'T' separating dates and times can optionally be replaced with a space. Note that any timestamp containing a space or colon will need to be quoted. Examples: * `foo` - matches signals containing the word "foo" * `"foo bar"` - matches signals containing the phrase "foo bar" * `foo bar` or `foo AND bar` - matches signals containing the words "foo" and "bar" * `foo -bar` or `foo AND NOT bar` - matches signals containing the word "foo" but not the word "bar" * `foo OR bar` - matches signals containing the word "foo" or the word "bar" * `start>2018-11-28` - matches signals which started after November 11, 2018. * `start<=2018-11-28` - matches signals which started on or before November 11, 2018. * `start:2018-11-28` - matches signals which started on November 11, 2018. * `start>"2018-11-28 01:02:03+04:00"` - matches signals which started after November 11, 2018 at 1:02:03 AM according to the UTC+04 time zone. * `start>7d` - matches signals which started after the point in time 7*24 hours ago * `start>180d` - similar to 7d, but likely to cross the daylight savings time boundary, so the end time will be 1 hour different from "now." * `foo AND start>90d AND stage<resolved` - unresolved signals from the past 90 days containing the word "foo"
string query = 2;value - The bytes for query to set.public int getPageSize()
Maximum number of `signals` to return in the response.
int32 page_size = 3;getPageSize in interface SearchSignalsRequestOrBuilderpublic SearchSignalsRequest.Builder setPageSize(int value)
Maximum number of `signals` to return in the response.
int32 page_size = 3;value - The pageSize to set.public SearchSignalsRequest.Builder clearPageSize()
Maximum number of `signals` to return in the response.
int32 page_size = 3;public String getPageToken()
Page token from an earlier query, as returned in `next_page_token`. All field values except for page_size and page_token should be the same as the original query (may return an error or unexpected data otherwise).
string page_token = 4;getPageToken in interface SearchSignalsRequestOrBuilderpublic ByteString getPageTokenBytes()
Page token from an earlier query, as returned in `next_page_token`. All field values except for page_size and page_token should be the same as the original query (may return an error or unexpected data otherwise).
string page_token = 4;getPageTokenBytes in interface SearchSignalsRequestOrBuilderpublic SearchSignalsRequest.Builder setPageToken(String value)
Page token from an earlier query, as returned in `next_page_token`. All field values except for page_size and page_token should be the same as the original query (may return an error or unexpected data otherwise).
string page_token = 4;value - The pageToken to set.public SearchSignalsRequest.Builder clearPageToken()
Page token from an earlier query, as returned in `next_page_token`. All field values except for page_size and page_token should be the same as the original query (may return an error or unexpected data otherwise).
string page_token = 4;public SearchSignalsRequest.Builder setPageTokenBytes(ByteString value)
Page token from an earlier query, as returned in `next_page_token`. All field values except for page_size and page_token should be the same as the original query (may return an error or unexpected data otherwise).
string page_token = 4;value - The bytes for pageToken to set.public final SearchSignalsRequest.Builder setUnknownFields(UnknownFieldSet unknownFields)
setUnknownFields in interface Message.BuildersetUnknownFields in class GeneratedMessageV3.Builder<SearchSignalsRequest.Builder>public final SearchSignalsRequest.Builder mergeUnknownFields(UnknownFieldSet unknownFields)
mergeUnknownFields in interface Message.BuildermergeUnknownFields in class GeneratedMessageV3.Builder<SearchSignalsRequest.Builder>Copyright © 2020 Google LLC. All rights reserved.