We came across a situation where an api request to swatch-contracts in stage was returning a 401 status code. It was unclear if the 401 was coming from an upstream source (turnpike), or the swatch app. Eventually we were able to determine that it was the swatch-contracts app. There was no evidence looking at the pod that swatch-contracts was even getting hit. We had to turn on the access log (and we then reverted the commit) to verify: https://github.com/RedHatInsights/rhsm-subscriptions/commit/19172cc5bd4ebf0ea1523204201012363086fa13

We should think about making the access log more easily accessible for troubleshooting

• expose env var to toggle? No
• do we want to push them to splunk?  Yes
• do we want to limit/filter access log to just errors? https://quarkus.io/guides/http-reference#configuring-http-access-logs No

Done Criteria

• Access logging is turned on for quarkus apps
• Access logs are visible in splunk 
• Source type for the splunk logs is set. Ask in #help-itde-monitoring-logging for what the source type should be set for on an access log
•