The Cognite Pi extractor is case sensitive and it will only pick up tags with the exact name as they are in the OSI Pi server data source.
This is causing major issues for our data ingestion process since the tags shared by the use case proponent are not entirely the same as on the Pi server itself (may have different capitalization of letter through its name).
For example:
- Shared tag name: A01AAB0A.pv
- Tag name in PI server: a01AAB0A.PV
In this situation, the following config would fail to ingest the listed tag:
extractor:
include-tags:
- "A11AAB0A.pv"
It would be great if the PI extractor could have a case-sensitive: true/false flag to allow case-insensitive tags filtering for ingestion.
For example, something like this would allow the listed tag to be ingested:
extractor:
case-sensitive: false
include-tags:
- "A11AAB0A.pv"
We often fail to ingest timeseries with this kind of discrepancy, which causes inconvenience on the user side and consume time from our side as Cognite Pi extractor maintainers.
We believe it would be much easier to read/ingest the pi tags regardless of the capitalization of the letters or if we could add a flexibility parameter or a regex expression that would pick up a greater specific range of a specific tag.
Check the
documentation
Ask the
Community
Take a look
at
Academy
Cognite
Status
Page
Contact
Cognite Support