Data Discovery is currently in Private Preview and is not available for General Availability (GA). It should not be used in production environments, as features and functionality may change before the final GA release.
Viewing the Logs
Viewing Logs
The application logs can be viewed using the following commands:
kubectl logs classification-deployment-{version} -n protegrity -f
kubectl logs roberta-provider-deployment-{version} -n protegrity -f
kubectl logs presidio-provider-deployment-{version} -n protegrity -f
Note: The version of the images can be obtained using the following command:
kubectl get pods -n <namespace-name>
Setting the Log Level
The log level can be updated in the value.yaml file.
# Custom logging configuration for the application.
#
# EXAMPLE - default settings
# loggingConfig:
# root:
# level: DEBUG
# loggers:
# tornado.access:
# level: WARNING
#
To set the log level, run the following steps.
Navigate to the
/eks/helm/classification_appdirectory.Edit the
values.yamlfile.Uncomment the required logging configuration. Under
loggingConfig:, set the value ofroot:levelto one fo the following.
- INFO
- DEBUG
- ERROR
- WARNING
For example, to change the the log level to warning, configure the parameter as follows.
loggingConfig:
root:
level: WARNING
loggers:
tornado.access:
level: WARNING
Save the changes.
Navigate to the
eksdirectory and run theaws_undeploy.shfile to undeploy the application.Run the
aws_deploy.shfile to redeploy the application.