EosMetrics.EventRecorder.prototype.record_event
function record_event(event_id: String, auxiliary_payload: GLib.Variant): void {
// Gjs wrapper for emtr_event_recorder_record_event()
}
Make a best-effort to record the fact that an event of type event_id happened at the current time. Optionally, associate arbitrary data, auxiliary_payload, with this particular instance of the event. Under no circumstances should personally-identifiable information be included in the auxiliary_payload or event_id. Large auxiliary payloads dominate the size of the event and should therefore be used sparingly. Events for which precise timing information is not required should instead be recorded using EosMetrics.EventRecorder.prototype.record_events to conserve bandwidth.
At the discretion of the metrics system, the event may be discarded before being reported to the metrics server. The event may take arbitrarily long to reach the server and may be persisted unencrypted on the client for arbitrarily long. There is no guarantee that the event is delivered via the network; for example, it may instead be delivered manually on a USB drive. No indication of successful or failed delivery is provided, and no application should rely on successful delivery. The event will not be aggregated with other events before reaching the server.
- event_id
an RFC 4122 UUID representing the type of event that took place
- auxiliary_payload
miscellaneous data to associate with the event. Must not contain maybe variants as they are not compatible with D-Bus.