Value Statement

As a user of ACM, I want the operator logs to be more readable and informative, that way I can quickly identify issues and troubleshoot problems in our system.

Definition of Done for Engineering Story Owner (Checklist)

• [x] Implemented clear and consistent log message formatting, including the use of severity levels (i.e INFO, WARNING, ERROR)
• [ ] Migrated away from controller-runtime logging methodology for the operator logs.

Development Complete

• The code is complete.
• Functionality is working.
• Any required downstream Docker file changes are made.

Tests Automated

• [x] Unit/function tests have been automated and incorporated into the
  build.
• [x] 100% automated unit/function test coverage for new or changed APIs.

Secure Design

• [ ] Security has been assessed and incorporated into your threat model.

Multidisciplinary Teams Readiness

• [ ] Create an informative documentation issue using the [Customer
  Portal_doc_issue template](
  https://github.com/stolostron/backlog/issues/new?assignees=&labels=squad%3Adoc&template=doc_issue.md&title=),
  and ensure doc acceptance criteria is met. Link the development issue to
  the doc issue.
• [ ] Provide input to the QE team, and ensure QE acceptance criteria
  (established between story owner and QE focal) are met.

Support Readiness

• [ ] The must-gather script has been updated.