Implement telemetry client interfaces #36
Merged
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
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:
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:
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