-
Notifications
You must be signed in to change notification settings - Fork 46
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
Update debugging.mdx #2227
base: main
Are you sure you want to change the base?
Update debugging.mdx #2227
Conversation
@@ -57,6 +57,22 @@ For server SDKs, these reasons for the value you are seeing can be: | |||
- `Unrecognized`: the sdk was initialized, but this config did not exist in the set of values | |||
- `Uninitialized`: the sdk was not yet successfully initialized | |||
|
|||
In newer server SDKs, the reasons will be a combination of initialization source and evaluation reason: |
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.
Mmmm. At first I wanted to combine all of this but I see why its separate. Can you make a heading for the client and server sdk sections?
So
Client SDK Reasons
Server SDK Reasons
|
||
## SDK Event Handling and Minimizing Event Loss | ||
|
||
The SDK batches and flushes events in the background to our server. When the volume of incoming events exceeds the SDK's flushing capacity, some events may be dropped after a certain number of retries. To reduce the chances of event loss, you can adjust several settings in the Statsig options: |
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.
this only applies to python at the moment. Id document it in the python sdk docs instead of in a generic debugging section. If you do leave it here, then it should specify which sdk type/version it applies to
- `Network` | ||
- `Bootstrap` | ||
- `DataAdapter` | ||
- `Uninitialized` | ||
- `StatsigNetwork`: this refers to when custom proxy/grpc streaming has triggered the fallback behavior, thus falling back to statsig api. | ||
* If no network config/overrides were used, the sdk default uses statsig apis but the reason will be Network. | ||
|
||
Evaluation Reason | ||
- `LocalOverride` | ||
- `Unrecognized` | ||
- `Unsupported` |
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.
either add a definition for each of them, or none of them. In this case, each of them would be best
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.
the definition for the rest of them are above, i only added for the new ones we introduced in v2. I re-listed them these enums have been shifted to reason vs source
No description provided.