Managing logs
SDS for Kubernetes KMS Plugin generates logs for every operation, making it possible to trace all operations performed and potential issues. It is a technical activity essential to the security of information systems.
Logging prerequisites
To meet the logging requirements for SDS for Kubernetes KMS Plugin, you must follow the security recommendations for logging systems issued by the ANSSI in their document ANSSI-PA-012 (French only).
Accessing logs
Run the following journalctl command to access SDS for Kubernetes KMS Plugin logs:
journalctl -fu sds-kms-plugin
Setting gRPC dependencies logging verbosity
Some underlying dependencies used for gRPC communication may issue error-level logs. For example, in case of permission issues on the socket directory, you may get messages such as:
> E No address added out of total 1 resolved
To prevent such messages from polluting your log output, the GRPC_VERBOSITY environment variable is automatically set to NONE by default when launching SDS for Kubernetes KMS Plugin.
If you want to keep these logs (e.g., for debugging purposes), set the GRPC_VERBOSITY environment variable to DEBUG in the sds-kms-plugin.service file. For more information, refer to Creating the Stormshield KMaaS service.