Operations asks the civic Firepower FDM helper team for an effective application logging strategy. Which emission pattern should the app adopt?
Select an answer to reveal the explanation.
Short Explanation
Structured logs are labeled bins on a conveyor—time, level, event, request id—so operators can sort them. Random print("oops") is loose change on the floor, not a strategy.
Full Explanation
An effective logging strategy emits structured events (timestamp, severity, event name, correlation fields) to stdout/stderr for collection. Ad-hoc prints without levels or keys hinder search and alerting. This is about how the app emits logs, not about interpreting a stack trace from an existing incident log.