Get the essential data observability guide
Download this guide to learn:
What is data observability?
4 pillars of data observability
How to evaluate platforms
Common mistakes to avoid
The ROI of data observability
Unlock now
Thank you! Your submission has been received!
Oops! Something went wrong while submitting the form.
Sign up for a free data observability workshop today.
Assess your company's data health and learn how to start monitoring your entire data stack.
Book free workshop
Sign up for news, updates, and events
Subscribe for free
Thank you! Your submission has been received!
Oops! Something went wrong while submitting the form.
Getting started with Data Observability Guide

Make a plan to implement data observability across your company’s entire data stack

Download for free
Book a data observability workshop with an expert.

Assess your company's data health and learn how to start monitoring your entire data stack.

Book free workshop

Monitor the source with Fivetran observability

Get right to the root cause of data incidents—with all the context you need. Monitor connectors themselves in addition to seeing their effect on downstream tables.

and
August 13, 2024

Co-founder / Engineering

August 13, 2024
Monitor the source with Fivetran observability

How can you treat a symptom without understanding its root cause? 

Think about it: if you go to the doctor with a persistent cough, and the doctor only asks you about the cough (the symptom), they might prescribe cough syrup to suppress it. Sure, you’ll feel better temporarily, but if the underlying cause is something serious, like pneumonia, you’re not actually getting better—you’re just masking the issue.

And the reverse situation is just as bad. If your doctor knows that pneumonia is going around and decides to treat you for it without even asking about your symptoms, they might treat you for the completely wrong thing.

Like a data doctor, you need to look at your data issues from all angles—including the symptoms (what’s visibly wrong in your pipeline) and the causes (the underlying issues leading to those problems). 

Connect the dots from cause to effect

That’s why we launched our Fivetran integration: so you could understand which connectors were upstream of data quality issues.

Metaplane customers love the visibility into what’s currently going on in their pipeline, but wanted more insight into their ETL metrics to answer questions about what might be causing those issues, like:

  • Were fewer rows synced than expected?
  • When was the last time this connector successfully ran?
  • How long is Fivetran taking to sync my data?

Now, it’s possible. Our Fivetran observability now allows you to monitor connectors themselves in addition to seeing their effect on downstream tables.

View the details of all your recent job runs, including connector durations and status.

By extending observability further into your ETL tools, you get right to the root cause of data incidents—with all the context you need.

ETL visibility, unlocked

Our dashboard puts connector performance front and center, so you get all the information you need at a glance. 

See if your connector syncs are behaving normally or if there have been any unusual spikes over the last 7 days.

With a single click, you can:

  • Explore how long each connector takes
  • See how many rows Fivetran synced
  • Check for unusual connector performance spikes
  • Consolidate alerts in one place

A clear picture of your entire pipeline 

Metaplane monitors `connector duration` and `last succeeded at` (i.e. `freshness`) to show you exactly what’s happening with your data. It’s a single point of reference for tracking the health and status of Fivetran.

Dive deep into individual connector performance to pinpoint issues

If a connector starts behaving abnormally and you want to learn more, simply click into that connector. You can view detailed logs that show which tables were synced, the duration of each sync, and any anomalies that occurred for any and all connectors.

All your alerts in one place

We’ll let you know when something goes wrong. If a connector’s performance falls out of its normal range (or fails entirely), Metaplane sends you a Slack alert with context.

Get a failure notification with the context you need to debug the issue in Slack

From this alert, you can click directly into the respective table in your warehouse and specifically debug your connectors from there. Instead of correlating data from different sources, you have everything you need to quickly identify and triage issues, all in one place. 

Get started with Fivetran observability in < 5 min

Be the first to know when something is off with your data. Get started with Metaplane’s Fivetran observability in minutes.

Want to get started with Metaplane for the first time? You can create an account for free or pick a time to learn more about data observability best practices from the team.

Table of contents

    Tags

    We’re hard at work helping you improve trust in your data in less time than ever. We promise to send a maximum of 1 update email per week.

    Your email
    Ensure trust in data

    Start monitoring your data in minutes.

    Connect your warehouse and start generating a baseline in less than 10 minutes. Start for free, no credit-card required.