We should look into adding turn-key solution for third-party logging integrations. Pantheon does not support syslog, and so they recommend you use the database watchdog provider. At least for live, we should use solutions besides the database provider as you want to keep as much logging data as possible, but this could result in a large database table that will slow down database copies. Also, if the database provider is not properly configured there is a risk that the table never gets truncated and grows forever. We've seen this on several inherited projects from past agencies that did not spot this issue (at one point I saw a log table that exceed 3GB).
We should look into incorporating more powerful logging tools such as AWS CloudWatch.
We should look into adding turn-key solution for third-party logging integrations. Pantheon does not support syslog, and so they recommend you use the database watchdog provider. At least for live, we should use solutions besides the database provider as you want to keep as much logging data as possible, but this could result in a large database table that will slow down database copies. Also, if the database provider is not properly configured there is a risk that the table never gets truncated and grows forever. We've seen this on several inherited projects from past agencies that did not spot this issue (at one point I saw a log table that exceed 3GB).
We should look into incorporating more powerful logging tools such as AWS CloudWatch.