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

feat: add kill switch for client metrics #4829

Merged
merged 5 commits into from
Sep 26, 2023
Merged

Conversation

FredrikOseberg
Copy link
Contributor

@FredrikOseberg FredrikOseberg commented Sep 25, 2023

This PR adds a killswitch for client metrics that we can use to disable metrics in our cloud offering.

Discussion points:

  • Is it ok for us to change the response code to 204 when we disable the metrics? Is there a better way?

@vercel
Copy link

vercel bot commented Sep 25, 2023

The latest updates on your projects. Learn more about Vercel for Git ↗︎

Name Status Preview Comments Updated (UTC)
unleash-monorepo-frontend ✅ Ready (Inspect) Visit Preview 💬 Add feedback Sep 26, 2023 7:20am
1 Ignored Deployment
Name Status Preview Comments Updated (UTC)
unleash-docs ⬜️ Ignored (Inspect) Visit Preview Sep 26, 2023 7:20am

Copy link
Contributor

@kwasniew kwasniew left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I understand that we distinguish 204 and 202 so that client can tell whether the feature is enabled or disabled right?

@FredrikOseberg
Copy link
Contributor Author

FredrikOseberg commented Sep 25, 2023

I understand that we distinguish 204 and 202 so that client can tell whether the feature is enabled or disabled right?

That's the idea. Although the clients don't support this for now, it would be a way for us in the future to distinguish the responses. Though this implementation detail is up for discussion.

@FredrikOseberg FredrikOseberg merged commit b919c44 into main Sep 26, 2023
15 checks passed
@FredrikOseberg FredrikOseberg deleted the feat/metrics-kill-switch branch September 26, 2023 07:37
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
Archived in project
Development

Successfully merging this pull request may close these issues.

None yet

2 participants