When we bring the environment down and restart it, our logs are lost. This is kind of a pain, but especially important for personal data logging (T200520), which is happening through the standard logging functionality.
Description
Description
| Status | Subtype | Assigned | Task | ||
|---|---|---|---|---|---|
| Open | None | T240153 Address project technical debt | |||
| Resolved | Samwalton9-WMF | T256465 Review need for Library Card platform logs | |||
| Open | None | T203685 Ensure that logs are saved even when the environment is recreated |
Event Timeline
Comment Actions
If we don't need to keep them around for a super long time, then we could just use an external event/log analytics service like https://timber.io/ or https://sentry.io/