- Notifications
You must be signed in to change notification settings - Fork70
Updating headers + tracing project CTAs#892
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 ourterms of service andprivacy statement. We’ll occasionally send you account related emails.
Already on GitHub?Sign in to your account
base:main
Are you sure you want to change the base?
Uh oh!
There was an error while loading.Please reload this page.
Conversation
vercelbot commentedJul 8, 2025 • edited
Loading Uh oh!
There was an error while loading.Please reload this page.
edited
Uh oh!
There was an error while loading.Please reload this page.
The latest updates on your projects. Learn more aboutVercel 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.
Hey@tanushree-sharma, I left some brief comments, I don't have access to the UI so I haven't been able to cross-check things.
| We navigate to `Projects` -> `<your project name>`, click the data retention drop down, and modify it to base retention. As | ||
| with the organization level setting, this will only affect retention (and pricing) for traces going forward. | ||
| Navigate to **Projects** > **_Your project name_** > Select **Retention** and modify the default rentetion of the project to **Base**. This will only affect retention (and pricing) for **traces going forward**. |
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.
| Navigate to**Projects** >**_Your project name_** > Select**Retention** and modify the defaultrentetion of the project to**Base**. This will only affect retention (and pricing) for**traces going forward**. | |
| Navigate to**Projects** >**_Your project name_** > Select**Retention** and modify the defaultretention of the project to**Base**. This will only affect retention (and pricing) for**traces going forward**. |
| Navigate to the `Usage configuration` tab, and look at our organization level retention settings. Modifying this setting affects all **new projects** that are | ||
| created going forward in all workspaces in our org. |
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.
| Navigate to the`Usage configuration` tab, and look at our organization level retention settings. Modifying this setting affects all**new projects** that are | |
| created going forward in all workspaces in our org. | |
| Navigate to the`Usage configuration` tab to review the organization level retention settings. Modifying this setting will affect all**new projects** that are created in all workspaces in the organization. |
| created going forward in all workspaces in our org. | ||
| :::note | ||
| For backwards compatibility, older organizations may have this defaulted to Extended. Organizations created after June 3rd | ||
| For backwards compatibility, older organizations may have this defaulted to Extended. Organizations created after June 3rd, 2024 |
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.
| For backwards compatibility, older organizations may have this defaulted to Extended. Organizations created after June 3rd, 2024 | |
| For backwards compatibility, older organizations may have this defaulted to**Extended**. Organizations created after June 3rd, 2024 |
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.
What do you think about bolding the retention policy names in the UI?
| created going forward in all workspaces in our org. | ||
| :::note | ||
| For backwards compatibility, older organizations may have this defaulted to Extended. Organizations created after June 3rd | ||
| For backwards compatibility, older organizations may have this defaulted to Extended. Organizations created after June 3rd, 2024 | ||
| have this defaulted to Base. |
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.
| have this defaulted to Base. | |
| have this defaulted to**Base**. |
| We navigate to `Projects` -> `<your project name>`, click the data retention drop down, and modify it to base retention. As | ||
| with the organization level setting, this will only affect retention (and pricing) for traces going forward. | ||
| Navigate to **Projects** > **_Your project name_** > Select **Retention** and modify the default rentetion of the project to **Base**. This will only affect retention (and pricing) for **traces going forward**. | ||
|  | ||
| ### Keep around a percentage of traces for extended data retention |
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.
What do you think about:
Apply extended data retention to a percentage of traces
Or, something similar?
| When an automation rule matches any [run](/observability/concepts#runs) within a [trace](/observability/concepts#traces), the all runs within the trace are upgraded to be retained for 400 days. | ||
| ::: |
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.
Should this say "... then all runs within.."
| #### 3. Configure your rule | ||
| #### 1. Navigate to online evaluators | ||
| Head to the **Tracing Projects** tab and select a tracing project. Click on **+ New** in the top right corner the tracing projectpage, then click on **New Evaluator**. |
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.
| Head to the**Tracing Projects** tab and select a tracing project. Click on**+ New** in the top right corner the tracingprojectpage, then click on**New Evaluator**. | |
| Head to the**Tracing Projects** tab and select a tracing project. Click on**+ New** in the top right cornerofthe tracingproject page, then click on**New Evaluator**. |
| - Runs where a [user left feedback](/evaluation/how_to_guides/attach_user_feedback) indicating he response was unsatisfactory | ||
| - Runs that invoke a specific tool call. See [filtering for tool calls](//observability/how_to_guides/filter_traces_in_application#example-filtering-for-tool-calls) for more information |
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.
| - Runs where a[user left feedback](/evaluation/how_to_guides/attach_user_feedback) indicatinghe response was unsatisfactory | |
| - Runs that invoke a specific tool call. See[filtering for tool calls](//observability/how_to_guides/filter_traces_in_application#example-filtering-for-tool-calls) for more information | |
| - Runs where a[user left feedback](/evaluation/how_to_guides/attach_user_feedback) indicatingthe response was unsatisfactory. | |
| - Runs that invoke a specific tool call. See[filtering for tool calls](//observability/how_to_guides/filter_traces_in_application#example-filtering-for-tool-calls) for more information. |
| - Runs that invoke a specific tool call. See [filtering for tool calls](//observability/how_to_guides/filter_traces_in_application#example-filtering-for-tool-calls) for more information | ||
| - Runs that match a particular piece of metadata (eg. if you log traces with a plan_type and only want to run evaluations on traces from your enterprise customers). See [adding metadata to your traces](/observability/how_to_guides/add_metadata_tags) for more information. | ||
| Filters on evaluators work the same way as filters applied traces in the project. For more information on filters, you can refer to [this guide](./filter_traces_in_application). |
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.
| Filters on evaluators work the same way as filters applied traces in the project. For more information on filters, you can refer to[this guide](./filter_traces_in_application). | |
| Filters on evaluators work the same way as filters appliedtotraces in the project. For more information on filters, you can refer to[this guide](./filter_traces_in_application). |
| ### Configure a LLM-as-a-judge online evaluator | ||
| View this guide to configure on configuring an [LLM-as-a-judge evaluator](/evaluation/how_to_guides/llm_as_judge). | ||
| View this guide to configure on configuring an [LLM-as-a-judge evaluator](/evaluation/how_to_guides/llm_as_judge?mode=ui). |
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.
| View this guide to configureon configuringan[LLM-as-a-judge evaluator](/evaluation/how_to_guides/llm_as_judge?mode=ui). | |
| View this guide to configure an[LLM-as-a-judge evaluator](/evaluation/how_to_guides/llm_as_judge?mode=ui). |
Uh oh!
There was an error while loading.Please reload this page.
Docs updates: