Skip to content

RMST-299: Add support for Glean Telemetry in Remote Settings client #7288

Open
leplatrem wants to merge 20 commits intomainfrom
rmst-299
Open

RMST-299: Add support for Glean Telemetry in Remote Settings client #7288
leplatrem wants to merge 20 commits intomainfrom
rmst-299

Conversation

@leplatrem
Copy link
Copy Markdown
Contributor

@leplatrem leplatrem commented Mar 24, 2026

Pull Request checklist

  • Breaking changes: This PR follows our breaking change policy
    • This PR follows the breaking change policy:
      • This PR has no breaking API changes, or
      • There are corresponding PRs for our consumer applications that resolve the breaking changes and have been approved
  • Quality: This PR builds and tests run cleanly
    • Note:
      • For changes that need extra cross-platform testing, consider adding [ci full] to the PR title.
      • If this pull request includes a breaking change, consider cutting a new release after merging.
  • Tests: This PR includes thorough tests or an explanation of why it does not
  • Changelog: This PR includes a changelog entry in CHANGELOG.md or an explanation of why it does not need one
    • Any breaking changes to Swift or Kotlin binding APIs are noted explicitly
  • Dependencies: This PR follows our dependency management guidelines
    • Any new dependencies are accompanied by a summary of the due diligence applied in selecting them.

@leplatrem leplatrem marked this pull request as ready for review March 25, 2026 12:17
# License, v. 2.0. If a copy of the MPL was not distributed with this
# file, You can obtain one at http://mozilla.org/MPL/2.0/.

# This file defines the metrics that will be gathered for the Remote Settings
Copy link
Copy Markdown
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Is this file even required?

Since technically the telemetry is done in consuming components (eg. kotlin)

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

It's required if you want to check in the Kotlin code in app-services to implement the metrics (e.g. you could define a RemoteSettingsTelemetry implementation that firefox-android could use). Also you might want to use this PR for data review. If neither of those is true, then I don't think it's needed.

Copy link
Copy Markdown
Contributor

@bendk bendk left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

The code looks good to me, but a couple notes:

  • If this is a new metric, then it'll need data review.
  • Jan-Erik is working on a system for reporting Glean metrics directly from Rust. The ETA is somewhere around the start of H2, but that's not set in stone. So, if there's no deadline for this you may want to wait for that to land and everything gets easier. If there is a deadline, then you probably don't want to wait.

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I think this got checked in by accident.

# License, v. 2.0. If a copy of the MPL was not distributed with this
# file, You can obtain one at http://mozilla.org/MPL/2.0/.

# This file defines the metrics that will be gathered for the Remote Settings
Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

It's required if you want to check in the Kotlin code in app-services to implement the metrics (e.g. you could define a RemoteSettingsTelemetry implementation that firefox-android could use). Also you might want to use this PR for data review. If neither of those is true, then I don't think it's needed.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants