Reference documentation and code samples for the Stackdriver Monitoring V3 Client class DroppedLabels.
A set of (label, value) pairs that were removed from a Distribution
time series during aggregation and then added as an attachment to a
Distribution.Exemplar.
The full label set for the exemplars is constructed by using the dropped
pairs in combination with the label values that remain on the aggregated
Distribution time series. The constructed full label set can be used to
identify the specific entity, such as the instance or job, which might be
contributing to a long-tail. However, with dropped labels, the storage
requirements are reduced because only the aggregated distribution values for
a large group of time series are stored.
Note that there are no guarantees on ordering of the labels from
exemplar-to-exemplar and from distribution-to-distribution in the same
stream, and there may be duplicates. It is up to clients to resolve any
ambiguities.
Generated from protobuf messagegoogle.monitoring.v3.DroppedLabels
[[["Easy to understand","easyToUnderstand","thumb-up"],["Solved my problem","solvedMyProblem","thumb-up"],["Other","otherUp","thumb-up"]],[["Hard to understand","hardToUnderstand","thumb-down"],["Incorrect information or sample code","incorrectInformationOrSampleCode","thumb-down"],["Missing the information/samples I need","missingTheInformationSamplesINeed","thumb-down"],["Other","otherDown","thumb-down"]],["Last updated 2025-09-04 UTC."],[],[],null,["# Stackdriver Monitoring V3 Client - Class DroppedLabels (2.1.2)\n\nVersion latestkeyboard_arrow_down\n\n- [2.1.2 (latest)](/php/docs/reference/cloud-monitoring/latest/V3.DroppedLabels)\n- [2.1.1](/php/docs/reference/cloud-monitoring/2.1.1/V3.DroppedLabels)\n- [2.0.1](/php/docs/reference/cloud-monitoring/2.0.1/V3.DroppedLabels)\n- [1.12.1](/php/docs/reference/cloud-monitoring/1.12.1/V3.DroppedLabels)\n- [1.11.1](/php/docs/reference/cloud-monitoring/1.11.1/V3.DroppedLabels)\n- [1.10.3](/php/docs/reference/cloud-monitoring/1.10.3/V3.DroppedLabels)\n- [1.9.0](/php/docs/reference/cloud-monitoring/1.9.0/V3.DroppedLabels)\n- [1.8.0](/php/docs/reference/cloud-monitoring/1.8.0/V3.DroppedLabels)\n- [1.7.1](/php/docs/reference/cloud-monitoring/1.7.1/V3.DroppedLabels)\n- [1.6.0](/php/docs/reference/cloud-monitoring/1.6.0/V3.DroppedLabels)\n- [1.5.1](/php/docs/reference/cloud-monitoring/1.5.1/V3.DroppedLabels)\n- [1.4.0](/php/docs/reference/cloud-monitoring/1.4.0/V3.DroppedLabels)\n- [1.3.2](/php/docs/reference/cloud-monitoring/1.3.2/V3.DroppedLabels)\n- [1.2.2](/php/docs/reference/cloud-monitoring/1.2.2/V3.DroppedLabels) \nReference documentation and code samples for the Stackdriver Monitoring V3 Client class DroppedLabels.\n\nA set of (label, value) pairs that were removed from a Distribution\ntime series during aggregation and then added as an attachment to a\nDistribution.Exemplar.\n\nThe full label set for the exemplars is constructed by using the dropped\npairs in combination with the label values that remain on the aggregated\nDistribution time series. The constructed full label set can be used to\nidentify the specific entity, such as the instance or job, which might be\ncontributing to a long-tail. However, with dropped labels, the storage\nrequirements are reduced because only the aggregated distribution values for\na large group of time series are stored.\nNote that there are no guarantees on ordering of the labels from\nexemplar-to-exemplar and from distribution-to-distribution in the same\nstream, and there may be duplicates. It is up to clients to resolve any\nambiguities.\n\nGenerated from protobuf message `google.monitoring.v3.DroppedLabels`\n\nNamespace\n---------\n\nGoogle \\\\ Cloud \\\\ Monitoring \\\\ V3\n\nMethods\n-------\n\n### __construct\n\nConstructor.\n\n### getLabel\n\nMap from label to its value, for all labels dropped in any aggregation.\n\n### setLabel\n\nMap from label to its value, for all labels dropped in any aggregation."]]