Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

SDK: Add library interfaces to support external workflows pre-registering telemetry clients #7

Open
rtamalin opened this issue Jun 4, 2024 · 0 comments
Labels
Config enhancement New feature or request SDK

Comments

@rtamalin
Copy link
Collaborator

rtamalin commented Jun 4, 2024

A registered telemetry client expects the following values to be configured:

  • upstream telemetry server
  • client instance id
  • client credentials, consisting of the client id and the auth token
  • optional customer id

If a telemetry client self-registers, it will automatically generate a client instance id, and use it to perform a client registration with the configured upstream server, defaulting to the primary SUSE Telemetry Gateway server, to obtain the client credentials.

If a telemetry client is being pre-registered using by an external product registration workflow, then these values will need to be configured appropriately by the associated tools, e.g. suseconnect.

To assist with integrating with external tools the telemetry library SDK should provide the following calls:

  • GetUpstreamServer(), SetUpstreamServer()
  • GetClientInstanceId(), SetClientInstanceId()
  • GetClientCredentials(), SetClientCredentials()
  • GetCustomerId(), SetCustomerId()
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Config enhancement New feature or request SDK
Projects
None yet
Development

No branches or pull requests

1 participant