Skip to main content

Time Series and OT Product Development User Group [Early Adopter]

  • 15 Topics
  • 37 Replies

Welcome to the Time Series and OT Early Adopter Group

This group is an early adopter group for users of the Time Series and Events APIs with a focus on OT data. In this group we will post topics to solicit feedback on future roadmap plans, provide insights into upcoming feature releases and to answer your questions about features. We created this group to be able to maintain ongoing discussions on feature topics, rather than create a new group every time we release a new feature. We hope you enjoy this format and look forward to your participation. For more general 'how to' type questions, please continue to use the Question and Answers section of the Hub, and for Product Idea please continue to submit those via the 'Have a Product Idea' button.

J
Seasoned
Jesse JenkenSeasoned
Hosted Event Hub Extractor Needs Multiplexing / Ability to Send to Multiple Datasets

Within our implementation we have an existing Hosted Extractor reading data from an IoT Hub that contains multiple sites worth of data. Our Hosted Extractor Mapping Template filters for events that have a particular deviceId on it, representative of the location these events are coming from. In effort of ingesting another site-location datafeed, I wanted to extend the template with an ELSE IF condition that has the mapping rules for the other location, which are almost identical to the first except for the target datasets, which I’ve come to realize is set in the Sink section of the Extractor Configuration. The net result here is needing to create redundant Hosted Extractor configurations that change only a filter, rather than having a cascading ELSE IF ruleset that applies to the full stream. For example, this pseudo-template for our existing hosted extractor configuration for one site: if (context.messageAnnotations.`iothub-connection-device-id` == "SITE_A") { input.map(record_unpack

242
J
Seasoned
Johan Herman Storm
Committed
Johan Herman StormCommitted
Interpolation rules in CDF

How do you set and see the interpolation rules for your dataset in CDF?

452
Johan Herman Storm
Committed
Glen Sykes
Seasoned Practitioner
Glen SykesSeasoned Practitioner
Getting started with Records and Streams

Hello Community, The Records and Streams APIs are now available for early adoption, with an expected announcement of Beta software maturity level in January 2025. Intended use cases for Records are the storage of high volumes of structured data such as Logs (i.e. Alarms and Events, Manufacturing Logs and Well Logs), and Historic Data. The API is designed to handle hundreds of billions records per year, from various source systems. Use cases that currently store historic data as Nodes in the industrial knowledge graph are excellent candidates for the use of the new API. Early adoption means Cognite provides you access to pre-production APIs (and later SDKs) in return for engagement and feedback during the product development process. By default, the APIs are not enabled in every customer project. Early adoption intended to provide those customers who are interested in utilising the API functionality in their future plans, the ability to gain an understanding of the product concepts, pro

530
Glen Sykes
Seasoned Practitioner
Glen Sykes
Seasoned Practitioner
Glen SykesSeasoned Practitioner
Problems with Stream IDs in ILA API

@Tanmay Deshpande and @Tom Jonsthovel , posting your question here to make it easier to engage the developer team for support. We have successfully created the ILA group and can call the API, however we currently get stuck on ingesting logs (400 - bad request). Please see our steps below. It would be great if you could advise on how to properly ingest logs and share a Jupyter notebook with some examples. Also, would be great to understand the link between the ingested log and the container. Eg, do we need to add a 'log' property to the container definition? Created a data model. Ingest a log into the container with externalId "Pump" and link to "Pump" instance with externalId "66470bf0-5c07-4a39-8878-0adf4dc7f448" Get 400 on return.

635
APSHANKAR Sagar
Committed
L
Committed
Lok Mun SohCommitted
OPCUA | Timeseries inaccurate timestamp from different timezone

Ingesting data through OPCUA where the OPCUA Server timezone is set as UTC+8.After ingestion, the timeseries somehow normalize the data to UTC+0.E.g. Ingesting data at 2024-09-11 11:00+08:00But checked the timeseries data as 2024-09-11 11:00+00:00 which mean 2024-09-11 19:00+08:00.How do we ensure that the ingested data uses the correct timezone when storing it?

221
Dilini Fernando
Seasoned Practitioner
R
Seasoned
Rimmi AnandSeasoned
Is there change in Timeseries Subscription Limit

As per documentation, it is mentioned that 10,000 timeseries is the limit in each subscription. I see issue with count while adding timeseries using SDK. I have created timeseries subscription through SDK, it took more than 10000 timeseries. Is there any change in limit under subscription ?

616
Dilini Fernando
Seasoned Practitioner
Olav Alstad
Committed
Olav AlstadCommitted
User defined status code for time series

Datapoints can have three main status codes: Good, Uncertain and Bad. https://developer.cognite.com/dev/concepts/reference/status_codes Is it possible to define a user defined status code? In our case, that would be Replaced. (I’m aware of the the sub category GoodEntryReplaced under Good, but it would be great to have Replaced as a main status code)

815
Glen Sykes
Seasoned Practitioner
N
Committed
Niranjan Madhukar KarvekarCommitted
Data point subscriptions - timeseries limit

Hi, In the documentation it is mentioned that 10,000 timeseries is the limit in each subscription. Is this the hard limit or it can be changed based on use cases? We are using CDF workflow and in that our first function to read data points subscriptions to get the timeseries and datapoints. Based on our use cases, 10,000 number for timeseries in subscription is too small. We are considering 10,000 wellbores and 200 properties. (10,000 * 200 = 2 Million timeseries). Any recommendations?

653
Dilini Fernando
Seasoned Practitioner
N
Committed
Niranjan Madhukar KarvekarCommitted
Graphql query to retrieve data points

Hi, We are using graphql query to get data points in CDF function. As I understand we could retrieve 1,00000 data points at a time if we provide the limit. Here is the sample query: query MyQuery { listProductionData( filter: {externalId: {in: ["wellbore1"]}} ) { items { space data { Oil { 1_day { dataPoints(end: 2240591400000, limit: 100000, start: 1672338600000) { value timestamp } } } } } }} I tried above query and I can get all the daily datapoints present in the range from 2023-01-01 to 2040-12-31. But when I tried below query : query MyQuery { listProductionData( filter: {externalId: {in: ["wellbore1"]}} ) { items { space data { Oil { 1_day { getDataPoints(start: 1672338600000, end: 2240591400000) { items { timestamp value } } } } } } }} we can get only 10 data points at a time. I don’t see any limit option when we use getDataPoints. Can you please help to understand the difference between dataPoints and getDataPoints? Any reason that limit option is not part of getDataPoints. Wh

702
Dilini Fernando
Seasoned Practitioner
Glen Sykes
Seasoned Practitioner
Glen SykesSeasoned Practitioner
Welcome to the Time Series Subscriptions community

Welcome to the Time Series Subscriptions community group for Early Adopters! Time series subscriptions are aimed at data engineers who need to monitor changes to Time Series datapoints / write only the updated datapoints to their application storage etc. This feature negates the need for consumers to download an entire time series again, just to get the changes. The feature is now available in public beta (including Python SDK support), and customers are encouraged to try it out. This group is staffed by the product team and we are available for Q&A, providing support and receiving feedback on the feature. To get started, please take a look at the user guide, the API specification. User guide: https://developer.cognite.com/dev/concepts/data_point_subscriptions/ API documentation: https://developer.cognite.com/api/?version=20230101-beta#tag/Data-point-subscriptions/ Python SDK: https://cognite-sdk-python.readthedocs-hosted.com/en/latest/core_data_model.html#data-point-subscriptions We l

2088
R
Seasoned
Glen Sykes
Seasoned Practitioner
Glen SykesSeasoned Practitioner
Python SDK support for Time Series Data Quality Status Codes

Hello Community Members, I am delighted to announce that from today, the Cognite Python SDK now has support for Time Series Data Quality Status codes. Using the SDK, you may retrieve data points including their status codes, and filter on status codes if desired. You may also insert data points with status codes. For a full description of all the methods and functionality, please refer to the Python SDK Documentation and our Developer Documentation Whilst this functionality remains in Beta maturity, we are targeting the upcoming June release for General Availability. Cognite relies on customer feedback as key part of its product maturation process, and customers are warmly encouraged to begin implementation of support for data quality status codes and to provide the valuable feedback necessary to allow us to make this feature Generally Available. Thank you for your continued support! Glen

430
Glen Sykes
Seasoned Practitioner
Glen Sykes
Seasoned Practitioner
Glen SykesSeasoned Practitioner
Data Point Versioning and Lineage

Hello group members, “If you were to use CDF as an Industrial Historian, what features relating to versioning, tracking of changes and auditing would you need from our Time Series API”. In an upcoming release, we are planning to introduce support for versioning on Time Series, with the intention to enable our Time Series service to be used in the same way as you would a traditional industrial Historian. I am keen to gather information and insights from you to understand the scenarios where such a capability is required, in order that we build the right thing. Please feel free to send me a direct message if this is of interest to you! Kind Regards, Glen

190
Glen Sykes
Seasoned Practitioner
Glen Sykes
Seasoned Practitioner
Glen SykesSeasoned Practitioner
Welcome to the Time Series and OT Early Adopter Group

This group is an early adopter group for users of the Time Series and Events APIs with a focus on OT data. In this group we will post topics to solicit feedback on future roadmap plans, provide insights into upcoming feature releases and to answer your questions about features. We created this group to be able to maintain ongoing discussions on feature topics, rather than create a new group every time we release a new feature. We hope you enjoy this format and look forward to your participation. For more general 'how to' type questions, please continue to use the Question and Answers section of the Hub, and for Product Idea please continue to submit those via the 'Have a Product Idea' button.

180
Glen Sykes
Seasoned Practitioner
Glen Sykes
Seasoned Practitioner
Glen SykesSeasoned Practitioner
Time Series Subscriptions General Availability Release

Hello everyone in the group! I’m delighted to announce that in the upcoming release, the Time Series Subscriptions feature will mature to a Generally Available level of maturity. But…! The feedback does not stop there. Please do continue to use this group to ask questions about the feature, request improvements or provide any other form of feedback. In light of the news, I also feel that this group in its current form has served its purpose. However, we would like the group to continue as we appreciated your engagement on our product developments. Therefore, we would like to repurpose this group to cover more topics and features relating to the Time Series API, and our other OT services too, such as Events. We hope you continue to be members of the group, and look forward to collaborating with you with our future developments, and thank you so much for your contributions in bringing the Subscriptions feature to GA!

170
Glen Sykes
Seasoned Practitioner
Andre Alves
MVP
Andre AlvesMVP
Data point subscription write access

I am trying to create a time series subscription and receiving the error below: "Must have access to WRITE time series subscription. My question is, if the subscription is a listener, why does it need WRITE access?

433
Glen Sykes
Seasoned Practitioner

Hello and welcome!

This group is an early adopter group for users of the Time Series and Events APIs with a focus on OT data.  In this group we will post topics to solicit feedback on future roadmap plans, provide insights into upcoming feature releases and to answer your questions about features. 
For more general 'how to' type questions, please continue to use the Question and Answers section of our community, and for Product Idea please continue to submit those via the 'Product Idea' button.

We look forward to collaborating with you with our future developments!

Anita Hæhre
Seasoned Practitioner
G
MVP
F
Practitioner
Dilini Fernando
Seasoned Practitioner
P
J
Seasoned Practitioner
Mithila Jayalath
Seasoned Practitioner
T
Seasoned Practitioner
Everton Colling
Seasoned Practitioner
Øystein Aspøy
Committed
M
Practitioner
K
MVP
K
Practitioner
Glen Sykes
Seasoned Practitioner
R
Seasoned
Peter Quinn
Committed
S
Committed
T
Seasoned
N
Committed
Sigurd Holsen
Practitioner
Olav Alstad
Committed
S
Seasoned
A
Committed
jtfrandsen
Active
C
Active
D
Hariharan Raveendran
Active
achkautovich
ryanbooker
Practitioner
R
Seasoned
+ 17
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