Impact 2024: The Industrial Data and AI Conference for and by Users
All you need to know to get started with our community.
Connect with the community to ask and answer questions and learn.
Build better products with the product team.
Have your say on beta products in our Early Adopter Groups.
I understand that updates older than 7 days may be discarded from the endpoint, which is perfectly fine. However, I’m wondering if it’s possible to determine when a cursor is older than the given limit, since updates older than 7 days are discarded. Based on my understanding of your Subscription API, it would simply continue iterating over the oldest available updates on the endpoint, which could result in missing important updates that occurred between the time of my cursor and the current oldest update. For the Subscription API to be fully functional, I believe it's essential to either receive a notification or an exception when using an expired cursor, be able to determine the age of a cursor, or somehow be assured that iterating from a cursor won't lead to lost data. Knowing the age of the cursor would be preferable, as it would allow us to gauge how much margin we have, but it should also be possible to receive a notification if an expired cursor is being used. Is this currently p
Hello, Does CDF provide CDC connectors/extractors for common SQL databases ? Thanks
I have a use case where I need to filter events from CDF based on a “string.contains” pattern. Is this possible with the current API? Consider the following metadata field for an event in CDF. "EventData": "[{"version":"2.0.0"},{"type":"opcae"},{"id":"1d21002a-77a2-4531-a9bf-27f28876f2e1"},{"source":"47-PA-9810B-M01"},{"time":"5/29/2024 8:56:41 AM"},{"eventType":"Simple"},{"eventCategory":3439269159},{"eventCategoryName":"Process Simple Event"},{"severity":404},{"message":"Start"},{"eventCounter":187718259},{"Class":127},{"ObjectDescription":"PH PotWtr Pump B"},{"PriorityLevel":5}]"The value for `EventData` is a JSON string that has not been unpacked as proper metadata fields. Several of these fields are relevant for us to filter events down to the relevant subset.It is unclear from the documentation whether the API supports the “string.contains” pattern. The only class that maybe sounds like it is relevant is the Search class. This is the documentation:SearchThe Search filter perform
Hello everyone!My name is Krishnan Karthik and I work as a Principal Consultant for a Engineering and Consulting Services company. I am excited to start the course on understanding Cognite Data Fusion architecture and implementation fundamentals to educate and guide clients who are using this platform.
When using Entity Match/Quick Match, the user cannot “Select All” matching Events (or Timeseries) when applying an additional filter. The check box is grayed out. Pretty frustrating. Am I missing something?
Hi.We’re administering CDF deployments from Github using github actions and Cognite toolkit.I’m setting up a github action to automatically perform a dry-run for a pull request to main, and post the dry-run output as a comment on the PR to assist the reviewer.I’d preferably like to use a client with read-only access to CDF for this, but it seems cdf-tk requires full write access even for dry runs - is that so? Performing a dry-run locally with read-only credentials results in:ERROR (AuthorizationError): Don't have correct access rights to deploy iam.groups(all_scoped). Missing:GroupsAcl(actions=[<GroupsAcl Action.Create: 'CREATE'>], scope=AllScope()) -GroupsAcl(actions=[<GroupsAcl Action.Delete: 'DELETE'>], scope=AllScope())Please click here to visit the documentation and ensure that you have setup authentication for the CDF toolkit correctly.I would expect to see the same error on my github-action, but it stops without much useful information:Run cdf-tk deploy --env=dev --
Hello, We noticed that we get throttled (429 HTTP responses) on our backend whenever we make more than 10 req/sec. Is this a soft limit? Could we increase it? Thanks
Hello, We have trouble deploying new container via cdc-toolkit after changing an attribute property. We have the following error: cognite.client.exceptions.CogniteAPIError: Cannot change type for property ││ 'PullDate' in container 'space:container'. | code: 400 Notes;This container contains data before this change We incremented the model version to a new major one We have consumers consuming the current versionWhat is the best practice for handling this kind of changes with the least effect on our current consumers ? Thanks,
As we may soon will need to store sensitive data in Cognite to support specific use cases—such as information on payments made to a specific vendor—it would be highly beneficial to implement a feature that allows the creation of row-level security policies. This would allow us to apply targeted exceptions for users in the Fraud Prevention role, ensuring they have appropriate access while maintaining strict control and protection of sensitive data for other users.
Just presente myself to communit. Thanks
The PI AF Extractor is missing link to the documentation, is there someone that could add this in.For the PI extractor the links are there and something similar for the PI AF extractor would make it easy to navigate to the documentation. The PI AF looks like this:The documentation does exist and lies under this area, would be great if we could navigate from CDF directly to the documentation.https://docs.cognite.com/cdf/integration/guides/extraction/pi_af Regards,Markus PettersenAker BP - CDF Data Delivery
Hi all, I am encountering an issue when calling the client.iam.groups.list(all=True) method in my Python 3.12 environment within Azure Batch. The code runs without issues in my local setup (also Python 3.12), but it fails in Azure Batch with the following traceback: Traceback (most recent call last): File "GroupMembersCapabilities.py", line 55, in <module> groups = client.iam.groups.list(all=True) File "D:\Users\...\site-packages\cognite\client\_api\iam.py", line 297, in list return GroupList._load(res.json()["items"], cognite_client=self._cognite_client, allow_unknown=True) File "D:\Users\...\site-packages\cognite\client\data_classes\iam.py", line 224, in _load [cls._RESOURCE._load(res, cognite_client, allow_unknown) for res in resource_list] File "D:\Users\...\site-packages\cognite\client\data_classes\iam.py", line 147, in _load capabilities=[Capability.load(c, allow_unknown) for c in resource.get("capabilities", [])] or None File "D:\Users\...\site-packages\cognite\client\data
Recently came across articles on MAD and several variations of ESD test for detecting local vs. global anomalies (outliers) in time series data. Anyone has any experiences with such algorithms and any words of wisdom on how to utilize such algorithms to detect local anomalies? Thank you very much,Is there any benefit other than MAD being more robust (to outliers) than Standard Deviation? what about ESD?
Hi,I’ve set up notification alerts for the extraction pipeline for two projects (dev and prod). However, the notifications I’m receiving don’t indicate whether they are from the dev or prod environment—they’re quite generic. Could you please advise if there’s a way to enhance the messages to include project-specific details?Thank you!
Get active and reach the top!
The weekly leaderboard is refreshed every Monday. Make an impact in the community and score high!
To receive our newsletter Cognite Hub News, sign up from your profile card.
Read our product documentation.
See the latest status updates on our services.
Cognite Support is available 24/7.
Already have an account? Login
Enter your E-mail address. We'll send you an e-mail with instructions to reset your password.
Sorry, we're still checking this file's contents to make sure it's safe to download. Please try again in a few minutes.
Sorry, our virus scanner detected that this file isn't safe to download.
