[P1BIGROCKS-1674](https://jira.il2.dso.mil/browse/P1BIGROCKS-1674) The log aggregation of BigBang components does not provide a consistent view of container logs because the format of each applications logs is not accounted for. This epic captures all the work that's required to standardize **all** logs that come into the logging stack: ## Global: * Each log should contain information about the BigBang deployment: * BigBang Version * Component * Component Version ## Host Logs: * The host logs as defined by @iahmad need to be picked up as part of the vSOC effort # Container Runtime Logs: * Flexibility for docker/containerd/crio log formats and the ability to specify that option as a top level BigBang ``` logs: cri: docker ``` ## Kubernetes Logs: All Kubernetes logs should be formatted correctly. Document how to enable Audit logs for different distros (or point to their docs) and ensure that Audit logs are also being captured correctly. * Audit logs ## Application Logs: Each application needs to * Identify the format of the logs being created. * Identify if there exists a parse already for the log format * Configure the application to notify fluentbit of the log format type via pod annotations ## Documentation * Create documentation for new package owners (and update the checklist) to enable third party and new packages to log correctly * How do third party packages log with a parse that's not part of the base BB deployment?