The Glean SDK exports the
GleanDebugActivity that can be used to toggle debugging features on or off.
Users can invoke this special activity, at run-time, using the following
adb shell am start -n [applicationId]/mozilla.telemetry.glean.debug.GleanDebugActivity [extra keys]
In the above:
[applicationId]is the product's application id as defined in the manifest file and/or build script. For the Glean sample application, this is
org.mozilla.samples.gleancorefor a release build and
org.mozilla.samples.gleancore.debugfor a debug build.
[extra keys]is a list of extra keys to be passed to the debug activity. See the documentation for the command line switches used to pass the extra keys. These are the currently supported keys:
|boolean (||If set to |
|string (||Tags all outgoing pings as debug pings to make them available for real-time validation, on the Glean Debug View. The value must match the pattern |
|string array (||Tags outgoing pings with a maximum of 5 comma-separated tags. The tags must match the pattern |
|string (||Sends the ping with the given name immediately|
|string (||The name of an exported Android |
All the options provided to start the activity are passed over to the main activity for the application to process. This is useful if SDK users wants to debug telemetry while providing additional options to the product to enable specific behaviors.
Note: Due to limitations on Android logcat message size, pings larger than 4KB are broken into multiple log messages when using
For example, to direct a release build of the Glean sample application to (1) dump pings to logcat, (2) tag the ping with the
test-metrics-ping tag, and (3) send the "metrics" ping immediately, the following command can be used:
adb shell am start -n org.mozilla.samples.gleancore/mozilla.telemetry.glean.debug.GleanDebugActivity \ --ez logPings true \ --es sendPing metrics \ --es debugViewTag test-metrics-ping
logPings command doesn't trigger ping submission and you won't see any output until a ping has been sent. You can use the
sendPing command to force a ping to be sent, but it could be more desirable to trigger the pings submission on their normal schedule. For instance, the
events pings can be triggered by moving the app out of the foreground and the
metrics ping can be triggered normally if it is overdue for the current calendar day.
Note: The device or emulator must be connected to the internet for this to work. Otherwise the job that sends the pings won't be triggered.
Options that are set using the
adb flags are not immediately reset and will
persist until the application is closed or manually reset.
When running a Glean SDK-powered app in the Android emulator or on a device connected to your computer via cable, there are several ways to read the log output.
Android Studio can show the logs of a connected emulator or device. To display the log messages for an app:
- Run an app on your device.
- Click View > Tool Windows > Logcat (or click Logcat in the tool window bar).
The Logcat window will show all log messages and allows to filter those by the application ID.
Select the application ID of the product you're debugging.
You can also filter by
More information can be found in the View Logs with Logcat help article.
On the command line you can show all of the log output using:
This is the unfiltered output of all log messages.
You can match for
glean using grep:
adb logcat | grep -i glean
A simple way to filter for only the application that is being debugged is by using pidcat, a wrapper around
adb, which adds colors and proper filtering by application ID and log level.
Run it like this to filter for an application:
In the above
[applicationId] is the product's application id as defined in the manifest file and/or build script. For the Glean sample application, this is
org.mozilla.samples.gleancore for a release build and
org.mozilla.samples.gleancore.debug for a debug build.