Config: Need to provide mechanism for gating gathering and submission of specific telemetry types #33
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
|
The config support for this has been implemented in #36 |
# for free
to join this conversation on GitHub.
Already have an account?
# to comment
Related to #31, we will additionally need a way for the config to specify telemetry types that should be allowed, or shouldn't be allowed.
Possibly as simple as specifying a whitelist and a blacklist, but will need to review potential options as part of implementing this feature.
Precedence will also need to be clearly defined, i.e. if we list a telemetry type as both allowed and disallowed, which setting takes precedence.
Similarly we will have to decide precedence of the telemetry class versus telemetry type gating, e.g. can we disallow a mandatory class telemetry type?
The text was updated successfully, but these errors were encountered: