-
Notifications
You must be signed in to change notification settings - Fork 210
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
WIP: Initial draft of telemetry #3822
Conversation
👷 Deploy Preview for chef-server processing.
|
da9ff9e
to
3096fa3
Compare
Signed-off-by: sreepuramsudheer <[email protected]>
3096fa3
to
572384a
Compare
Quality Gate passedIssues Measures |
SonarQube Quality Gate |
|
||
-spec token() -> string() | atom(). | ||
token() -> | ||
case chef_secrets:get(<<"data_collector">>, <<"token">>) of |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Why are we using data_collector token in telemetry ?
|
||
-spec is_enabled() -> boolean(). | ||
is_enabled() -> | ||
case application:get_env(chef_telemetry, root_url) of |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Are we handling empty string cases/invalid url cases ?
Do we need to include this telemetry status in health api ?
Description
[Please describe what this change achieves]
Issues Resolved
[List any existing issues this PR resolves, or any Discourse or
StackOverflow discussions that are relevant]
Check List