-
Notifications
You must be signed in to change notification settings - Fork 64
Documentation for data export #475
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
Conversation
The latest updates on your projects. Learn more about Vercel for Git ↗︎
|
|
||
An export can be launched to target a specific LangSmith project and date range. Once a batch export is launched, our system will handle the orchestration and resilience of the export process. | ||
Please note that exporting your data may take some time depending on the size of your data. We also have a limit on how many of your exports can run at the same time. | ||
There is a also a limit of one day of runtime per export job. |
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 would change the wording here since "timeouts" are the more common term. Maybe "bulk exports have a timeout of 24 hours."
|
||
### Destinations - Providing a S3 bucket | ||
|
||
To export LangSmith data, you will need to provide a S3 bucket where the data will be exported to. |
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.
To export LangSmith data, you will need to provide a S3 bucket where the data will be exported to. | |
To export LangSmith data, you will need to provide an S3 bucket where the data will be exported to. |
88354e2
to
88fcc58
Compare
No description provided.