Impact 2024: The Industrial Data and AI Conference for and by Users | Nominate Speakers Now for a Ch...
Good morningClient is asking to perform a feature request so the extractor configuration files are currently stores as encrypted files on the source systems where the extractor are run (on prem).This is because:Yaml files are stored locally as clear text Even using ENV-VARS to ‘hide’ the actual values in the YAML files, if someone has access to the system, it can take a look at this ENV variables anyway. THe KeyVault functionality has also a failure as the KeyVault config as well shall be exposed, having a vuelnerability anyway to access ALL keyvault stored params.If this is planned to be, client wants to know an estimated date of the release of this new functionality, and if this is not considered to be imlemented, please to provide a justification. Client is Sierracol (Colombia) and project is CDF deployment. Thank you, Sebastian Wolter
Is there any use cases available and/or documentation with examples about configuring the PI extractor?I have found the documentation available in the web lacks information with more robust examples.Also some of the videos i have seen so far are very very basic that seemes a waste of time to watch cause they can be resumed in one phrase cause they briefly tells you what the extractor do but they dont tell how to get it to work which is what we need as engineers, a step by step guide with better examples, using fictionary data and examples could be a good starting point so we can just follow up the guides and set up instead of being crating a lot of tickets which would be reserved for troubleshooting, etc. Thank you,
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.