Update docs for new set usage limits flow #1351
Closed
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Growth eng team work by Arjun, Hana, Jess. Jess to send new screenshots in docs channel
katmayb
approved these changes
Nov 10, 2025
| <Note> | ||
| For backwards compatibility, older organizations may have this defaulted to **Extended**. Organizations created after June 3rd, 2024 have this defaulted to **Base**. | ||
| </Note> | ||
| You can checkbox if you'd like to apply your data retention setting to all existing traces in your workspace. If unchecked, your retention setting will only apply to new traces. |
Contributor
There was a problem hiding this comment.
Suggested change
| You can checkbox if you'd like to apply your data retention setting to all existing traces in your workspace. If unchecked, your retention setting will only apply to new traces. | |
| You can check the box if you'd like to apply your data retention setting to all existing traces in your workspace. If unchecked, your retention setting will only apply to new traces. |
| LangSmith has two usage limits: total traces and extended retention traces. These correspond to the two metrics tracked on the [usage graph](#usage-graph). You can use these in tandem to have granular control over spend. | ||
|
|
||
| To set limits, navigate back to **Settings** -> **Usage and Billing** -> **Usage configuration**. There is a table at the bottom of the page that lets you set usage limits per workspace. For each workspace, the two limits appear, along with a cost estimate: | ||
| To set limits, navigate back to **Settings** -> **Usage and Billing** -> **Usage configuration**. Input a spend limit, and we will imply a number of base and extended traces. Move the slider to set the trace limits to your desired numbers. |
Contributor
There was a problem hiding this comment.
Instead of "we" can you change to "LangSmith will..."
Suggested change
| To set limits, navigate back to **Settings** -> **Usage and Billing** -> **Usage configuration**. Input a spend limit, and we will imply a number of base and extended traces. Move the slider to set the trace limits to your desired numbers. | |
| To set limits, navigate back to **Settings** -> **Usage and Billing** -> **Usage configuration**. Input a spend limit, and LangSmith will determine a number of base and extended traces. Move the slider to set the trace limits to your desired numbers. |
"imply" seems indirect, maybe "determine" or "allocate" or "set"
| To set limits, navigate back to **Settings** -> **Usage and Billing** -> **Usage configuration**. There is a table at the bottom of the page that lets you set usage limits per workspace. For each workspace, the two limits appear, along with a cost estimate: | ||
| To set limits, navigate back to **Settings** -> **Usage and Billing** -> **Usage configuration**. Input a spend limit, and we will imply a number of base and extended traces. Move the slider to set the trace limits to your desired numbers. | ||
|
|
||
| Note that if you have more than one workspace, your free monthly traces are by default allocated to your first workspace. |
Contributor
There was a problem hiding this comment.
Suggested change
| Note that if you have more than one workspace, your free monthly traces are by default allocated to your first workspace. | |
| Note that if you have more than one workspace, by default your free monthly traces are allocated to your first workspace. |
| Click on the edit icon on the right side of the table for the **Prod** row to enter the limit. | ||
|
|
||
|  | ||
| Click on the edit icon in the table for the **Prod** row to enter the limit. You can drag the slider to determine the maximum limits for each trace type. In the example below, we show the spend limit allocated towards only base retention traces. |
Contributor
There was a problem hiding this comment.
Suggested change
| Click on the edit icon in the table for the **Prod** row to enter the limit. You can drag the slider to determine the maximum limits for each trace type. In the example below, we show the spend limit allocated towards only base retention traces. | |
| Click on the edit icon in the table for the **Prod** row to enter the limit. You can drag the slider to determine the maximum limits for each trace type. The following example shows the spend limit allocated toward only base retention traces. |
| #### Cut maximum spend with an extended data retention limit | ||
|
|
||
| From [Optimization 1](#optimization-1-manage-data-retention), you learned that the easiest way to cut cost was through managing data retention. The same is true for limits. If you only want to keep roughly 10% of traces to be around more than 14 days, you can set a limit on the maximum high retention traces you can keep. This would result in `.10 * 7,800,000 = 780,000`. | ||
| From [Optimization 1](#optimization-1-manage-data-retention), you learned that the easiest way to cut cost was through managing data retention. The same is true for limits. If you only want to keep a certain percentage of traces to be around more than 14 days, you can set a limit on the maximum high retention traces you can keep by dragging the slider. |
Contributor
There was a problem hiding this comment.
Suggested change
| From [Optimization 1](#optimization-1-manage-data-retention), you learned that the easiest way to cut cost was through managing data retention. The same is true for limits. If you only want to keep a certain percentage of traces to be around more than 14 days, you can set a limit on the maximum high retention traces you can keep by dragging the slider. | |
| From [Optimization 1](#optimization-1-manage-data-retention), you learned that the easiest way to cut cost was through managing data retention. The same is true for limits. If you only want to keep a certain percentage of traces to be retained for more than 14 days, you can set a limit on the maximum high retention traces you can keep by dragging the slider. |
Contributor
|
I'll add in the images now |
katmayb
reviewed
Nov 10, 2025
|
|
||
| 1. Click **Set up Billing**. | ||
| 1. Add your credit card information. After this step, you will no longer be rate limited to 5000 traces, and you will be charged for any excess traces at rates specified on the [pricing](https://www.langchain.com/pricing-langsmith) page. | ||
| 2. Add your credit card information. After this step, you will no longer be rate limited to 5,000 traces, and you will be charged for any excess traces at rates specified on the [pricing](https://www.langchain.com/pricing-langsmith) page. |
Contributor
There was a problem hiding this comment.
Suggested change
| 2. Add your credit card information. After this step, you will no longer be rate limited to 5,000 traces, and you will be charged for any excess traces at rates specified on the [pricing](https://www.langchain.com/pricing-langsmith) page. | |
| 1. Add your credit card information. After this step, you will no longer be rate limited to 5,000 traces, and you will be charged for any excess traces at rates specified on the [pricing](https://www.langchain.com/pricing-langsmith) page. |
In markdown, we want to convert numbered lists to just be 1. ,1., 1. Markdown renders as a numbered list automatically. This future proofs docs so that if someone removes an item and forgets to adjust the numbering, it doesn't matter.
Contributor
|
@jessicaou I couldn't pull in your branch locally, so I've opened a new PR with your changes and incorporated my suggestions (all minor). I've added one screenshot where it was clear where it should go, but need your input on placement of the others. Closing this PR in favor of #1355 |
lc-arjun
added a commit
that referenced
this pull request
Nov 11, 2025
Copy of #1351 ## Preview https://langchain-5e9cc07a-preview-growth-1762871756-20d6a93mintlify.app/langsmith/billing --------- Co-authored-by: Arjun Natarajan <arjun@langchain.dev>
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Overview
Growth eng team work by Arjun, Hana, Jess. Jess to send new screenshots in docs channel
Type of change
Type: Update existing documentation
