RHCLOUD-35286: Ensure log verbosity can be adjusted

[Adam0Brien]

PR Template:

Describe your changes

• Added a filter for inventory podman logs that can be adjusted via inventory-api-compose
• Added an option for disabling livez and readyz logs to reduce noise.

e.g.

log:
  level: "info"
  livez: false
  readyz: false

Steps:

• Set log level to warn via inventory-api-compose.yaml
• make inventory-up
• kill relations-api pod
• curl readyz endpoint (looking for intentional failure to test warn logs)
• check podman logs for errors

Log Level is set to: warn
ERROR ts=2024-09-23T14:31:35Z caller=log/log.go:30 service.name=inventory-api service.version=0.1.0 trace.id= span.id= service.id=738b063b4a09 msg=RELATIONS-API UNHEALTHY
ERROR ts=2024-09-23T14:31:35Z caller=log/log.go:30 service.name=inventory-api service.version=0.1.0 trace.id= span.id= service.id=738b063b4a09 msg=RELATIONS-API UNHEALTHY
ERROR ts=2024-09-23T14:31:35Z caller=log/log.go:30 service.name=inventory-api service.version=0.1.0 trace.id= span.id= service.id=738b063b4a09 msg=RELATIONS-API UNHEALTHY

Steps:

• Set log level to info via inventory-api-compose.yaml
• make inventory-up
• check inventory podman logs

Log Level is set to: info
INFO ts=2024-09-23T14:32:43Z caller=log/helper.go:117 service.name=inventory-api service.version=0.1.0 trace.id= span.id= msg=Using config file: /inventory-api-compose.yaml
INFO ts=2024-09-23T14:32:43Z caller=log/log.go:30 service.name=inventory-api service.version=0.1.0 trace.id= span.id= subsystem=storage msg=Using backing storage: postgres
INFO ts=2024-09-23T14:32:43Z caller=log/log.go:30 service.name=inventory-api service.version=0.1.0 trace.id= span.id= subsystem=authn msg=Will check for client certs
INFO ts=2024-09-23T14:32:43Z caller=log/log.go:30 service.name=inventory-api service.version=0.1.0 trace.id= span.id= subsystem=authn msg=Loading pre-shared-keys from /psks.yaml
INFO ts=2024-09-23T14:32:43Z caller=log/log.go:30 service.name=inventory-api service.version=0.1.0 trace.id= span.id= subsystem=authz msg=Using authorizer: kessel
INFO ts=2024-09-23T14:32:43Z caller=log/log.go:30 service.name=inventory-api service.version=0.1.0 trace.id= span.id= subsystem=eventing msg=Using eventing: stdout
INFO ts=2024-09-23T14:32:43Z caller=log/log.go:30 service.name=inventory-api service.version=0.1.0 trace.id= span.id= service.id=f629c2427bf6 msg=[gRPC] server listening on: [::]:9081
INFO ts=2024-09-23T14:32:43Z caller=log/log.go:30 service.name=inventory-api service.version=0.1.0 trace.id= span.id= service.id=f629c2427bf6 msg=[HTTP] server listening on: [::]:8081

Ticket reference (if applicable)

Fixes #RHCLOUD-35286

Checklist

• Are the agreed upon acceptance criteria fulfilled?

• Was the 4-eye-principle applied? (async PR review, pairing, ensembling)

• Do your changes have passing automated tests and sufficient observability?

• Are the work steps you introduced repeatable by others, either through automation or documentation?

  • If automation is possible but not done due to other constraints, a ticket to the tech debt sprint is added
  • An SOP (Standard Operating Procedure) was created

• The Changes were automatically built, tested, and - if needed, behind a feature flag - deployed to our production environment. (Please check this when the new deployment is done and you could verify it.)

• Are the agreed upon coding/architectural practices applied?

• Are security needs fullfilled? (e.g. no internal URL)

• Is the corresponding Ticket in the right state? (should be on "review" now, put to done when this change made it to production)

• For changes to the public API / code dependencies: Was the whole team (or a sufficient amount of ppl) able to review?

[akoserwal]

Why call initConfig?