Goal of this spike is purely to find which 3rd party packages DO NOT log to stdout. Packages in scope for this spike: - Jira - Confluence - Fortify Repos/helm charts are included in https://repo1.dso.mil/platform-one/big-bang/apps/third-party Guide for validating logging: 1. Deploy each Big Bang with Istio and logging stack of choice (EFK or FLG or PLG). 1. Deploy the helm chart for one (or all depending on how you want to approach) of the 3rd party packages. You may need to deploy image pull secrets manually and modify the helm values to deploy the Istio VS. 1. Navigate to the UI and login/setup the application. No need to do anything excessive, goal is just to generate some traffic that should populate in the logs. 1. Check the pod logs (via `kubectl logs` for each pod included in the helm chart). If any pods are missing logs or seem to missing logs showing your activity make a note of this in the issue. If all pods have logs and seem to be properly logging everything make a note that the package seems to be good. 1. Validate that the logs are also being scraped by Fluentbit/Promtail (check in Kibana/Grafana). This step is basically just a good double check that our log collectors are seeing the same thing as `kubectl logs`. Once you have completed these steps for all 3 packages the ticket can be moved into review. For the reviewer(s): Review the findings and make sure all packages were tested. For any packages that are missing logs open an issue for ensuring the package logs to stdout (linked to this epic) with the details from the spike (one issue per package).