I'm using the ompgsql module to insert log messages directly to a Postgres DB. Further, the logs are in JSON prefixed with the @cee
tag and are being inserted into a JSONB
column.
It so happened that my app was generated a JSON log message which was very large, and it was being truncated by rsyslog, resulting in an malformed JSON, which was then being silently rejected by Postgres.
For now, I have bumped up the $MaxMessageSize
to 64k
, but that is not a foolproof solution.
What is the best way to handle such a scenario?
与恶龙缠斗过久,自身亦成为恶龙;凝视深渊过久,深渊将回以凝视…