Skip to main content
Planned for development

Alerting Mechanisms for Failed Processing & Limits

Related products:Trust and Security
  • February 28, 2025
  • 2 replies
  • 15 views
Anita Hæhre
ane.eide
joar.saether
+13
  • Anita Hæhre
    Anita Hæhre
  • ane.eide
    ane.eide
  • joar.saether
    joar.saether
  • Stig Grafsrønningen
  • Pedersen Jon-Robert
  • ishita1983
    ishita1983
  • alfi
  • Kristian Nymoen
  • Thomas Røkke
  • Patrick Galler
  • Raluca Bala
  • Abram Ziegelaar
    Abram Ziegelaar
  • Lars Lie
  • Ole Thoresen
  • JON L
  • Giovanna Luna Rosseto
  • Andrew Wagner
    Andrew Wagner
  • KHAN MUDASSIR

Workflow Failures Require an Alerting Mechanism

Scenario:

  • Business Users find Incorrect Data
  • Data team rallies to investigate
  • Investigation finds CDF Workflows have been failing subsequently for numerous occurrences, with failing transformations unable to create new assets along with data models being unable to be updated.

 

In order for us to rely on these mechanisms, we must have a mechanism that gives us awareness ahead of the business reporting a data quality problem that is resulting from a processing failure.  Without this, trust degrades with each incident.

 

It was determined that we hit the Instance Limit due to Data Model Spaces in this case.

It’s not unreasonable for these things to occur, but what is unreasonable is for silent failures to continue and data to skew and business to be the alerting mechanism, here.

 

Within an enterprise that staffs a dedicated data team, the most important thing is maintaining trust in the data regardless of the tooling, and we cannot provide that guarantee with Cognite are our platform today without more proactive alerting mechanisms.

2 replies

Elka Sierra
MVP
Forum|alt.badge.img

Hi ​@Jesse Jenken Thank you for your valuable feedback.

We appreciate your insights and understand the importance of your request. This touches several areas of our product, and I want to assure you that we're actively working on improvements in these areas. While I can't provide specific details or timelines right now, please know that your feedback is being taken seriously and is helping to shape our ongoing development efforts.

Thanks and regards

Elka

 


Arun Arunachalam
Seasoned Practitioner

Hei ​@Jesse Jenken we are aiming for a Q2 release on the notifications for the data workflow failures. Please stay tuned for more updated from our end on this !


Reply


Cookie Policy

We use cookies to enhance and personalize your experience. If you accept you agree to our full cookie policy. Learn more about our cookies.

 
Cookie Settings