SAP Cloud Logging supports the following parameters for create service
and update service
operations.
Configuration parameters may impact pricing. Pricing information is available via Discovery Center and SAP Cloud Logging Capacity Unit Estimator.
Name |
Required |
Type |
Description |
---|---|---|---|
backend |
No |
Configures the OpenSearch backend. |
|
dashboards |
No |
Configures the dashboards UI. |
|
ingest |
No |
Configures the ingest endpoint. |
|
ingest_otlp |
No |
Configures the data ingestion over the ingest-otlp endpoint (OpenTelemetry Protocol). |
|
retention_period |
No |
Integer |
The time in days until data (see Ingest Observability Data) is deleted. The range is between |
saml |
No |
Configures the SAML Integration to authenticate in dashboards. |
|
rotate_root_ca |
No |
Boolean |
Controls the rotation of the ingestion root Certificate Authority (CA) certificate. Defaults to Refer to Rotate the Ingestion Root CA Certificate for more details. |
Name |
Required |
Type |
Description |
---|---|---|---|
max_data_nodes |
No |
Integer |
Indirectly, this parameter sets the maximum disk size for storing observability data as described in Service Plans. This parameter has no effect for the dev plan. Needs to be between |
Name |
Required |
Type |
Description |
---|---|---|---|
custom_label |
No |
String |
Set a custom label to be displayed in OpenSearch Dashboards in the top bar to identify and distinguish multiple service instances. The label is embedded into a fixed sized element due to technical limitations. It gets cut off if the content is too long. 12 characters is ideal, and the maximum length is 20. Supported characters are |
Name |
Required |
Type |
Description |
---|---|---|---|
max_instances |
No |
Integer |
Specifies the maximum number of provisionable ingest instances, which are scaled automatically based on their overall CPU utilization. Must be between |
Name |
Required |
Type |
Description |
---|---|---|---|
enabled |
No |
Boolean |
Enables ingestion over the OpenTelemetry Protocol. Defaults to |
Ensure that you consider the SAP BTP Security Recommendation BTP-CLS-0001.
Configuration to integrate the service with a SAML Idenditiy Provider (IdP), like SAP Cloud Identity Services - Identity Authentication (Identity Authentication). See Prerequisites on how to integrate SAP Cloud Logging with Identity Authentication. This configuration exposes a subset of the SAML parameters of OpenSearch. Learn more about configuration parameters from OpenSearch
Name |
Required |
Type |
Description |
---|---|---|---|
enabled |
Yes |
Boolean |
Enables SAML authentication. We strongly recommend SAML authentication for production use cases, because of improved security and login flow. Basic authentication is configured if this parameter is set to |
admin_group |
Conditionally |
String |
The SAML group to grant administrative access and permissions to modify the security module. Required if |
initiated |
Conditionally |
Boolean |
Enables IdP-initiated SSO. Required if enabled is set to |
roles_key |
Conditionally |
String |
The list of backend_roles will be read from this attribute during user login. This field must be set to the corresponding attribute for IdP groups,usually |
idp.metadata_url |
Conditionally |
URL |
The URL to get the SAML IdP metadata from. Required if enabled is set to |
idp.entity_id |
Conditionally |
String |
The Entity ID of the SAML IdP. Open the metadata URL in your browser and copy the full value of the |
sp.entity_id |
Conditionally |
String |
The Entity ID of the service provider. Generally, this parameter is set to the name of your application configured in your IdP. Required if enabled is set to |
sp.signature_private_key |
No |
String |
The private key is used to sign the requests. This parameter must be valid base64 encoded and PKCS8 format. |
sp.signature_private_key_password |
No |
String |
The private key used to sign the requests. Valid base64 encoded and PKCS8 format of private key. |
exchange_key |
No |
String |
Key to sign tokens. Provide a random key with an even number (min. length: 32) of alphanumeric characters (A-Z, a-z, 0-9). A random key is generated if the key isn't provided. |