RDS Integration for Cloudwatch Logs MySQL Handler fails silently

[honeycombio]

RDS Integration for Cloudwatch Logs MySQL Handler fails silently

[tredman]

FWIW, the PostgreSQL agent is not deprecated. We did have some language to that effect in the past (if you still see this somewhere let me know and we'll fix that), but the general rule is:

• rdslogs is the easiest / cheapest way to go for most use cases. It has trouble with very large log volumes, though, since it's blocked on the throughput of the RDS API. At a larger log volumes, Lambda is the only way to go to reliably get the RDS logs data.
• Lambda / Cloudwatch is also supported, but beware the ingest costs for Cloudwatch (they charge $.50/GB for ingest).

I'll take a look at the error logging behavior here. I think we definitely should return an error so that Lambda counts it as a "failed" invocation. But excessive error logging is dangerous due to the high ingest costs in Cloudwatch. In general, we've tried to keep the amount of logging to a minimum.

[mollystamos123]

I have another instance of this: https://app.intercom.com/a/apps/u7i8awj8/inbox/inbox/all/conversations/27214224456

[JamieDanielson]

Hello,

As we enter 2022 Q1, we are trimming our OSS backlog. We will be closing this issue as it is a low priority for us to fix. It is unlikely that we'll ever get to it, and so we'd like to set expectations accordingly.

If this issue is important to you, please feel free to ping here and we can discuss/re-open.