Reduce Time to Value for Data Observability

Discover how our revamped Config module speeds up data observability implementation, helping organizations achieve quick and efficient results.

By

Melanie Yong

Updated on

October 28, 2024

Many data observability solutions on the market today require manual writing of tests and their individual test settings, which can make it time-consuming to get started. This can be a barrier for organizations with large number of data sources and assets that are looking to quickly implement data observability and start reaping the benefits of improved data quality.

As a result of these challenges, it can take weeks or even months for organizations to implement data observability and start seeing the benefits. The good news is that in the new generation of data observability solutions, the setup process of monitoring does not need extensive manual configuration. Features that aid the process of quick setup time are pre-built tests, auto-threshold settings for monitoring with intelligent ML models and the ability to pre-train monitors with historical data to shorten the training period.

Our platform now supports all of these, plus more in this feature-packed update which we’ve rolled into a new module called the Config. This is the first article of a two-part update on the Config.

Unified Platform, Unified Monitoring

One of the most popular feature requests from our users is the ability to access and manage all monitors from one screen, so that they can have a very quick overview of what checks are running in the moment. So we introduced two things: A landing page to set up monitoring where you are led into the quick set up process for each monitor, and also one page where you can see all active monitors in your account. 

Landing page to all tests you can set up in decube.

The All monitors page is a great way to have a quick look and filter the active monitors based on their statuses, types of tests being run and the data source. This can help you to quickly identify any monitors that are failing or that need attention.

All active monitors in one view.

Define Incident Levels for each monitor 

A job failure for some transformation jobs you’re monitoring in dbt may be a lot less important than the few you actually want to pay attention to. Now, for each monitor you’ve set up in your data source, you can set different incident levels for each monitor. With levels such as “Info”, “Warning” and “Critical”, you get incidents in decube and to your notifications with the appropriate incident level so you can quickly judge the priority of attending to a specific incident.

Each incident now comes with their appropriate Incident Level.

More Control on Schema Drift tests 

When you connect your data source, we’re already turning on the monitoring for your schemas to ensure full coverage on any schema change type that may cause downstream failure. However, we’ve made it even better by allowing you to define which schema change type that you’ll want to alert you, and also disable any schema that you would not need to be monitored. 

Control which schema change type to receive notifications on.

So, you can set table addition of less importance by only defining it as “Info” and not get alerted on it, while setting column deletions at “Warning” for certain schemas. 

Bulk Addition of Field Health tests

Instead of needing to add one test to one column at a time, we now support the bulk addition of a test type across multiple fields. This helps you to add coverage of our out-of-the-box tests like null, duplicate and cardinality tests and apply the same settings across to multiple columns in a table. This saves you a significant amount of time, especially if you have a large number of columns to test.

Bulk addition of Field Health monitoring tests.

This works well with our “Enable Machine Learning” feature where instead of defining manual thresholds, you can use this to let our ML model calculate the thresholds based on yours scanned metrics.

Alert notifications that matter to who receives it

From a day to day basis, teams get bombarded with alerts from different tools all the time, which interrupts the focus time one needs and attend to the alert. So, one of the significant changes to our alert system is the ability to send individual custom alerts to those who would need to receive it. 

Set up custom alerts for each monitor.

For example, for Airflow job failures, you may want to send it directly to a #job-failures Slack channel where there’s a limited audience of engineers who are able to access and troubleshoot on Airflow. You can do this by heading into any monitor and set custom alerts and input the channel name directly.

Example of a null percentage incident triggered to Slack.

Each alert notification has been improved as well to also include a link directly to our new Incident Details which provides a lot of information on the incident trend, and metrics from the failed test that generated the incident.

Optimize the training period for your monitors

When you start a monitor, it usually takes about 3-5 days depending on the frequency of your table updates to generate the ML model for thresholding before the first incident is triggered. However, if you enable our smart training capability, you’ll be able to reduce this training period significantly, as the monitor is able to scan historical data on your table and generate the model for the thresholds, and start triggering incidents early. 

If you enable a lookback period (eg. 7 days, 14 days and 30 days), you’ll also be able to see the scanned metrics in the Asset Details for the period that you had enabled the lookback on, and check whether there were any anomalies in your data before you enabled the monitoring on it. 

See the scanned metrics right in the monitor details when you click on each monitor.

Check out the updates today.

All the above updates were rolled out to our users this week. If you’ll like to see it for yourself, you can sign up for a 30 day trial or request for access to our sandbox account here.

What’s next? Here’s a sneak peek for the second part of our Config update: I’ll be talking about a new type of monitor that we’ve added to our platform. To stay up to date, follow our Linkedin page.

What is a Data Trust Platform in financial services?
A Data Trust Platform is a unified framework that combines data observability, governance, lineage, and cataloging to ensure financial institutions have accurate, secure, and compliant data. In banking, it enables faster regulatory reporting, safer AI adoption, and new revenue opportunities from data products and APIs.
Why do AI initiatives fail in Latin American banks and fintechs?
Most AI initiatives in LATAM fail due to poor data quality, fragmented architectures, and lack of governance. When AI models are fed stale or incomplete data, predictions become inaccurate and untrustworthy. Establishing a Data Trust Strategy ensures models receive fresh, auditable, and high-quality data, significantly reducing failure rates.
What are the biggest data challenges for financial institutions in LATAM?
Key challenges include: Data silos and fragmentation across legacy and cloud systems. Stale and inconsistent data, leading to poor decision-making. Complex compliance requirements from regulators like CNBV, BCB, and SFC. Security and privacy risks in rapidly digitizing markets. AI adoption bottlenecks due to ungoverned data pipelines.
How can banks and fintechs monetize trusted data?
Once data is governed and AI-ready, institutions can: Reduce OPEX with predictive intelligence. Offer hyper-personalized products like ESG loans or SME financing. Launch data-as-a-product (DaaP) initiatives with anonymized, compliant data. Build API-driven ecosystems with partners and B2B customers.
What is data dictionary example?
A data dictionary is a centralized repository that provides detailed information about the data within an organization. It defines each data element—such as tables, columns, fields, metrics, and relationships—along with its meaning, format, source, and usage rules. Think of it as the “glossary” of your data landscape. By documenting metadata in a structured way, a data dictionary helps ensure consistency, reduces misinterpretation, and improves collaboration between business and technical teams. For example, when multiple teams use the term “customer ID”, the dictionary clarifies exactly how it is defined, where it is stored, and how it should be used. Modern platforms like Decube extend the concept of a data dictionary by connecting it directly with lineage, quality checks, and governance—so it’s not just documentation, but an active part of ensuring data trust across the enterprise.
What is an MCP Server?
An MCP Server stands for Model Context Protocol Server—a lightweight service that securely exposes tools, data, or functionality to AI systems (MCP clients) via a standardized protocol. It enables LLMs and agents to access external resources (like files, tools, or APIs) without custom integration for each one. Think of it as the “USB-C port for AI integrations.”
How does MCP architecture work?
The MCP architecture operates under a client-server model: MCP Host: The AI application (e.g., Claude Desktop or VS Code). MCP Client: Connects the host to the MCP Server. MCP Server: Exposes context or tools (e.g., file browsing, database access). These components communicate over JSON‑RPC (via stdio or HTTP), facilitating discovery, execution, and contextual handoffs.
Why does the MCP Server matter in AI workflows?
MCP simplifies access to data and tools, enabling modular, interoperable, and scalable AI systems. It eliminates repetitive, brittle integrations and accelerates tool interoperability.
How is MCP different from Retrieval-Augmented Generation (RAG)?
Unlike RAG—which retrieves documents for LLM consumption—MCP enables live, interactive tool execution and context exchange between agents and external systems. It’s more dynamic, bidirectional, and context-aware.
What is a data dictionary?
A data dictionary is a centralized repository that provides detailed information about the data within an organization. It defines each data element—such as tables, columns, fields, metrics, and relationships—along with its meaning, format, source, and usage rules. Think of it as the “glossary” of your data landscape. By documenting metadata in a structured way, a data dictionary helps ensure consistency, reduces misinterpretation, and improves collaboration between business and technical teams. For example, when multiple teams use the term “customer ID”, the dictionary clarifies exactly how it is defined, where it is stored, and how it should be used. Modern platforms like Decube extend the concept of a data dictionary by connecting it directly with lineage, quality checks, and governance—so it’s not just documentation, but an active part of ensuring data trust across the enterprise.
What is the purpose of a data dictionary?
The primary purpose of a data dictionary is to help data teams understand and use data assets effectively. It provides a centralized repository of information about the data, including its meaning, origins, usage, and format, which helps in planning, controlling, and evaluating the collection, storage, and use of data.
What are some best practices for data dictionary management?
Best practices for data dictionary management include assigning ownership of the document, involving key stakeholders in defining and documenting terms and definitions, encouraging collaboration and communication among team members, and regularly reviewing and updating the data dictionary to reflect any changes in data elements or relationships.
How does a business glossary differ from a data dictionary?
A business glossary covers business terminology and concepts for an entire organization, ensuring consistency in business terms and definitions. It is a prerequisite for data governance and should be established before building a data dictionary. While a data dictionary focuses on technical metadata and data objects, a business glossary provides a common vocabulary for discussing data.
What is the difference between a data catalog and a data dictionary?
While a data catalog focuses on indexing, inventorying, and classifying data assets across multiple sources, a data dictionary provides specific details about data elements within those assets. Data catalogs often integrate data dictionaries to provide rich context and offer features like data lineage, data observability, and collaboration.
What challenges do organizations face in implementing data governance?
Common challenges include resistance from business teams, lack of clear ownership, siloed systems, and tool fragmentation. Many organizations also struggle to balance strict governance with data democratization. The right approach involves embedding governance into workflows and using platforms that unify governance, observability, and catalog capabilities.
How does data governance impact AI and machine learning projects?
AI and ML rely on high-quality, unbiased, and compliant data. Poorly governed data leads to unreliable predictions and regulatory risks. A governance framework ensures that data feeding AI models is trustworthy, well-documented, and traceable. This increases confidence in AI outputs and makes enterprises audit-ready when regulations apply.
What is data governance and why is it important?
Data governance is the framework of policies, ownership, and controls that ensure data is accurate, secure, and compliant. It assigns accountability to data owners, enforces standards, and ensures consistency across the organization. Strong governance not only reduces compliance risks but also builds trust in data for AI and analytics initiatives.
What is the difference between a data catalog and metadata management?
A data catalog is a user-facing tool that provides a searchable inventory of data assets, enriched with business context such as ownership, lineage, and quality. It’s designed to help users easily discover, understand, and trust data across the organization. Metadata management, on the other hand, is the broader discipline of collecting, storing, and maintaining metadata (technical, business, and operational). It involves defining standards, policies, and processes for metadata to ensure consistency and governance. In short, metadata management is the foundation—it structures and governs metadata—while a data catalog is the application layer that makes this metadata accessible and actionable for business and technical users.
What features should you look for in a modern data catalog?
A strong catalog includes metadata harvesting, search and discovery, lineage visualization, business glossary integration, access controls, and collaboration features like data ratings or comments. More advanced catalogs integrate with observability platforms, enabling teams to not only find data but also understand its quality and reliability.
Why do businesses need a data catalog?
Without a catalog, employees often struggle to find the right datasets or waste time duplicating efforts. A data catalog solves this by centralizing metadata, providing business context, and improving collaboration. It enhances productivity, accelerates analytics projects, reduces compliance risks, and enables data democratization across teams.
What is a data catalog and how does it work?
A data catalog is a centralized inventory that organizes metadata about data assets, making them searchable and easy to understand. It typically extracts metadata automatically from various sources like databases, warehouses, and BI tools. Users can then discover datasets, understand their lineage, and see how they’re used across the organization.
What are the key features of a data observability platform?
Modern platforms include anomaly detection, schema and freshness monitoring, end-to-end lineage visualization, and alerting systems. Some also integrate with business glossaries, support SLA monitoring, and automate root cause analysis. Together, these features provide a holistic view of both technical data pipelines and business data quality.
How is data observability different from data monitoring?
Monitoring typically tracks system metrics (like CPU usage or uptime), whereas observability provides deep visibility into how data behaves across systems. Observability answers not only “is something wrong?” but also “why did it go wrong?” and “how does it impact downstream consumers?” This makes it a foundational practice for building AI-ready, trustworthy data systems.
What are the key pillars of Data Observability?
The five common pillars include: Freshness, Volume, Schema, Lineage, and Quality. Together, they provide a 360° view of how data flows and where issues might occur.
What is Data Observability and why is it important?
Data observability is the practice of continuously monitoring, tracking, and understanding the health of your data systems. It goes beyond simple monitoring by giving visibility into data freshness, schema changes, anomalies, and lineage. This helps organizations quickly detect and resolve issues before they impact analytics or AI models. For enterprises, data observability builds trust in data pipelines, ensuring decisions are made with reliable and accurate information.

Table of Contents

Read other blog articles

Grow with our latest insights

Sneak peek from the data world.

Thank you! Your submission has been received!
Talk to a designer

All in one place

Comprehensive and centralized solution for data governance, and observability.

Thank you! Your submission has been received!
Oops! Something went wrong while submitting the form.
decube all in one image