Impact 2024: The Industrial Data and AI Conference for and by Users | Nominate Speakers Now for a Ch...
Jypyter notebooks in CDF is running inside your browser and is based on pyodide. There is a subset of packages that works with pyodide. psutil seems like something wouldn’t work here.There workaround is to install jupyter / python locally on your computer.CDF functions runs in a normal python environment, so that’s different.
Microsoft is in dialogue with Grafana, but there is nothing to test now. We are following up with Microsoft regularly and the currently we have been told is Q1 2024, but it’s just an estimate and not committed to.
We don’t have any plans to deploy jupyter or streamlit outside pyodide in the Cognite platform. What are you trying to do that does not work in pyodide?
In the attached config file you have commented out the schedule section#schedule: "* * * * *" Without a schedule the extractor will only run once and exit.
The format changed a little bit on v3 of the extactor: # Required when running the extractor on continous mode # There are two schedule types supported: # - `cron`: Regular cron expression. Check [cronguru](https://crontab.guru/) for further info # - `interval`: Interval-based schedule. For example: `1h` will repeate the query hour or `5m` will repeate the query every 5 minutes. # schedule: # type: interval # expression: 5m You could tryschedule: type: cron expression: "0 * * * *"
Hi Chris - we have acknowledged this as a bug and our engineering team is working on a fix. Will keep you posted.
It’s same as with the Cognite relased extractors. You have a local file with type:remote which refers to the extraction pipeline which contains the config. Sample local config:type: remotecognite: # Read these from environment variables host: ${COGNITE_BASE_URL} project: ${COGNITE_PROJECT} idp-authentication: token-url: ${COGNITE_TOKEN_URL} client-id: ${COGNITE_CLIENT_ID} secret: ${COGNITE_CLIENT_SECRET} scopes: - ${COGNITE_BASE_URL}/.default extraction-pipeline: external-id: ${COGNITE_EXTRACTION_PIPELINE}
What are you trying to achieve here? You cannot have local and remote in the same config.If you have a local config with the extractor it will only read the local config file.If you have type:remote with the extractor it should only contain details around connecting to CDF (cognite section). The extractor will then connect to CDF and read all config from the extraction pipeline.
No, that is not a supported use case.If you need different values per extractor-machine locally you could use environment variables in the config stored in the extraction pipeline.
Already have an account? Login
Enter your username or 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.