Interface ProfilesDataOrBuilder
- All Superinterfaces:
com.google.protobuf.MessageLiteOrBuilder,com.google.protobuf.MessageOrBuilder
- All Known Implementing Classes:
ProfilesData,ProfilesData.Builder
@Generated
public interface ProfilesDataOrBuilder
extends com.google.protobuf.MessageOrBuilder
-
Method Summary
Modifier and TypeMethodDescriptionOne instance of ProfilesDictionaryOne instance of ProfilesDictionarygetResourceProfiles(int index) An array of ResourceProfiles.intAn array of ResourceProfiles.An array of ResourceProfiles.getResourceProfilesOrBuilder(int index) An array of ResourceProfiles.List<? extends ResourceProfilesOrBuilder>An array of ResourceProfiles.booleanOne instance of ProfilesDictionaryMethods inherited from interface com.google.protobuf.MessageLiteOrBuilder
isInitializedMethods inherited from interface com.google.protobuf.MessageOrBuilder
findInitializationErrors, getAllFields, getDefaultInstanceForType, getDescriptorForType, getField, getInitializationErrorString, getOneofFieldDescriptor, getRepeatedField, getRepeatedFieldCount, getUnknownFields, hasField, hasOneof
-
Method Details
-
getResourceProfilesList
List<ResourceProfiles> getResourceProfilesList()An array of ResourceProfiles. For data coming from an SDK profiler, this array will typically contain one element. Host-level profilers will usually create one ResourceProfile per container, as well as one additional ResourceProfile grouping all samples from non-containerized processes. Other resource groupings are possible as well and clarified via Resource.attributes and semantic conventions. Tools that visualize profiles should prefer displaying resources_profiles[0].scope_profiles[0].profiles[0] by default.
repeated .opentelemetry.proto.profiles.v1development.ResourceProfiles resource_profiles = 1; -
getResourceProfiles
An array of ResourceProfiles. For data coming from an SDK profiler, this array will typically contain one element. Host-level profilers will usually create one ResourceProfile per container, as well as one additional ResourceProfile grouping all samples from non-containerized processes. Other resource groupings are possible as well and clarified via Resource.attributes and semantic conventions. Tools that visualize profiles should prefer displaying resources_profiles[0].scope_profiles[0].profiles[0] by default.
repeated .opentelemetry.proto.profiles.v1development.ResourceProfiles resource_profiles = 1; -
getResourceProfilesCount
int getResourceProfilesCount()An array of ResourceProfiles. For data coming from an SDK profiler, this array will typically contain one element. Host-level profilers will usually create one ResourceProfile per container, as well as one additional ResourceProfile grouping all samples from non-containerized processes. Other resource groupings are possible as well and clarified via Resource.attributes and semantic conventions. Tools that visualize profiles should prefer displaying resources_profiles[0].scope_profiles[0].profiles[0] by default.
repeated .opentelemetry.proto.profiles.v1development.ResourceProfiles resource_profiles = 1; -
getResourceProfilesOrBuilderList
List<? extends ResourceProfilesOrBuilder> getResourceProfilesOrBuilderList()An array of ResourceProfiles. For data coming from an SDK profiler, this array will typically contain one element. Host-level profilers will usually create one ResourceProfile per container, as well as one additional ResourceProfile grouping all samples from non-containerized processes. Other resource groupings are possible as well and clarified via Resource.attributes and semantic conventions. Tools that visualize profiles should prefer displaying resources_profiles[0].scope_profiles[0].profiles[0] by default.
repeated .opentelemetry.proto.profiles.v1development.ResourceProfiles resource_profiles = 1; -
getResourceProfilesOrBuilder
An array of ResourceProfiles. For data coming from an SDK profiler, this array will typically contain one element. Host-level profilers will usually create one ResourceProfile per container, as well as one additional ResourceProfile grouping all samples from non-containerized processes. Other resource groupings are possible as well and clarified via Resource.attributes and semantic conventions. Tools that visualize profiles should prefer displaying resources_profiles[0].scope_profiles[0].profiles[0] by default.
repeated .opentelemetry.proto.profiles.v1development.ResourceProfiles resource_profiles = 1; -
hasDictionary
boolean hasDictionary()One instance of ProfilesDictionary
.opentelemetry.proto.profiles.v1development.ProfilesDictionary dictionary = 2;- Returns:
- Whether the dictionary field is set.
-
getDictionary
ProfilesDictionary getDictionary()One instance of ProfilesDictionary
.opentelemetry.proto.profiles.v1development.ProfilesDictionary dictionary = 2;- Returns:
- The dictionary.
-
getDictionaryOrBuilder
ProfilesDictionaryOrBuilder getDictionaryOrBuilder()One instance of ProfilesDictionary
.opentelemetry.proto.profiles.v1development.ProfilesDictionary dictionary = 2;
-