-
-
Notifications
You must be signed in to change notification settings - Fork 658
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
docs: troubleshooting guides #4592
Conversation
The latest updates on your projects. Learn more about Vercel for Git ↗︎
|
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.
I think this is great and can go in as is 🚀 However, I have a few small comments that may be good to address either now or in a follow-up PR.
Again, fantastic work 🙌🏼 I love this ❤️
Co-authored-by: Thomas Heartman <thomas@getunleash.ai>
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.
Thanks @thomasheartman!! great insights as usual 🤗
To confirm how users will have flags resolved, follow these steps: | ||
1. The [Unleash Playground](../reference/playground.mdx Playground reference documentation) was developed with this particular use case in mind. An access token can be used along with context values (passed in via the UI) to see how a flag will be resolved. | ||
2. When using a **gradual rollout** strategy, be mindful of the **[stickiness](../reference/stickiness)** value. When evaluating a flag, if the provided context does not include the field used in the stickiness configuration, the gradual rollout strategy will be evaluated to false.``` | ||
3. If using [Unleash Edge](../reference/unleash-edge) or the [Proxy](../reference/unleash-proxy), consider changing the API endpoint being used by the SDK instance. The SDK and platform may be configured correctly while the intermediary (Edge or Proxy) is somehow malfunctioning. |
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.
@mvittiglio I was reviewing this and I'm not sure I understand:
- Changing the API Endpoint to what value?
- Saying that the intermediate is somehow malfunctioning doesn't help troubleshoot, and most likely it can be a misconfiguration more than a malfunction.
So, maybe you're trying to say to use the Frontend API from the SDK, to be able to tell if the problem is on the SDK or on the configuration of Edge/proxy, can that be?
For now, I'll remove this sentence, and we can add it back in another PR once clarified
About the changes
Adds troubleshooting guides for some common problems under the how-to area (following the diataxis framework).
This is part of Unleash 2023 offsite challenge