Skip to main content
Gathering Interest

Persistent Identification for Synthetic Time Series in Cognite

Related products:Data Workflows
O
Committed

Problem Statement:

Synthetic Time Series in CDF are dynamically calculated based on expressions, but lack persistent identifiers. This limits usability when users need:

  • Persistent IDs for discovery and access.
  • Simplified queries via API, SDK.
  • Centralized definition of expressions as part of the data model, avoiding the need for each backend to redefine them.

Suggested Approach:

Introduce a Synthetic Time Series Definition object that:

  1. Allows defining synthetic series with a persistent external_id.
  2. Stores metadata like expressions, descriptions, and units.
  3. Enables dynamic evaluation without requiring data storage.
  4. Supports defining expressions as part of a model, enabling reuse across different systems without requiring redundant definitions in backends.

Benefits:

  • Usability: Persistent identifiers for easier access and queries.
  • Consistency: Eliminates repetitive expression definitions.
  • Scalability: Centralized expression definitions simplify updates and maintenance.

T
Seasoned Practitioner
Forum|alt.badge.img

Hi ​@Oussama ALLALI, and thanks for this product idea. 

I think there are a few different product ideas here(?), i.e:

  • Synthetic Time Series (STS) supports the CDF Unit catalog
  • STS expression is persisted and can be recalled/re-executed using a standard identifier (specified by the user)
  • STS supported as a type in Data Modeling

Am a little uncertain as to what you’re alluding to when you mention “different systems” in this context. Would you mind giving me a couple of examples to help me understand?

O
1 person likes this
  • O
    Oussama ALLALI
O
Committed

Hi ​@Thomas Sjølshagen 

When mentioning different systems, I was referring to the multiple ways users interact with time series data in CDF, including:

  • Dashboards (e.g., Grafana): Users may want to reference a synthetic series directly without needing to know its underlying expression.
  • API/SDK Access: Developers querying STS through code may want to simply reference a persistent external_id.
T
Seasoned Practitioner
Forum|alt.badge.img

Thank you for the clarification ​@Oussama ALLALI! 

 

O
1 person likes this
  • O
    Oussama ALLALI


Terms & ConditionsCookie Settings

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