Activate ownership

Don't let important issues fall between chairs

Align and activate ownership across engineering, analytics engineers, BI analysts and business stakeholders.

Synq

Nightly production refresh failed

🔥 @Tom type column in fct_revenue has errors

Owner

Tom Smith

Owned assets

Dashboard

monthly_revenue

Dashboard

orders

Critical

Model

fct_revenue

Model

orders

Model

dim_markets

Ownership

Engineers, analysts and business users together. Unified by one ownership model.

Define ownership from data sources to dashboards. Use your existing metadata or Synq to map ownership across all your platforms. Ensure the right people know when to act.

Product Analytics

Billing

Analytics Engineering

Revenue Operations

source.usage

source.charges

source.coupons

usage

charges

revenue

support

monthly_revenue

performance

usage

stripe.charges

stripe.coupons

Ownership model that fits your business

Model ownership structure with your metadata, folder structures or any custom logic.

: dbt metadata

Define owners based on metadata from dbt, Looker or other tools. No need to redefine them in Synq.
: Folder structure

When your ownership works around folder structure use Synq browser to align owners and folders.
: Filters in Synq

No folder structures or metadata? No problem. Synq provides unified mechanism to assign cross-tool owners with powerful filters.

Critical data

Highlight what is important

Highlight your most important assets

Accelerate impact assessment and help teams understand if issues impact anything critical.
: Identify important downstream stakeholders

Understand important downstream stakeholders and their data use cases.

Owners alerting

Reduce the burden for on-call engineers. Notify issues to the right owners directly.

Activate ownership definitions by routing relevant alerts to the right people. No need for centralised on-call triage asking on Slack who was the last modifier for each failed model.

: Bring engineers to own data

Route errors back to data producers. We have seen many engineering teams who were glad to know.
: Understand team dependencies

Uncover how data flows through teams and their use cases.
: Notify downstream owners

Identify and notify downstream stakeholders about issues that might impact their data use cases.

Alerts

Triage without leaving Slack

Act with on-point, targeted, and actionable alerts with relevant details helping you understand what exactly happened.

#data_team 1

#data_team

Synq

Nightly production refresh failed

🔥 @Tom type column in fct_charges has errors


                                'type' should be one of the following values: [charge, refund].
Got 427 errors.

Last commit: Refactoring transactions table by Tom Hardy (17h ago)

Critical impact: board_pack, reg_report Lineage

👀

All details directly in Slack

Stop wading through logs in multiple tools just to find the exact error message.

Tag people who should act

Prevent alert overload and tag owners to make them aware of the issue.

Route alerts to the right teams

Set up alerting rules for groups of assets in any of your tools and route alerts to the right team

Empower owners to prioritise well. Help them see the impact.

Understand impact of changes or blast radius of errors as they happen. Assess what is downstream on table, model, column or owner level. Understand the impact