SDK: Telemetry Client Library Generate() should include a flags parameter #32
Labels
Comments
rtamalin
added a commit
that referenced
this issue
Jul 19, 2024
Add a telemetry package to the repo top-level directory that defines the client interfaces that should be used by applications integrating with the SUSE Telemetry Client to generate telemetry. The telemetry package defines the following interfaces: * Generate() - can be called by telemetry providers to "generate" telemetry. * Status() - can be used by telemetry providers to check the status of the telemetry client. Enhance the telemetry client config to support specifing enablement state for the opt-out and opt-in telemetry classes, and allow and deny lists for specific telemetry types. Add new types and associated helper methods, to support the telemetry client interfaces: * TelemetryClass - specifies mandatory, opt-out or opt-in classes of telemetry. * GenerateFlags - flags that control how the Generate() interface handles provided telemetry. Updated the examples directory contents, including adding an example Go app leveraging the telemetry client interfaces to generate telemetry and check the status of the telemetry client. Updated various config files and embedded config settings to reflect recent logging support changes and add class_options settings; they should all now be pretty consistent in their content. Updated the cmd/generator and cmd/clientds tools to setup logging. Relates: #15 #30 #31 #32 #33
|
Most of the work is done for this, however support for handling the submit flag being set isn't currently implemented. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
This parameter should support specify flags to indicate that immediate submission is requested rather than just storing the telemetry data item in the telemetry client data store for later submission as part of the background activity.
The text was updated successfully, but these errors were encountered: