Check the
documentation
Ask the
Community
Take a look
at
Academy
Cognite
Status
Page
Contact
Cognite Support
Our extractors doesn't support routing data from running instance to different spaces/datasets. This approach will become a major issue when we scale to many sites for one customer. Could we make it possible to assign space/dataset dynamically based on some information in the payload. This is based on experience from our SAs, potentially from several of our customers.
Parked
Extractors - routing data
+1
Hi Anita,
The hosted extractors mapping functionality should be usable for this purpose, but for on-premises extractors, the implementation for the idea will be very dependent on the extractor (and protocol used by the source system).
It’s most likely going to be near impossible to reliably build mapping based on actual source data (I suspect) in the on-premises case, but may be possible from given identifier patterns in the protocol metadata (similar to what the hosted extractors would be doing).
From a capacity perspective, this is not something I would expect the teams to be able to deliver until 2H, 2026 at the earliest.
Enter your E-mail address. We'll send you an e-mail with instructions to reset your password.