Package io.opentelemetry.proto.metrics.experimental

Class MetricConfigResponse.Builder

    • Method Detail

      • getDescriptor

        public static final com.google.protobuf.Descriptors.Descriptor getDescriptor()

      • internalGetFieldAccessorTable

        protected com.google.protobuf.GeneratedMessageV3.FieldAccessorTable internalGetFieldAccessorTable()
        Specified by:
        internalGetFieldAccessorTable in class com.google.protobuf.GeneratedMessageV3.Builder<MetricConfigResponse.Builder>

      • clear

        public MetricConfigResponse.Builder clear()
        Specified by:
        clear in interface com.google.protobuf.Message.Builder
        Specified by:
        clear in interface com.google.protobuf.MessageLite.Builder
        Overrides:
        clear in class com.google.protobuf.GeneratedMessageV3.Builder<MetricConfigResponse.Builder>

      • getDescriptorForType

        public com.google.protobuf.Descriptors.Descriptor getDescriptorForType()
        Specified by:
        getDescriptorForType in interface com.google.protobuf.Message.Builder
        Specified by:
        getDescriptorForType in interface com.google.protobuf.MessageOrBuilder
        Overrides:
        getDescriptorForType in class com.google.protobuf.GeneratedMessageV3.Builder<MetricConfigResponse.Builder>

      • getDefaultInstanceForType

        public MetricConfigResponse getDefaultInstanceForType()
        Specified by:
        getDefaultInstanceForType in interface com.google.protobuf.MessageLiteOrBuilder
        Specified by:
        getDefaultInstanceForType in interface com.google.protobuf.MessageOrBuilder

      • build

        public MetricConfigResponse build()
        Specified by:
        build in interface com.google.protobuf.Message.Builder
        Specified by:
        build in interface com.google.protobuf.MessageLite.Builder

      • buildPartial

        public MetricConfigResponse buildPartial()
        Specified by:
        buildPartial in interface com.google.protobuf.Message.Builder
        Specified by:
        buildPartial in interface com.google.protobuf.MessageLite.Builder

      • clone

        public MetricConfigResponse.Builder clone()
        Specified by:
        clone in interface com.google.protobuf.Message.Builder
        Specified by:
        clone in interface com.google.protobuf.MessageLite.Builder
        Overrides:
        clone in class com.google.protobuf.GeneratedMessageV3.Builder<MetricConfigResponse.Builder>

      • setField

        public MetricConfigResponse.Builder setField​(com.google.protobuf.Descriptors.FieldDescriptor field,
                                             Object value)
        Specified by:
        setField in interface com.google.protobuf.Message.Builder
        Overrides:
        setField in class com.google.protobuf.GeneratedMessageV3.Builder<MetricConfigResponse.Builder>

      • clearField

        public MetricConfigResponse.Builder clearField​(com.google.protobuf.Descriptors.FieldDescriptor field)
        Specified by:
        clearField in interface com.google.protobuf.Message.Builder
        Overrides:
        clearField in class com.google.protobuf.GeneratedMessageV3.Builder<MetricConfigResponse.Builder>

      • clearOneof

        public MetricConfigResponse.Builder clearOneof​(com.google.protobuf.Descriptors.OneofDescriptor oneof)
        Specified by:
        clearOneof in interface com.google.protobuf.Message.Builder
        Overrides:
        clearOneof in class com.google.protobuf.GeneratedMessageV3.Builder<MetricConfigResponse.Builder>

      • setRepeatedField

        public MetricConfigResponse.Builder setRepeatedField​(com.google.protobuf.Descriptors.FieldDescriptor field,
                                                     int index,
                                                     Object value)
        Specified by:
        setRepeatedField in interface com.google.protobuf.Message.Builder
        Overrides:
        setRepeatedField in class com.google.protobuf.GeneratedMessageV3.Builder<MetricConfigResponse.Builder>

      • addRepeatedField

        public MetricConfigResponse.Builder addRepeatedField​(com.google.protobuf.Descriptors.FieldDescriptor field,
                                                     Object value)
        Specified by:
        addRepeatedField in interface com.google.protobuf.Message.Builder
        Overrides:
        addRepeatedField in class com.google.protobuf.GeneratedMessageV3.Builder<MetricConfigResponse.Builder>

      • isInitialized

        public final boolean isInitialized()
        Specified by:
        isInitialized in interface com.google.protobuf.MessageLiteOrBuilder
        Overrides:
        isInitialized in class com.google.protobuf.GeneratedMessageV3.Builder<MetricConfigResponse.Builder>

      • mergeFrom

        public MetricConfigResponse.Builder mergeFrom​(com.google.protobuf.CodedInputStream input,
                                              com.google.protobuf.ExtensionRegistryLite extensionRegistry)
                                       throws IOException
        Specified by:
        mergeFrom in interface com.google.protobuf.Message.Builder
        Specified by:
        mergeFrom in interface com.google.protobuf.MessageLite.Builder
        Overrides:
        mergeFrom in class com.google.protobuf.AbstractMessage.Builder<MetricConfigResponse.Builder>
        Throws:
        IOException

      • getFingerprint

        public com.google.protobuf.ByteString getFingerprint()
         Optional. The fingerprint associated with this MetricConfigResponse. Each
 change in configs yields a different fingerprint. The resource SHOULD copy
 this value to MetricConfigRequest.last_known_fingerprint for the next
 configuration request. If there are no changes between fingerprint and
 MetricConfigRequest.last_known_fingerprint, then all other fields besides
 fingerprint in the response are optional, or the same as the last update if
 present.
 The exact mechanics of generating the fingerprint is up to the
 implementation. However, a fingerprint must be deterministically determined
 by the configurations -- the same configuration will generate the same
 fingerprint on any instance of an implementation. Hence using a timestamp is
 unacceptable, but a deterministic hash is fine.
        bytes fingerprint = 1;
        Specified by:
        getFingerprint in interface MetricConfigResponseOrBuilder

      • setFingerprint

        public MetricConfigResponse.Builder setFingerprint​(com.google.protobuf.ByteString value)
         Optional. The fingerprint associated with this MetricConfigResponse. Each
 change in configs yields a different fingerprint. The resource SHOULD copy
 this value to MetricConfigRequest.last_known_fingerprint for the next
 configuration request. If there are no changes between fingerprint and
 MetricConfigRequest.last_known_fingerprint, then all other fields besides
 fingerprint in the response are optional, or the same as the last update if
 present.
 The exact mechanics of generating the fingerprint is up to the
 implementation. However, a fingerprint must be deterministically determined
 by the configurations -- the same configuration will generate the same
 fingerprint on any instance of an implementation. Hence using a timestamp is
 unacceptable, but a deterministic hash is fine.
        bytes fingerprint = 1;

      • clearFingerprint

        public MetricConfigResponse.Builder clearFingerprint()
         Optional. The fingerprint associated with this MetricConfigResponse. Each
 change in configs yields a different fingerprint. The resource SHOULD copy
 this value to MetricConfigRequest.last_known_fingerprint for the next
 configuration request. If there are no changes between fingerprint and
 MetricConfigRequest.last_known_fingerprint, then all other fields besides
 fingerprint in the response are optional, or the same as the last update if
 present.
 The exact mechanics of generating the fingerprint is up to the
 implementation. However, a fingerprint must be deterministically determined
 by the configurations -- the same configuration will generate the same
 fingerprint on any instance of an implementation. Hence using a timestamp is
 unacceptable, but a deterministic hash is fine.
        bytes fingerprint = 1;

      • getSchedulesList

        public List<MetricConfigResponse.Schedule> getSchedulesList()
         A single metric may match multiple schedules. In such cases, the schedule
 that specifies the smallest period is applied.
 Note, for optimization purposes, it is recommended to use as few schedules
 as possible to capture all required metric updates. Where you can be
 conservative, do take full advantage of the inclusion/exclusion patterns to
 capture as much of your targeted metrics.
        repeated .opentelemetry.proto.metrics.experimental.MetricConfigResponse.Schedule schedules = 2;
        Specified by:
        getSchedulesList in interface MetricConfigResponseOrBuilder

      • getSchedulesCount

        public int getSchedulesCount()
         A single metric may match multiple schedules. In such cases, the schedule
 that specifies the smallest period is applied.
 Note, for optimization purposes, it is recommended to use as few schedules
 as possible to capture all required metric updates. Where you can be
 conservative, do take full advantage of the inclusion/exclusion patterns to
 capture as much of your targeted metrics.
        repeated .opentelemetry.proto.metrics.experimental.MetricConfigResponse.Schedule schedules = 2;
        Specified by:
        getSchedulesCount in interface MetricConfigResponseOrBuilder

      • getSchedules

        public MetricConfigResponse.Schedule getSchedules​(int index)
         A single metric may match multiple schedules. In such cases, the schedule
 that specifies the smallest period is applied.
 Note, for optimization purposes, it is recommended to use as few schedules
 as possible to capture all required metric updates. Where you can be
 conservative, do take full advantage of the inclusion/exclusion patterns to
 capture as much of your targeted metrics.
        repeated .opentelemetry.proto.metrics.experimental.MetricConfigResponse.Schedule schedules = 2;
        Specified by:
        getSchedules in interface MetricConfigResponseOrBuilder

      • setSchedules

        public MetricConfigResponse.Builder setSchedules​(int index,
                                                 MetricConfigResponse.Schedule value)
         A single metric may match multiple schedules. In such cases, the schedule
 that specifies the smallest period is applied.
 Note, for optimization purposes, it is recommended to use as few schedules
 as possible to capture all required metric updates. Where you can be
 conservative, do take full advantage of the inclusion/exclusion patterns to
 capture as much of your targeted metrics.
        repeated .opentelemetry.proto.metrics.experimental.MetricConfigResponse.Schedule schedules = 2;

      • setSchedules

        public MetricConfigResponse.Builder setSchedules​(int index,
                                                 MetricConfigResponse.Schedule.Builder builderForValue)
         A single metric may match multiple schedules. In such cases, the schedule
 that specifies the smallest period is applied.
 Note, for optimization purposes, it is recommended to use as few schedules
 as possible to capture all required metric updates. Where you can be
 conservative, do take full advantage of the inclusion/exclusion patterns to
 capture as much of your targeted metrics.
        repeated .opentelemetry.proto.metrics.experimental.MetricConfigResponse.Schedule schedules = 2;

      • addSchedules

        public MetricConfigResponse.Builder addSchedules​(MetricConfigResponse.Schedule value)
         A single metric may match multiple schedules. In such cases, the schedule
 that specifies the smallest period is applied.
 Note, for optimization purposes, it is recommended to use as few schedules
 as possible to capture all required metric updates. Where you can be
 conservative, do take full advantage of the inclusion/exclusion patterns to
 capture as much of your targeted metrics.
        repeated .opentelemetry.proto.metrics.experimental.MetricConfigResponse.Schedule schedules = 2;

      • addSchedules

        public MetricConfigResponse.Builder addSchedules​(int index,
                                                 MetricConfigResponse.Schedule value)
         A single metric may match multiple schedules. In such cases, the schedule
 that specifies the smallest period is applied.
 Note, for optimization purposes, it is recommended to use as few schedules
 as possible to capture all required metric updates. Where you can be
 conservative, do take full advantage of the inclusion/exclusion patterns to
 capture as much of your targeted metrics.
        repeated .opentelemetry.proto.metrics.experimental.MetricConfigResponse.Schedule schedules = 2;

      • addSchedules

        public MetricConfigResponse.Builder addSchedules​(MetricConfigResponse.Schedule.Builder builderForValue)
         A single metric may match multiple schedules. In such cases, the schedule
 that specifies the smallest period is applied.
 Note, for optimization purposes, it is recommended to use as few schedules
 as possible to capture all required metric updates. Where you can be
 conservative, do take full advantage of the inclusion/exclusion patterns to
 capture as much of your targeted metrics.
        repeated .opentelemetry.proto.metrics.experimental.MetricConfigResponse.Schedule schedules = 2;

      • addSchedules

        public MetricConfigResponse.Builder addSchedules​(int index,
                                                 MetricConfigResponse.Schedule.Builder builderForValue)
         A single metric may match multiple schedules. In such cases, the schedule
 that specifies the smallest period is applied.
 Note, for optimization purposes, it is recommended to use as few schedules
 as possible to capture all required metric updates. Where you can be
 conservative, do take full advantage of the inclusion/exclusion patterns to
 capture as much of your targeted metrics.
        repeated .opentelemetry.proto.metrics.experimental.MetricConfigResponse.Schedule schedules = 2;

      • addAllSchedules

        public MetricConfigResponse.Builder addAllSchedules​(Iterable<? extends MetricConfigResponse.Schedule> values)
         A single metric may match multiple schedules. In such cases, the schedule
 that specifies the smallest period is applied.
 Note, for optimization purposes, it is recommended to use as few schedules
 as possible to capture all required metric updates. Where you can be
 conservative, do take full advantage of the inclusion/exclusion patterns to
 capture as much of your targeted metrics.
        repeated .opentelemetry.proto.metrics.experimental.MetricConfigResponse.Schedule schedules = 2;

      • clearSchedules

        public MetricConfigResponse.Builder clearSchedules()
         A single metric may match multiple schedules. In such cases, the schedule
 that specifies the smallest period is applied.
 Note, for optimization purposes, it is recommended to use as few schedules
 as possible to capture all required metric updates. Where you can be
 conservative, do take full advantage of the inclusion/exclusion patterns to
 capture as much of your targeted metrics.
        repeated .opentelemetry.proto.metrics.experimental.MetricConfigResponse.Schedule schedules = 2;

      • removeSchedules

        public MetricConfigResponse.Builder removeSchedules​(int index)
         A single metric may match multiple schedules. In such cases, the schedule
 that specifies the smallest period is applied.
 Note, for optimization purposes, it is recommended to use as few schedules
 as possible to capture all required metric updates. Where you can be
 conservative, do take full advantage of the inclusion/exclusion patterns to
 capture as much of your targeted metrics.
        repeated .opentelemetry.proto.metrics.experimental.MetricConfigResponse.Schedule schedules = 2;

      • getSchedulesBuilder

        public MetricConfigResponse.Schedule.Builder getSchedulesBuilder​(int index)
         A single metric may match multiple schedules. In such cases, the schedule
 that specifies the smallest period is applied.
 Note, for optimization purposes, it is recommended to use as few schedules
 as possible to capture all required metric updates. Where you can be
 conservative, do take full advantage of the inclusion/exclusion patterns to
 capture as much of your targeted metrics.
        repeated .opentelemetry.proto.metrics.experimental.MetricConfigResponse.Schedule schedules = 2;

      • getSchedulesOrBuilder

        public MetricConfigResponse.ScheduleOrBuilder getSchedulesOrBuilder​(int index)
         A single metric may match multiple schedules. In such cases, the schedule
 that specifies the smallest period is applied.
 Note, for optimization purposes, it is recommended to use as few schedules
 as possible to capture all required metric updates. Where you can be
 conservative, do take full advantage of the inclusion/exclusion patterns to
 capture as much of your targeted metrics.
        repeated .opentelemetry.proto.metrics.experimental.MetricConfigResponse.Schedule schedules = 2;
        Specified by:
        getSchedulesOrBuilder in interface MetricConfigResponseOrBuilder

      • getSchedulesOrBuilderList

        public List<? extends MetricConfigResponse.ScheduleOrBuilder> getSchedulesOrBuilderList()
         A single metric may match multiple schedules. In such cases, the schedule
 that specifies the smallest period is applied.
 Note, for optimization purposes, it is recommended to use as few schedules
 as possible to capture all required metric updates. Where you can be
 conservative, do take full advantage of the inclusion/exclusion patterns to
 capture as much of your targeted metrics.
        repeated .opentelemetry.proto.metrics.experimental.MetricConfigResponse.Schedule schedules = 2;
        Specified by:
        getSchedulesOrBuilderList in interface MetricConfigResponseOrBuilder

      • addSchedulesBuilder

        public MetricConfigResponse.Schedule.Builder addSchedulesBuilder()
         A single metric may match multiple schedules. In such cases, the schedule
 that specifies the smallest period is applied.
 Note, for optimization purposes, it is recommended to use as few schedules
 as possible to capture all required metric updates. Where you can be
 conservative, do take full advantage of the inclusion/exclusion patterns to
 capture as much of your targeted metrics.
        repeated .opentelemetry.proto.metrics.experimental.MetricConfigResponse.Schedule schedules = 2;

      • addSchedulesBuilder

        public MetricConfigResponse.Schedule.Builder addSchedulesBuilder​(int index)
         A single metric may match multiple schedules. In such cases, the schedule
 that specifies the smallest period is applied.
 Note, for optimization purposes, it is recommended to use as few schedules
 as possible to capture all required metric updates. Where you can be
 conservative, do take full advantage of the inclusion/exclusion patterns to
 capture as much of your targeted metrics.
        repeated .opentelemetry.proto.metrics.experimental.MetricConfigResponse.Schedule schedules = 2;

      • getSchedulesBuilderList

        public List<MetricConfigResponse.Schedule.Builder> getSchedulesBuilderList()
         A single metric may match multiple schedules. In such cases, the schedule
 that specifies the smallest period is applied.
 Note, for optimization purposes, it is recommended to use as few schedules
 as possible to capture all required metric updates. Where you can be
 conservative, do take full advantage of the inclusion/exclusion patterns to
 capture as much of your targeted metrics.
        repeated .opentelemetry.proto.metrics.experimental.MetricConfigResponse.Schedule schedules = 2;

      • getSuggestedWaitTimeSec

        public int getSuggestedWaitTimeSec()
         Optional. The client is suggested to wait this long (in seconds) before
 pinging the configuration service again.
        int32 suggested_wait_time_sec = 3;
        Specified by:
        getSuggestedWaitTimeSec in interface MetricConfigResponseOrBuilder

      • setSuggestedWaitTimeSec

        public MetricConfigResponse.Builder setSuggestedWaitTimeSec​(int value)
         Optional. The client is suggested to wait this long (in seconds) before
 pinging the configuration service again.
        int32 suggested_wait_time_sec = 3;

      • clearSuggestedWaitTimeSec

        public MetricConfigResponse.Builder clearSuggestedWaitTimeSec()
         Optional. The client is suggested to wait this long (in seconds) before
 pinging the configuration service again.
        int32 suggested_wait_time_sec = 3;

      • setUnknownFields

        public final MetricConfigResponse.Builder setUnknownFields​(com.google.protobuf.UnknownFieldSet unknownFields)
        Specified by:
        setUnknownFields in interface com.google.protobuf.Message.Builder
        Overrides:
        setUnknownFields in class com.google.protobuf.GeneratedMessageV3.Builder<MetricConfigResponse.Builder>

      • mergeUnknownFields

        public final MetricConfigResponse.Builder mergeUnknownFields​(com.google.protobuf.UnknownFieldSet unknownFields)
        Specified by:
        mergeUnknownFields in interface com.google.protobuf.Message.Builder
        Overrides:
        mergeUnknownFields in class com.google.protobuf.GeneratedMessageV3.Builder<MetricConfigResponse.Builder>