What dependencies should projects using Glean.js use in the probe-scraper?
Categories
(Data Platform and Tools Graveyard :: Glean.js, task)
Tracking
(Not tracked)
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?
Comment 1•4 years ago
|
||
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.
Reporter | ||
Comment 2•4 years ago
|
||
(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
andpings.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).
Updated•3 years ago
|
Description
•