There's currently no way to send a custom ping, and Glean.sendPing could certainly be it. Though perhaps we want the public API to only be able to send custom pings, not built-in ones.

Recently, Glean.sendPing became Glean.sendPings (to support parallel sending), but the issue fundamentally still stands.

I feel like we can basically get away with making the existing sendPings public, however, I think for safety we shouldn't allow the public API to send pings that are internally managed and scheduled by glean (metrics, events, baseline). It seems like it would be too easy to screw up the carefully-orchestrated scheduling on those. How do others feel about that?

I think that's fine, I was also a little concerned about limiting the public access to the internal pings. As long as you are limiting the public API to only sending custom pings, then I am okay with that approach.

(In reply to Michael Droettboom [:mdroettboom] from comment #2)

I feel like we can basically get away with making the existing sendPings public, however, I think for safety we shouldn't allow the public API to send pings that are internally managed and scheduled by glean (metrics, events, baseline). It seems like it would be too easy to screw up the carefully-orchestrated scheduling on those. How do others feel about that?

+1 from me to just disallowing the pings owned by Glean for it.

(In reply to Michael Droettboom [:mdroettboom] from comment #2)

I feel like we can basically get away with making the existing sendPings public, however, I think for safety we shouldn't allow the public API to send pings that are internally managed and scheduled by glean (metrics, events, baseline). It seems like it would be too easy to screw up the carefully-orchestrated scheduling on those. How do others feel about that?

Yes. The only caveat there is that we want GleanDebugActivity to still be able to trigger pings we own (e.g. to test events or recorded metrics). One easy way to make this work would be to have 2 APIs:

• an internal internalSendPings (or something like that), which would be unfiltered. This would be callable from the GleanDebugActivity, which has access to internals;
• the public sendPings, which would apply ping filtering and then call internalSendPings.