Configuring Data Discovery
This section provides guidance on configuring Data Discovery logging and service providers.
Configurations can be set during deployment by overwriting the configurations defined in the Data Discovery Helm values.yaml.
Overriding Configurations
Create a
values-override.yamlfile with the custom configuration mentioned in the Logging Configuration.Save the changes.
If the application is already deployed, uninstall it using the following command.
helm uninstall data-discovery -n data-discoveryRun the installation command mentioned in the Installing Data Discovery.
Apply the custom configuration using the following command.
-f values-override.yaml
Logging Configuration
To configure the settings during deployment, add the following entries to the values-override.yaml file:
Setting the Log level
Update the log level in the values-override.yaml file.
- Classification Service:
# Custom logging configuration for classificationService
classificationService:
loggingConfig: |
{}
- Providers:
# Custom logging configuration for Providers
providers:
Pattern:
loggingConfig: |
{}
Context:
loggingConfig: |
{}
The empty braces can be populated using the standard Python logging configuration JSON format. For more information, refer the official documentation.
To set the log level, perform the following steps:
- Edit the
values-override.yamlfile. - Under
loggingConfig:, set the value ofroot:levelto one of the following:
- DEBUG
- INFO
- WARNING
- ERROR
- CRITICAL
For example, to change the the log level to WARNING, configure any of the loggingConfig parameters as follows:
- Classification Service:
classificationService:
loggingConfig: |
{
"root": {
"level": "WARNING"
}
}
- Providers:
providers:
Pattern:
loggingConfig: |
{
"root": {
"level": "WARNING"
}
}
Context:
loggingConfig: |
{
"root": {
"level": "WARNING"
}
}
- Save the changes.
Configuring Input Validation Parameters
The Classification service in Data Discovery offers an input validation security feature that rejects invalid input data. For more information about Input Validation, refer to the Input Validation section.
Configure this feature during deployment by adding parameters to the values-override.yaml file. The below configuration uses the same override mechanism described in the Overriding Configuration section.
Following example shows how to Enable/Disable Input Validation Security Controls:
classificationAppConfig:
securitySettings:
# Can be set as True or False
ENABLE_ALL_SECURITY_CONTROLS: true
Feedback
Was this page helpful?