Tech Debt: Forward Postgres logs to Elastic

### Description of the Tech Debt

Forward logs to our Elastic/Kibana instance. Postgres logs are currently kept with default retention only. We need to match this to dev/test 3 months and 2 years prod.

### Tech Debt Triage

The purpose of our technical debt triage process is to analyze technical debt to determine risk level of the technical debt and the value in tackling that technical debt.

Risk Value Scoring:

| Level | Value |
| ------ | ----- |
| High | 3 |
| Medium | 2 |
| Low | 1 |

| Technical Debt - Risk Types | Level | Value |
| ----------------------------------------------------------------------------------------------------------------------------- | ----- | ----- |
| Business Area Risk - Risk of business area visibility / damage to user experience | | 1 |
| Developer Fault Risk - How likely will this tech debt cause a future error related to coding on top of it | | 1 |
| System Fault Risk - Risk of system errors or application downtime | | 3 |
| Time Scale Risk - Compound risk effect if left alone. How much more difficult to fix or dangerous will this become over time? | | 1 |
| Time Sink Risk - How much will this tech debt slow the development process down | | 1 |
| TOTAL SCORE: | | 7 |

### Reference

https://www.crunchydata.com/blog/log-export-examples-using-crunchy-postgres-for-kubernetes

Start by inspecting the repository's Postgres and Kubernetes deployment manifests, then compare them with the linked CrunchyData log-export examples. Done means Postgres logs reach Elastic/Kibana with three months of retention in dev/test and two years in production.

Written by the indexing model from the issue text.