0.21.0 Release Notes
by Shir ChorevThis version aligns capabilities and versions across Deepchecks Multi-tenant SaaS alongside SageMaker Partner AI Apps, towards the AWS re:Invent launch.
This version aligns capabilities and versions across Deepchecks Multi-tenant SaaS alongside SageMaker Partner AI Apps, towards the AWS re:Invent launch.
This version includes new history field, enhancements to llm properties and improved explainability highlighting, along with more features, demos, stability and performance improvements, that are part of our 0.20.0 release.
New special field: History
For supplying previous historical context, such as chat history. Relevant properties will use the “History” field as additional context for checking property values.

LLM properties bank enhancements
Added new prompts and improved prompt performance. Includes unifying the “Completeness” prompt template into one (Non-Q&A use cases have the “coverage” built-in property for uncovering issues such as a non-complete summary).

Multiple line highlighting for explainability
Now properties such as “Grounded in Context”, “PII”, can display more than one area attributing to the highest/lowest scores, allowing efficient RCA

New demos
Data logging
This version includes expanded explainability for properties, multi-category property support, multi-label classification support, and enhancements to the documentation, along with more features, stability and performance improvements, that are part of our 0.19.0 release.
Highlighting of properties for explainability

Multi-label support for properties and classification use cases

Docs Additions
Updates to Auto-annotation flow and to Steps upload
This version includes improved understanding of your version’s performance with root cause analysis, added visibility the system’s usage, along with more features, stability and performance improvements, that are part of our 0.18.0 release.
Version Insights Enhancements
Explainable insights with analysis, and actionable suggestion. Insights are based on property values. They Can be seen in the "Overview" screen per version, and in "Versions" screen to see application-wide insights with link to the relevant version.

Score Reasoning Breakdown
According to Annotation Reason. Click the “Show breakdown” next to the Score on the Dashboard.

Usage Plan Visibility
Displaying your stats and limits (Applications, Users, Processed data tokens) in the "Usage Tab" in the workspace settings
Improvement to PII Property
Versions Page Updates
Added high level data on version: insights on specific versions, and widget showing the most recent version, best performing one, etc.
Production Overtime View Improvements
Default view now loads time ranges of most recent weeks of data

This version which includes a new overtime view for property values and score for production data, and exciting property related improvements, along with more features, stability and performance improvements, that are part of our 0.17.0 release.
Overtime Production View for Monitoring
In Production Environment, annotation scores and property scores are displayed over time
Timestamps are taken from the "started_at" field for each interaction. If no timestamp was give, current time of upload will be considered as interaction time.
New Property: Information Density
Rerun Annotation Pipeline on Multiple Versions
After uploading a new customized “Auto-Annotation YAML” in the Annotation Config screen, the annotation can now be conveniently rerun on all versions and environment in application, with the “Run Annotation Pipeline” button on the top right.

OpenAI Support for LLM Properties
Improvements to Relevance and Grounded in Context Properties
This version includes improvements to the grounded in context model, explainability for grounded in context and retrieval relevancy properties, supporting GPT-4o in the backend, english translation visibility, along with more features, stability and performance improvements, that are part of our 0.16.0 release.
Updated Model for the Grounded in Context Property
Properties Explainability
Upon click, Grounded in Context displays the least grounded part of output, and similarly Retrieval Relevance marks the most relevant part of the information retrieval.

Updated LLM Reasoning View
LLM reasoning is now viewable upon click
Translation to English is Viewable
GPT-4o Supported in LLM Properties
This version includes SDK usage improvements, monitoring flow with Datadog integration, avoided answer property updates, along with more features, stability and performance improvements, that are part of our 0.15.0 release.
SDK Updates - important note for SDK use of deepchecks-llm-client>=0.15.0
dc_client ) is now created by instantiating DeepchecksLLMClient.log_batch_interactions, now require the app_name, version_name and env_type arguments to enable better control of logged data.Avoided Answer Property
Datadog Monitoring Integration
See full documentation here: Datadog Integration
Deepchecks now suppports seamless integration with Datadog, in order to easily track the metrics over time, view configurable dashboards and receive alerts. This enables Datadog users to have the relevant logs, dashboards and alerts, viewable and configurable all in one place.
Robust Tiers and Usage Tracking
This version includes improvements of using the properties (improved properties screen, multiple columns in data screen, improved retrieval relevance property), output text difference highlighting, visibility for the used tokens, and more features, stability and performance improvements that are part of our 0.14.0 release.
New Properties Screen
Following your feedback, the properties experience was now improved, to enable searching and viewing all properties, no matter their type, conveniently.
Starred properties are the ones that are viewable in the Overview screen. Remove or add them to overview screen from the properties page itself or from the overview page.

Custom properties now support underscores in the property name.
Multiple Columns in Data Screen
You can now choose multiple properties (or similarity) columns to display simultaneously in the data page, allowing to conveniently view multiple values for the interactions.

Improved Retrieval Relevance
Text Difference Highlighting
You can now turn “on” the toggle in the output view when comparing interactions, to highlight the differences between the outputs of the same interaction across two different versions.

Usage Visibility
Token usage in the system is now tracked and displayed in the new “Usage” screens in the workspace settings. The token tracking mechanism will replace the existing limits on the number of interactions uploaded or on calculating LLM properties.

This version includes enhancements to the version comparison, additional similarity metrics: ROUGE and BLUE, expansions to the insights mechanism, and more features, stability and performance improvements that are part of our 0.13.0 release.
Similarity Additions
ROUGE and BLEU metrics are now calculated between the outputs of every two similar interactions across versions (marked by having the same user_interaction_id), in addition to the existing Deepchecks similarity.
In the Data screen and in the Versions screen, the Similarity column can now be used for sorting.

Version Comparison Improvements
New design for Versions Screen, allowing to alternate between environments or expand a single version on click, to see all of its environments. Versions can now be compared across multiple properties.

Version's metadata can be added when creating a new version or editing a version. The version description is viewable upon hover in comparison screen, other fields are viewable upon opening the edit mode.
When choosing to see different interactions across versions, interactions can now be browsed to together (when scrolling and exploring different interaction sections)
Expanded Insights Mechanism
Create Application via SDK
This page includes updates from our 0.12.0 Release, which includes new features, stability and performance improvements.
SDK Breaking ChangesThe api for determining the version and environment the SDK is set to has changed.
Previously as a method:
dc_client.env_type(EnvType.PROD) dc_client.version_name('v1')Now, updating the class member:
dc_client.env_type = EnvType.PROD dc_client.version_name = 'v1'