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

Extend OAS-Telemetry Configuration to Support APIKEY and Additional Settings #5

Open
4 tasks
motero2k opened this issue Nov 6, 2024 · 0 comments
Open
4 tasks
Assignees

Comments

@motero2k
Copy link
Collaborator

motero2k commented Nov 6, 2024

Extend the OAS-Telemetry configuration to include an APIKEY.

Add the following configurations:

  • An environment variable OASTLM_MODULE_ENABLED (if not set to true, the module should not be loaded).
  • An activation setting at startup (if true, the module will start logging traces upon initialization; if false, it must be manually activated via API or UI to begin logging traces).

Extend the UI to allow specifying the APIKEY on the login page. This may require a /check endpoint.

Tasks:

  • Add support for the OASTLM_MODULE_ENABLED environment variable to control module loading.
  • Implement startup configuration to auto-activate trace logging (based on a boolean value).
  • Modify the UI to allow input of the APIKEY during the login process.
  • Create or update the /check endpoint for APIKEY validation.
@motero2k motero2k self-assigned this Nov 6, 2024
@motero2k motero2k converted this from a draft issue Nov 6, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
Status: Next Actions
Development

No branches or pull requests

1 participant