Aporia Documentation
Get StartedBook a Demo🚀 Cool StuffBlog
V2
V2
  • 📖Aporia Docs
  • 🤗Introduction
    • Quickstart
    • Support
  • 💡Core Concepts
    • Why Monitor ML Models?
    • Understanding Data Drift
    • Analyzing Performance
    • Tracking Data Segments
    • Models & Versions
  • 🚀Deployment
    • AWS
    • Google Cloud
    • Azure
    • Databricks
    • Offline / On-Prem
    • Platform Architecture
  • 🏠Storing your Predictions
    • Overview
    • Real-time Models (Postgres)
    • Real-time Models (Kafka)
    • Batch Models
    • Kubeflow / KServe
  • 🧠Model Types
    • Regression
    • Binary Classification
    • Multiclass Classification
    • Multi-Label Classification
    • Ranking
  • 🌈Explainability
    • SHAP values
  • 📜NLP
    • Intro to NLP Monitoring
    • Example: Text Classification
    • Example: Token Classification
    • Example: Question Answering
  • 🍪Data Sources
    • Overview
    • Amazon S3
    • Athena
    • BigQuery
    • Databricks
    • Glue Data Catalog
    • Google Cloud Storage
    • PostgreSQL
    • Redshift
    • Snowflake
    • Microsoft SQL Server
    • Oracle
  • ⚡Monitors & Alerts
    • Overview
    • Data Drift
    • Metric Change
    • Missing Values
    • Model Activity
    • Model Staleness
    • Performance Degradation
    • Prediction Drift
    • Value Range
    • Custom Metric
    • New Values
    • Alerts Consolidation
  • 🎨Dashboards
    • Overview
  • 🤖ML Monitoring as Code
    • Getting started
    • Adding new models
    • Data Segments
    • Custom metrics
    • Querying metrics
    • Monitors
    • Dashboards
  • 📡Integrations
    • Slack
    • Webhook
    • Teams
    • Single Sign On (SAML)
    • Cisco
  • 🔐Administration
    • Role Based Access Control (RBAC)
  • 🔑API Reference
    • REST API
    • API Extended Reference
    • Custom Segment Syntax
    • Custom Metric Syntax
    • Code-Based Metrics
    • Metrics Glossary
  • ⏩Release Notes
    • Release Notes 2024
    • Release Notes 2023
Powered by GitBook
On this page
  • Example: Boolean Decision without Probability
  • Example: Boolean Decision with Probability
  • Example: Probability Only
  1. Model Types

Binary Classification

PreviousRegressionNextMulticlass Classification

Last updated 2 years ago

Binary classification models predict a binary outcome (one of two possible classes). In Aporia, these models are represented by the binary model type.

Examples of binary classification problems:

  • Will the customer buy this product or not_buy this product?

  • Is this email spam or not_spam?

  • Is this review written by a customer or a robot?

Frequently, binary models output not only a yes/no answer, but also a probability.

Example: Boolean Decision without Probability

If you have a model with a yes/no decision but without a probability value, then your database may look like the following:

id
feature1 (numeric)
feature2 (boolean)
decision (boolean)
label (boolean)
timestamp (datetime)

1

13.5

True

True

True

2014-10-19 10:23:54

2

-8

False

False

True

2014-10-19 10:24:24

To integrate this type of model follow our , and during the schema mapping remember to include a boolean prediction field and boolean actual field and linked them together.

Check out the for more information about how to connect from different data sources.

Example: Boolean Decision with Probability

If you have a model with a yes/no decision and a probability / confidence value for it, then your database may look like the following:

id
feature1 (numeric)
feature2 (boolean)
proba (numeric)
decision (boolean)
label (boolean)
timestamp (datetime)

1

13.5

True

0.8

True

True

2014-10-19 10:23:54

2

-8

False

0.5

False

True

2014-10-19 10:24:24

To integrate this type of model follow our , and during the schema mapping remember to include a boolean prediction, a proba numeric prediction and boolean actual field and linked them together. In case you want to link both the proba and the boolean prediction to the actual field, just add a duplicate of the actual column in the query defining the dataset, so you'll have 2 actual fields in your schema and link each of them to one of the prediction fields.

Example: Probability Only

In cases when there is no threshold for your boolean prediction, and the final business result is actually a probability, you may simply omit the decision field from the examples in the previous section and only include the proba field for your prediction.

Check out the for more information about how to connect from different data sources.

🧠
Quickstart
data sources section
Quickstart
data sources section