Closed Bug 1706874 Opened 4 years ago Closed 4 years ago

What dependencies should projects using Glean.js use in the probe-scraper?

Categories

(Data Platform and Tools Graveyard :: Glean.js, task)

Tracking

(Not tracked)

RESOLVED INVALID

People

(Reporter: Dexter, Unassigned)

References

Details

We currently define a dependency named "glean-core". That's common to all the projects using the Glean SDK.

I believe we should define something similar for glean-js so that products using glean-js can list the related dependency.

However.. shouldn't the defined metrics be the same, since the ping_info and client_info are the same? Do we expect to have Glean.js specific metrics outside of these sections?

Flags: needinfo?(brizental)
Blocks: 1706875

There is a library that I added there a few weeks agora called glean-js.

However.. shouldn't the defined metrics be the same, since the ping_info and client_info are the same? Do we expect to have Glean.js specific metrics outside of these sections?

In the that we point to Glean.js metrics.yaml and pings.yaml files. Even though the metrics are the same we duplicate these files.

Not sure I answered / understood you question maybe.

Flags: needinfo?(brizental)

(In reply to Beatriz Rizental [:brizental] from comment #1)

There is a library that I added there a few weeks agora called glean-js.

However.. shouldn't the defined metrics be the same, since the ping_info and client_info are the same? Do we expect to have Glean.js specific metrics outside of these sections?

In the that we point to Glean.js metrics.yaml and pings.yaml files. Even though the metrics are the same we duplicate these files.

Not sure I answered / understood you question maybe.

Ah, yes, that's exactly what I was looking for. I did not bother scroll the file as I somehow expected all the glean stuff to be close together at the top (for no real reason).

Status: NEW → RESOLVED
Closed: 4 years ago
Resolution: --- → INVALID
Product: Data Platform and Tools → Data Platform and Tools Graveyard
You need to log in before you can comment on or make changes to this bug.