ProfilesData
extends Message
in package
ProfilesData represents the profiles data that can be stored in persistent storage, OR can be embedded by other protocols that transfer OTLP profiles data but do not implement the OTLP protocol.
The main difference between this message and collector protocol is that in this message there will not be any "control" or "metadata" specific to OTLP protocol. When new fields are added into this message, the OTLP request MUST be updated as well.
Generated from protobuf message opentelemetry.proto.profiles.v1development.ProfilesData
Table of Contents
Properties
- $dictionary : mixed
- One instance of ProfilesDictionary
- $resource_profiles : mixed
- An array of ResourceProfiles.
Methods
- __construct() : mixed
- Constructor.
- clearDictionary() : mixed
- getDictionary() : ProfilesDictionary|null
- One instance of ProfilesDictionary
- getResourceProfiles() : RepeatedField
- An array of ResourceProfiles.
- hasDictionary() : mixed
- setDictionary() : $this
- One instance of ProfilesDictionary
- setResourceProfiles() : $this
- An array of ResourceProfiles.
Properties
$dictionary
One instance of ProfilesDictionary
protected
mixed
$dictionary
= null
Generated from protobuf field .opentelemetry.proto.profiles.v1development.ProfilesDictionary dictionary = 2;
$resource_profiles
An array of ResourceProfiles.
private
mixed
$resource_profiles
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.
Generated from protobuf field repeated .opentelemetry.proto.profiles.v1development.ResourceProfiles resource_profiles = 1;
Methods
__construct()
Constructor.
public
__construct([array<string|int, mixed> $data = null ]) : mixed
Parameters
- $data : array<string|int, mixed> = null
-
{ Optional. Data for populating the Message object.
@type \Opentelemetry\Proto\Profiles\V1development\ResourceProfiles[]|\Google\Protobuf\Internal\RepeatedField $resource_profiles 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. @type \Opentelemetry\Proto\Profiles\V1development\ProfilesDictionary $dictionary One instance of ProfilesDictionary}
clearDictionary()
public
clearDictionary() : mixed
getDictionary()
One instance of ProfilesDictionary
public
getDictionary() : ProfilesDictionary|null
Generated from protobuf field .opentelemetry.proto.profiles.v1development.ProfilesDictionary dictionary = 2;
Return values
ProfilesDictionary|nullgetResourceProfiles()
An array of ResourceProfiles.
public
getResourceProfiles() : RepeatedField
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.
Generated from protobuf field repeated .opentelemetry.proto.profiles.v1development.ResourceProfiles resource_profiles = 1;
Return values
RepeatedFieldhasDictionary()
public
hasDictionary() : mixed
setDictionary()
One instance of ProfilesDictionary
public
setDictionary(ProfilesDictionary $var) : $this
Generated from protobuf field .opentelemetry.proto.profiles.v1development.ProfilesDictionary dictionary = 2;
Parameters
- $var : ProfilesDictionary
Return values
$thissetResourceProfiles()
An array of ResourceProfiles.
public
setResourceProfiles(array<string|int, ResourceProfiles>|RepeatedField $var) : $this
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.
Generated from protobuf field repeated .opentelemetry.proto.profiles.v1development.ResourceProfiles resource_profiles = 1;
Parameters
- $var : array<string|int, ResourceProfiles>|RepeatedField