Suggest features, upvote favorites, and use the user story format: > As a [role], I want to [action], so that [benefit]. Help us build what you need - post your idea now!
What you should know submitting product ideas to our product team
Share your product ideas with the community and our product team
Hi,I noticed that the current setup with the Dockerfile cognite/db-extractor-base runs the extractor as the root user within the container.In our use case, we have to heavily modify the Dockerfile to change the setup so that it runs as a non-root user. It would be highly beneficial if the Docker image either accepted an argument to run as a non-root user or, preferably, ran the script as a non-root user by default. Running containers as the root user is not best practice for containerized development and is often restricted in organizational environments.I'm not sure if there is an intentional reason for running as root, or if this aspect hasn't been considered yet at Cognite.If you are open to changing this, I can assist and provide our current solution. I believe this adjustment would improve security and compatibility for multiple users.Best regards,Matias Ramsland,matias.ramsland@akerbp.com
It is not possible to aggregate edges, making it impossible to create queries such as: How many reporting units are at the Reporting Site CLK? The aggregation API of Cognite has several limitations; we cannot group by date. More complex filters do not work either. Aggregations are limited to primitive fields in the GraphQL API. Using the GraphQL API, we cannot filter an object type based on its edge. For example, querying the reporting sites associated with a specific reporting unit is not possible. Pagination parameters are unstable. For instance, the "has previous page" parameter does not work. The limit of 10,000 items for subqueries in the SDK Query method makes pagination extremely costly. We believe this limit should only apply to the select output. It should be possible to filter and sort by the createdTime and lastUpdatedTime columns in FDM. There is a lack of search capabilities using wildcards or case-insensitive searches with multiple parameters. The Cognite API lacks transaction capabilities. FDM documentation should have more examples.
The Cognite API lacks transaction capabilities.
There is a lack of search capabilities using wildcards or case-insensitive searches with multiple parameters.
It should be possible to filter and sort by the createdTime and lastUpdatedTime columns in FDM.
The limit of 10,000 items for subqueries in the SDK Query method makes pagination extremely costly. We believe this limit should only apply to the select output.
Pagination parameters are unstable. For instance, the "has previous page" parameter does not work.
The aggregation API of Cognite has several limitations; we cannot group by date. More complex filters do not work either. Aggregations are limited to primitive fields in the GraphQL API.
It is not possible to aggregate edges, making it impossible to create queries such as: How many reporting units are at the Reporting Site CLK?
When creating interactive engineering diagrams on the Cognite web UI, we have the option to select between standard and advanced model.It would be beneficial to have the possibility to combine this with customized entity matching and be able to choose from available feature types (such as "simple", "bigram" etc.).This option would be just as, if not more, useful as the advanced detection model.
We use CDF to store model result that in essence is a dataframe with datetime index and multiple columns for each scenario/attribute/timeseries. This could be a weather forecast model or a hydropower optimization model etc. We wish to store the model results as a sequence as the values are related to the same model run and would require a significant amount of timeseries (given that the models are run several times a day and produce thousands of timeseries for each run). We would therefore appriciate if sequences would support datetime index, and not just int. This would reduce the code we need to wrap around the cdf client in order to store our dataframes.
I have quite a few engineering diagrams that have been annotated in CDF and now we need to convert them to SVGs in order for some third party application to read them. The API supports this, but the Python SDK does not, or at least not directly. It is possible to force the behavior, but it requires a cumbersome workaround to “trick” the SDK.The SDK seems to expect that the convert job is the next after detect, in theory this makes some sense, however in reality this is not how it will be done. The process will be to detect annotations, then get them approved, then generate the SVG file. The middle step is a manual and the convert job will be run as a separate pipeline.As shown below, the API supports this by having the feature that we can send in the file and the annotations, the input for the SDK is the output of detect. It is possible to replicate the required input, but it is cumbersome. Is there a way to more simply use the files and the annotations through the SDK to convert the files after the fact?Ideally I would want to do something like this:files = client.files.list(data_set_external_ids=docDataSetExtId)ext_ids = [f.external_id for f in files]flt = AnnotationFilter(annotated_resource_type="file", annotated_resource_ids=[{"externalId": ext_id} for ext_id in ext_ids])annotations = client.annotations.list(flt, limit=-1)# Thisclient.diagrams.convert(files, annotations)# or like thisfor file in files: flt = AnnotationFilter(annotated_resource_type="file", annotated_resource_ids=[{"externalId": file.external_id}]) annotations = client.annotations.list(flt, limit=-1) client.diagrams.convert(file, annotations)# Or even just having the SDK handle all of it in the background (best option for me)# And then the SDK or CDF itself just retrieves all annotations linked to the fileclient.diagrams.convert(external_id=file.external_id) https://cognite-sdk-python.readthedocs-hosted.com/en/latest/contextualization.html#convert-to-an-interactive-svg-where-the-provided-annotations-are-highlightedhttps://api-docs.cognite.com/20230101/tag/Engineering-diagrams/operation/diagramConvert
Currently, the data explorer functionality does not allow filtering of 3D images based on the dataset they belong to. Since those 3D images are scoped or associated with specific datasets, the data explorer should provide the ability to filter the 3D images by the dataset they are part of."
Oil and gas Industry handle different kind of curves, one of them IPR that curve correspond in CDF to sequence. we must load 500 IPR curves one by every well, but I have found a stopper, when we use ODBC extractor in the sequence destination, must put in external_Id directly in the yaml configuration file (image belove) , every time that we load an IPR curve. It will be possible that external_id works like time series, taking data from column? And loading all the sequences with the same file or query, happen the same for oracle queries from database and excel files.@Sebastian Wolter @Aditya Kotiyal
Hi, sure this has been raised before, but would it be too much to ask to enable standard logging calls in Python when using Cognite Functions. While I am fully aware that it works to use print statements instead, it is very contrary to expectations for most developers that logging would not work, also for your own consultants (various Cognite consultants on our projects have themselves converted print statements to logger.info calls in the name of “best practice”, only to be surprised that nothing gets printed out). Moreover it gives the impression that the product is not quite “working” or that there is “something weird going on”. I would consider it similar to a cosmetic UX defect which is easy to work around: sometimes hard to prioritise, but affects the overall impression of the product when things do not work as expected. Maybe it is time to give it some TLC.
Oxy is requesting for the ability to link Charts to a Infield in a way that based on the historical data available in a time series in charts, the product is capable of making the threshold recommendation for a measurement in Infield. E.g., based on the engine’s measured temperatures over the last year in Charts, the normalized expected temperature is between 90 and 110 °C. So 90 will automatically populate as the lower limit in Infield and 110 as the maximum limit for this motor.
When selecting information in Canvas you must move the Canvas to allow visibility of the additional information. It appears the information always appears to the right of the object selected. The user has to move the Canvas to enable viewing information. Would it be possible to display information with respect to the visible window?
We kindly request your support in enhancing the SAP extractor to include support for OData V4.0 endpoints.By extending the compatibility of the extractor to encompass OData V4.0, we can seamlessly extract the required data from SAP, enabling us to optimize our integration processes and derive valuable insights from our SAP data.The addition of support for OData V4.0 endpoints would significantly enhance the functionality and utility of the SAP extractor. OData V4.0 is the latest version of the OData protocol, offering improvements in areas such as performance, scalability, and flexibility compared to previous versions. By enabling the SAP extractor to communicate with OData V4.0 endpoints, users would benefit from enhanced performance and compatibility, ensuring a smoother and more efficient data extraction process.A lot of SAP API’s are on OData V4.0 and having the support will enable us to progress on ingestion of these API’s
Current customer’s workflow, involves heavy manual interaction with their internal Sharepoint to update the status on RCFA and its related action items. If Canvas could read and write back the summary of the investigation and action items, it will save the customer a considerable amount of time and will automate this process.
Steps to Reproduce Click on Data Explorer tab Click on the Assets tab at the top to select the assets resource type. in the assets tab, search for the asset (By sort field or by SAP equipment number). Switch to list view on the asset search results. on the search results, click on "Select column" button at the top right hand side of the search results panel. Add 3D Availability column to the view of assets. The asset searched for should be the first one on the search results and should show label "Exact Match". Click on the link for that asset under 3D Availability. Verify the asset in 3D view for point cloud and 360 images. users wants to annotate something to inform a colleague Observed Results: Not possible to create an annotation by an end user. Expected Results: User desires to make annotations on 2D or 3d to inform. Not possible to find tasks associated to assets in InField in the main CDF solution.
Search functionality while exploring 3D Models not working as expected.Steps to Reproduce the issue.1. Navigate to data explorer.2. Click on 3D Tab.3. Select B60 (P-12) (32A-37-38A-38B) model.4. On the search box on the left select 07-C-0701A asset5. While the asset is selected on the right-hand side user will view all the assets, time series, file and events data.6. Click on assets tab. User will be able to view all the linked asset to the compressor 07-C-0701A as shown below7. Now on the left-hand side change the asset name from 07-C-0701A to 07-C-0701B as shown in image belowExpected Results As the user change the asset to 07-C-0701B on the left-hand side search window and click on the asset it directs the user to the correct object in 3D model and the list of assets on the right hand should also change. However, the list does not change as shown in the image above. As soon as the asset is changed on the search option on the left the direct linked asset shall also change.Observed Results Even though the asset on left hand side is changed the asset list on right hand side does not change automatically and use must close the asset window in right so that the linked asset related to 07-C-0701B are updated.
In behalf of Celanese Bishop users:The email we receive with an alarm has little information about it. It only has the name of the monitoring job, the time of the alarm, the timeseries and the threshold. In some cases, it is important to send also some details or instructions to the person who is getting the alarm. Let’s say, for instance, an operator is receiving this alarm if a pressure is too high. The email could have some instructions on how to fix the problem, a link to a document with the instructions or some other details that are required to tackle the issue. We suggest, therefore, that the user that is creating the alarm has the option to input a text that will be sent on the e-mails.
BackgroundIt appears that currently we don’t have a way to fully automate the migration of CDF Charts created in CDF dev to CDF prod. This would mean that it will be necessary to re-create all the Charts in prod CDF project by hand importing the exported calculations from dev. Proposal If there is API support for retrieving a representation of a Charts, it will be possible to easily migrate that to a different CDF project.Represent CDF Charts in data-sets. Add SDK capability to retrieve the object representation of the Charts. This should allow migration of Charts in-between different CDF projects.
When I crate a calculated time series using Charts “save and schedule”, these timeseries do not have a linked asset. I suggest having the possibility to select the asset in the save and schedule UI.Here is a post that I did about this.
I have several files I routinely access in Cognite Data Fusion. I can add bookmarks in my browser and edit the favorite title to make it descriptive but it would be ideal to be able to add a favorite in CDF which would include the item’s name.
Check the
documentation
Ask the
Community
Take a look
at
Academy
Cognite
Status
Page
Contact
Cognite Support
