version, which holds the version of the configuration schema. This article describes version 1.
Using values from environment variables
The configuration file allows substitutions with environment variables. For example:COGNITE_CLIENT_SECRET environment variable into the cognite/secret parameter. You can also do string interpolation with environment variables, for example:
Implicit substitutions only work for unquoted value strings. For quoted strings, use the
!env tag to activate environment substitution:Using values from Azure Key Vault
The DB extractor also supports loading values from Azure Key Vault. To load a configuration value from Azure Key Vault, use the!keyvault tag followed by the name of the secret you want to load. For example, to load the value of the my-secret-name secret in Key Vault into a password parameter, configure your extractor like this:
azure-keyvault section in your configuration, with the following parameters:
Example:
cognite
Global parameter.
The cognite section describes which CDF project the extractor will load data into and how to connect to the project.
idp-authentication
Part of cognite configuration.
The idp-authentication section enables the extractor to authenticate to CDF using an external identity provider (IdP), such as Microsoft Entra ID (formerly Azure Active Directory).
scopes
Part of idp-authentication configuration.
Enter a list of scopes requested for the token
Each element of this list should be a string.
certificate
Part of idp-authentication configuration.
Authenticate with a client certificate
data-set
Part of cognite configuration.
Enter a data set the extractor should write data into
extraction-pipeline
Part of cognite configuration.
Enter the extraction pipeline used for remote config and reporting statuses
connection
Part of cognite configuration.
Configure network connection details
proxies
Part of connection configuration.
Dictionary mapping from protocol to url.
logger
Global parameter.
The optional logger section sets up logging to a console and files.
console
Part of logger configuration.
Include the console section to enable logging to a standard output, such as a terminal window.
file
Part of logger configuration.
Include the file section to enable logging to a file. The files are rotated daily.
metrics
Global parameter.
The metrics section describes where to send metrics on extractor performance for remote monitoring of the extractor. We recommend sending metrics to a Prometheus pushgateway, but you can also send metrics as time series in the CDF project.
push-gateways
Part of metrics configuration.
List of prometheus pushgateway configurations
Each element of this list should be a the push-gateways sections contain a list of metric destinations.
cognite
Part of metrics configuration.
Push metrics to CDF timeseries. Requires CDF credentials to be configured
data-set
Part of cognite configuration.
Data set the metrics will be created under
server
Part of metrics configuration.
The extractor can also be configured to expose a HTTP server with prometheus metrics for scraping
sap
Global parameter.
List of SAP instances to connect to
Each element of this list should be a configuration of an SAP source
Either one of the following options:
sap_netweaver_gateway
Part of sap configuration.
The SAP NetWeaver Gateway lets clients connect using the Open Data Protocol (OData).
Examples:
certificates
Part of sap_netweaver_gateway configuration.
Certificates needed for authentication towards SAP instance.
There are three certificates needed to perform the authentication: certificate authority (ca-cert), public key (public-key), and private key (private-key).
proxy
Part of sap_netweaver_gateway configuration.
HTTP and/or HTTPS proxies to be used when connecting to the SAP source system.
sap_soap_source
Part of sap configuration.
The SAP extractor can connect to SAP instances using SOAP, such as for SAP ERP SOAMANAGER
Example:
certificates
Part of sap_soap_source configuration.
Certificates needed for authentication towards SAP instance.
There are three certificates needed to perform the authentication: certificate authority (ca-cert), public key (public-key), and private key (private-key).
endpoints
Global parameter.
List of endpoints to query
Each element of this list should be a description of an endpoint to extract data from on one of the configured SAP sources.
Requests
Therequest parameter is part of the endpoints configuration, and is required soap endpoints.
SOAP requests
SAP ABAP Webservices are SOAP/based, meaning the requests to the SAP server must be in a valid XML format. The SAP extractor expects this XML to be added as a string in therequest parameter. This is an example of a valid XML request to a SAP ABAP Webservice generated from a SAP Function Module:
destination
Part of endpoints configuration.
The destination of the data in CDF.
Either one of the following options:
raw
Part of destination configuration.
The raw destination writes data to the CDF staging area (RAW). The raw destination requires the sap-key parameter in the endpoint configuration.
events
Part of destination configuration.
The events destination inserts the resulting data as CDF events.
field-mapping
Part of events configuration.
Enter the fields of the SAP entity that corresponds to fields of an Event
assets
Part of destination configuration.
The assets destination inserts the resulting data as CDF assets.
field-mapping
Part of assets configuration.
Enter the fields of the SAP entity that corresponds to fields of an Asset
time_series
Part of destination configuration.
The time_series destination inserts the resulting data as CDF assets.
field-mapping
Part of time_series configuration.
Enter the fields of the SAP entity that corresponds to fields of a time series data point
files
Part of destination configuration.
The files destination writes data to the CDF staging area (Files)
sap-key
Part of endpoints configuration.
Enter a list of fields related to the SAP entity to be used as keys while ingesting data to CDF staging. This is a required parameter when using raw as the CDF destination.
Each element of this list should be a string.
select
Part of endpoints configuration.
Enter a list of fields to be selected from the SAP entity, using OData $select operation. This parameter is available only for SAP OData endpoints.
Each element of this list should be a string.
related-entities
Part of endpoints configuration.
Sub entities to be fetched from the main sap-entity. Feature is available for SOAP and OData sources.
destination
Part of related-entities configuration.
The destination of the data in CDF.
Either one of the following options:
raw
Part of destination configuration.
The raw destination writes data to the CDF staging area (RAW). The raw destination requires the sap-key parameter in the endpoint configuration.
events
Part of destination configuration.
The events destination inserts the resulting data as CDF events.
field-mapping
Part of events configuration.
Enter the fields of the SAP entity that corresponds to fields of an Event
assets
Part of destination configuration.
The assets destination inserts the resulting data as CDF assets.
field-mapping
Part of assets configuration.
Enter the fields of the SAP entity that corresponds to fields of an Asset
time_series
Part of destination configuration.
The time_series destination inserts the resulting data as CDF assets.
field-mapping
Part of time_series configuration.
Enter the fields of the SAP entity that corresponds to fields of a time series data point
files
Part of destination configuration.
The files destination writes data to the CDF staging area (Files)
sap-key
Part of related-entities configuration.
Enter a list of fields related to the SAP entity to be used as keys while ingesting data to CDF staging. This is a required parameter when using raw as the CDF destination.
Each element of this list should be a string.
attachments
Part of endpoints configuration.
Extraction of SAP attachments to CDF files. Feature is available only for OData endpoints (restricted to S/4HANA installations)
destination
Part of attachments configuration.
The destination of the data in CDF.
Either one of the following options:
raw
Part of destination configuration.
The raw destination writes data to the CDF staging area (RAW). The raw destination requires the sap-key parameter in the endpoint configuration.
events
Part of destination configuration.
The events destination inserts the resulting data as CDF events.
field-mapping
Part of events configuration.
Enter the fields of the SAP entity that corresponds to fields of an Event
assets
Part of destination configuration.
The assets destination inserts the resulting data as CDF assets.
field-mapping
Part of assets configuration.
Enter the fields of the SAP entity that corresponds to fields of an Asset
time_series
Part of destination configuration.
The time_series destination inserts the resulting data as CDF assets.
field-mapping
Part of time_series configuration.
Enter the fields of the SAP entity that corresponds to fields of a time series data point
files
Part of destination configuration.
The files destination writes data to the CDF staging area (Files)
schedule
Part of endpoints configuration.
Enter the schedule for when this query should run. Make sure not to schedule runs too often, but leave some room for the previous execution to be done. Required when running in continuous mode, ignored otherwise.
Either one of the following options:
Examples:
fixed_interval
Part of schedule configuration.
cron_expression
Part of schedule configuration.
extract-schema
Part of endpoints configuration.
If included, the extractor will extract the SAP entity schema to CDF RAW
extractor
Global parameter.
General extractor configuration
state-store
Part of extractor configuration.
Include the state store section to save extraction states between runs. Use this if data is loaded incrementally. We support multiple state stores, but you can only configure one at a time.
raw
Part of state-store configuration.
A RAW state store stores the extraction state in a table in CDF RAW.
local
Part of state-store configuration.
A local state store stores the extraction state in a JSON file on the local machine.