LogoLogo
HomeBlogGitHub
latest
latest
  • New DOCS
  • What is Evidently?
  • Get Started
    • Evidently Cloud
      • Quickstart - LLM tracing
      • Quickstart - LLM evaluations
      • Quickstart - Data and ML checks
      • Quickstart - No-code evaluations
    • Evidently OSS
      • OSS Quickstart - LLM evals
      • OSS Quickstart - Data and ML monitoring
  • Presets
    • All Presets
    • Data Drift
    • Data Quality
    • Target Drift
    • Regression Performance
    • Classification Performance
    • NoTargetPerformance
    • Text Evals
    • Recommender System
  • Tutorials and Examples
    • All Tutorials
    • Tutorial - Tracing
    • Tutorial - Reports and Tests
    • Tutorial - Data & ML Monitoring
    • Tutorial - LLM Evaluation
    • Self-host ML Monitoring
    • LLM as a judge
    • LLM Regression Testing
  • Setup
    • Installation
    • Evidently Cloud
    • Self-hosting
  • User Guide
    • 📂Projects
      • Projects overview
      • Manage Projects
    • 📶Tracing
      • Tracing overview
      • Set up tracing
    • 🔢Input data
      • Input data overview
      • Column mapping
      • Data for Classification
      • Data for Recommendations
      • Load data to pandas
    • 🚦Tests and Reports
      • Reports and Tests Overview
      • Get a Report
      • Run a Test Suite
      • Evaluate Text Data
      • Output formats
      • Generate multiple Tests or Metrics
      • Run Evidently on Spark
    • 📊Evaluations
      • Evaluations overview
      • Generate snapshots
      • Run no code evals
    • 🔎Monitoring
      • Monitoring overview
      • Batch monitoring
      • Collector service
      • Scheduled evaluations
      • Send alerts
    • 📈Dashboard
      • Dashboard overview
      • Pre-built Tabs
      • Panel types
      • Adding Panels
    • 📚Datasets
      • Datasets overview
      • Work with Datasets
    • 🛠️Customization
      • Data drift parameters
      • Embeddings drift parameters
      • Feature importance in data drift
      • Text evals with LLM-as-judge
      • Text evals with HuggingFace
      • Add a custom text descriptor
      • Add a custom drift method
      • Add a custom Metric or Test
      • Customize JSON output
      • Show raw data in Reports
      • Add text comments to Reports
      • Change color schema
    • How-to guides
  • Reference
    • All tests
    • All metrics
      • Ranking metrics
    • Data drift algorithm
    • API Reference
      • evidently.calculations
        • evidently.calculations.stattests
      • evidently.metrics
        • evidently.metrics.classification_performance
        • evidently.metrics.data_drift
        • evidently.metrics.data_integrity
        • evidently.metrics.data_quality
        • evidently.metrics.regression_performance
      • evidently.metric_preset
      • evidently.options
      • evidently.pipeline
      • evidently.renderers
      • evidently.report
      • evidently.suite
      • evidently.test_preset
      • evidently.test_suite
      • evidently.tests
      • evidently.utils
  • Integrations
    • Integrations
      • Evidently integrations
      • Notebook environments
      • Evidently and Airflow
      • Evidently and MLflow
      • Evidently and DVCLive
      • Evidently and Metaflow
  • SUPPORT
    • Migration
    • Contact
    • F.A.Q.
    • Telemetry
    • Changelog
  • GitHub Page
  • Website
Powered by GitBook
On this page
  • What changed
  • If your code breaks
  • Migrate to the new version
  • Pre-built report example
  • Custom report example
  • Help
  1. SUPPORT

Migration

How to migrate to the new Evidently API.

This page will help if you get one of the following errors:

  • no module named 'evidently.dashboard'

  • modulenotfounderror: no module named 'evidently.dashboard'

What changed

Starting from Evidently 0.1.59, the old API that uses Dashboards and json profiles was deprecated. This functionality is now available using the Report object.

In Evidently 0.3.0, the old API was removed from the code base.

If your code breaks

If you get an error no module named 'evidently.dashboard' or similar, you might be running the code that uses old API, with a newer Evidently version.

To make sure your existing code that uses Dashboards or json profiles works, fix the Evidently version to 0.2.8 or earlier.

For example, when installing Evidently, specify:

!pip install evidently==0.2.8

You can continue using the older versions and access old documentation, but they are no longer supported.

Migrate to the new version

To make use of all the latest Evidently functionality, including data drift detection and evaluations for text data, embeddings and various new Metrics and Presets, you should migrate to the new API.

Pre-built report example

Here is a quick example of the change.

Previously, to generate a pre-built Data Drift Report, you had to import a Dashboard object and specify the tab. For JSON profile, you needed to create a separate object.

Now, both are unified in a single Report object, and you include a preset instead of a tab. Here is how it works for Data Drift report.

To get a visual HTML report in Jupyter notebook or Colab.

data_drift_report = Report(metrics=[
    DataDriftPreset(),
])

data_drift_report.run(reference_data=ref, current_data=cur)
data_drift_report

To get what was previously as JSON profile (and has now been improved and re-worked!), simply get the Report output as JSON:

data_drift_report.json()

You can also get the output as a Python dictionary.

data_drift_report.as_dict()

Custom report example

You can already easily create custom Reports by listing individual metrics to include. Here is the example code to generate custom report:

data_quality_column_report = Report(metrics=[
    ColumnDistributionMetric(column_name="education"), 
    ColumnQuantileMetric(column_name="education-num", quantile=0.75), 
    ColumnCorrelationsMetric(column_name="education"),
    ColumnValueListMetric(column_name="relationship", values=["Husband", "Unmarried"]), 
    ColumnValueRangeMetric(column_name="age", left=10, right=20),
    
])

Help

PreviousEvidently and MetaflowNextContact

Last updated 2 months ago

To understand the new API, go through the or any of the .

If you want to keep non-aggregated visualization from the earlier Evidently version, set the . It is set to False by default.

If you want to include all the render data in the JSON output, use .

It works the same for all other pre-built Reports that are available as presets. Browse the to see the code.

If you need any help, ask in our .

Getting Started tutorial
sample notebooks
corresponding "raw_data" parameter to True
parameters to include additional information in JSON
sample notebooks
Discord community