[Operational Awareness] review usage of logger in KIM to ensure well formatted and expressive log-messages and appropriate log-levels

[tobiscr]

Description

For efficient analysis and debugging during runtime, we have to provide expressive error-messages in KIM. Also the used log-level has to be reviewed to highlight relevant information in the logs.

Guidelines for Loglevel usage:

• DEBUG / VERBOSE (only for tracing purposes)
• INFO (business/operational relevant but not critical)
• WARN (critical but recoverable)
• ERROR (critical and non-recoverable)

AC:

• Ensure each log message related to the reconciliation of a RuntimeCR has to include the runtime-ID and shoot-ID
• Review the logic in KIM and ensure business / technical relevant events and also all technical edge / error cases are logge
• Review used log messages to ensure they include all information to enable an on-call engineer to understand the problem (expressive message, provide all data required for next analysis step, indicate if the issue could be related by 3rd party system etc.)
• Ensure for each log message is an appropriate log-level used
• Use JSON as standard log format (Configure logging to be in a json format #50)
• Use proper timestamp format (Adjust log format of KIM to RFC3339 #219)

Reasons

Improve operational quality of KIM by using expressive log-messages.

Attachments