Product News

Sync logs: Full record observability in your data warehouse | Census

Katy Yuan
Katy Yuan April 04, 2022

Katy is a Product Marketing Manager at Census who loves diving into startups, SaaS technology, and modern data platforms. When she's not working, you can find her playing pickleball or Ultimate Frisbee.

Here’s a glimpse of the next generation in Operational Analytics observability: We’re excited to announce Sync Logs for all of your Census syncs!

This means Census writes detailed logs of each data point you’ve synced so you can audit, troubleshoot, and create alerts using the most granular information.

No more ⚠ surprise bugs or sleepless nights fixing pipeline issues.

☸️ The data warehouse is your central hub

We store your logs in your warehouse so you can analyze and combine them with all your other data. This ties into our mission to centralize all data and business logic in your warehouse, THE central hub for your data team.

Native integration with your data warehouse means:

  • No wrestling with S3 buckets, external files, or additional tools to get visibility into your data pipelines.
  • Compatibility with anything that speaks SQL, so you can query logs with the tools you already have – including BI tools, SQL clients, and data testing frameworks like Great Expectations or dbt.
  • You can even incorporate sync logs into your Census SQL models!

🔎 Full observability for Operational Analytics

Sync Logs are another part of Census’s commitment to end-to-end observability, so every user can sync with confidence. For real-time visibility into API calls, check out the API Inspector we released in February.

Using Sync Logs, data engineers, analytics engineers, and operations teams can achieve:

  • Full Visibility: Every sync can generate complete and detailed logs so you know exactly what happened with your data. Audit individual records, troubleshoot API rejection reasons, and investigate data discrepancies.
  • Real-Time Monitoring: Stay up-to-date with the status and health of your data pipelines by monitoring successful and rejected records over time to identify spikes and anomalies in your syncs.
  • Granular Alerting: Proactively triage issues and solve problems faster by setting up alerts triggered by specific rejection reasons or when specific errors reach a certain threshold.

Now, you have full records that guarantee visibility into any sync you choose, so you can audit, troubleshoot, and create alerts with the complete picture of every single data point.

👉 Read the product documentation for Sync Logs

ℹ️ Sync Logs are only available on Platform plans

💕 Customer use case

Issuu, a digital content publishing platform, syncs data from their warehouse to destinations like Iterable. Suela Isaj on the data & analytics team uses Sync Logs to troubleshoot and audit their syncs. She’s able to access the detailed description of each failure and the reason for failure in their data warehouse, helping her find root causes and quickly implement huge improvements.

With Sync Logs, any Census user can:

  • Audit when individual records were successfully synced to your SaaS tools and which operation was performed to investigate data discrepancies.
  • Troubleshoot API rejection reasons for all of your records across all syncs.
  • Rollback data to a previous state if there's an urgent issue.
  • Pro mode! Use the Census Slack integration to notify the right teams of data issues.

Stay one step ahead of data problems and anticipate issues before they happen!

🔮 What’s next?

We’re constantly improving our observability features to make them easier to use and more impactful. Coming soon for Sync Logs is the option to "Download all rejection & skip reasons” for every destination through the Census UI, and other enhancements based on your feedback!

Get a demo or try Census for free!

Related articles

Product News
Sync data 100x faster on Snowflake with Census Live Syncs
Sync data 100x faster on Snowflake with Census Live Syncs

For years, working with high-quality data in real time was an elusive goal for data teams. Two hurdles blocked real-time data activation on Snowflake from becoming a reality: Lack of low-latency data flows and transformation pipelines The compute cost of running queries at high frequency in order to provide real-time insights Today, we’re solving both of those challenges by partnering with Snowflake to support our real-time Live Syncs, which can be 100 times faster and 100 times cheaper to operate than traditional Reverse ETL. You can create a Live Sync using any Snowflake table (including Dynamic Tables) as a source, and sync data to over 200 business tools within seconds. We’re proud to offer the fastest Reverse ETL platform on the planet, and the only one capable of real-time activation with Snowflake. 👉 Luke Ambrosetti discusses Live Sync architecture in-depth on Snowflake’s Medium blog here. Real-Time Composable CDP with Snowflake Developed alongside Snowflake’s product team, we’re excited to enable the fastest-ever data activation on Snowflake. Today marks a massive paradigm shift in how quickly companies can leverage their first-party data to stay ahead of their competition. In the past, businesses had to implement their real-time use cases outside their Data Cloud by building a separate fast path, through hosted custom infrastructure and event buses, or piles of if-this-then-that no-code hacks — all with painful limitations such as lack of scalability, data silos, and low adaptability. Census Live Syncs were born to tear down the latency barrier that previously prevented companies from centralizing these integrations with all of their others. Census Live Syncs and Snowflake now combine to offer real-time CDP capabilities without having to abandon the Data Cloud. This Composable CDP approach transforms the Data Cloud infrastructure that companies already have into an engine that drives business growth and revenue, delivering huge cost savings and data-driven decisions without complex engineering. Together we’re enabling marketing and business teams to interact with customers at the moment of intent, deliver the most personalized recommendations, and update AI models with the freshest insights. Doing the Math: 100x Faster and 100x Cheaper There are two primary ways to use Census Live Syncs — through Snowflake Dynamic Tables, or directly through Snowflake Streams. Near real time: Dynamic Tables have a target lag of minimum 1 minute (as of March 2024). Real time: Live Syncs can operate off a Snowflake Stream directly to achieve true real-time activation in single-digit seconds. Using a real-world example, one of our customers was looking for real-time activation to personalize in-app content immediately. They replaced their previous hourly process with Census Live Syncs, achieving an end-to-end latency of <1 minute. They observed that Live Syncs are 144 times cheaper and 150 times faster than their previous Reverse ETL process. It’s rare to offer customers multiple orders of magnitude of improvement as part of a product release, but we did the math. Continuous Syncs (traditional Reverse ETL) Census Live Syncs Improvement Cost 24 hours = 24 Snowflake credits. 24 * $2 * 30 = $1440/month ⅙ of a credit per day. ⅙ * $2 * 30 = $10/month 144x Speed Transformation hourly job + 15 minutes for ETL = 75 minutes on average 30 seconds on average 150x Cost The previous method of lowest latency Reverse ETL, called Continuous Syncs, required a Snowflake compute platform to be live 24/7 in order to continuously detect changes. This was expensive and also wasteful for datasets that don’t change often. Assuming that one Snowflake credit is on average $2, traditional Reverse ETL costs 24 credits * $2 * 30 days = $1440 per month. Using Snowflake’s Streams to detect changes offers a huge saving in credits to detect changes, just 1/6th of a single credit in equivalent cost, lowering the cost to $10 per month. Speed Real-time activation also requires ETL and transformation workflows to be low latency. In this example, our customer needed real-time activation of an event that occurs 10 times per day. First, we reduced their ETL processing time to 1 second with our HTTP Request source. On the activation side, Live Syncs activate data with subsecond latency. 1 second HTTP Live Sync + 1 minute Dynamic Table refresh + 1 second Census Snowflake Live Sync = 1 minute end-to-end latency. This process can be even faster when using Live Syncs with a Snowflake Stream. For this customer, using Census Live Syncs on Snowflake was 144x cheaper and 150x faster than their previous Reverse ETL process How Live Syncs work It’s easy to set up a real-time workflow with Snowflake as a source in three steps:

Best Practices
How Retail Brands Should Implement Real-Time Data Platforms To Drive Revenue
How Retail Brands Should Implement Real-Time Data Platforms To Drive Revenue

Remember when the days of "Dear [First Name]" emails felt like cutting-edge personalization?

Product News
Why Census Embedded?
Why Census Embedded?

Last November, we shipped a new product: Census Embedded. It's a massive expansion of our footprint in the world of data. As I'll lay out here, it's a natural evolution of our platform in service of our mission and it's poised to help a lot of people get access to more great quality data.