Closed Bug 1974069 Opened 6 months ago Closed 4 months ago

Add profile markers for dual_labeled_counter submetric operations

Categories

(Toolkit :: Telemetry, task, P2)

task

Tracking

()

RESOLVED FIXED
143 Branch
Tracking Status
firefox143 --- fixed

People

(Reporter: chutten|PTO, Assigned: chutten|PTO)

References

Details

Attachments

(3 files)

dual_labeled_counter submetrics should add profiler markers on their add operations similar to how LabeledCounterMetric does.

This will be complicated by how CounterMetric already has a MetricMetadataGetterImpl impl thanks to LabeledCounterMetric so none of the existing macros will work. Probably best to split the submetric-specific parts of define_metric_metadata_getter! into its own macro for DualLabeledCounterSubMetric to use.

A fix for this bug should also augment the add new metric type to FOG docs with instructions about how to ensure new metric types' operations properly add profiler markers (and test them).

Assignee: nobody → chutten
Status: NEW → ASSIGNED
Priority: -- → P2
Depends on: 1974793
No longer depends on: 1973102

For the record, the way this manifests today is that dual_labeled_counter add operations do indeed get Countre::add markers like labeled_counter metrics' add operations do, but instead of having the metric name they have an error like: Error looking up SubId(SubMetricId(33554471)): FOGSubmetricLookupFailed.

See Also: → 1934947

This

  1. Keeps the macros from being available to modules outside of api/src/private
  2. Keeps the macros from being available to crates outside of firefox-on-glean
  3. Allows api/src/private to use the macros without crate:: scoping

In the parent process the submetric operations are all in CounterMetric's macros.

Status: ASSIGNED → RESOLVED
Closed: 4 months ago
Resolution: --- → FIXED
Target Milestone: --- → 143 Branch
QA Whiteboard: [qa-triage-done-c144/b143]
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Created:
Updated:
Size: