You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I am no Node programmer, but I have had a look at the Lambda code from the AWS console and if it is the Lambda function which is escaping these quotes, it should be in line 74, where the data is prepared to be sent to Loggly:
// get all the events, stringify them and join them
// with the new line character which can be sent to Loggly
// via bulk endpoint
const finalEvent = parsedEvents.map(JSON.stringify).join('\n');
I suspect the stringify operator needs to cater for special character like double-quotes which are being passed from AWS. The operator takes two other optional parameters - not sure if that can help in stripping the double quotes.
I also believe the RDS enhanced monitoring logs are unique in the sense that they are in JSON format and using quotation marks for the keys. Other CloudWatch logs might be in plain text which can explain why the Lambda function has no issues sending them to Loggly without any escape characters.
Thanks
Sadeq
The text was updated successfully, but these errors were encountered:
Sadequl Hussain
I am no Node programmer, but I have had a look at the Lambda code from the AWS console and if it is the Lambda function which is escaping these quotes, it should be in line 74, where the data is prepared to be sent to Loggly:
I suspect the stringify operator needs to cater for special character like double-quotes which are being passed from AWS. The operator takes two other optional parameters - not sure if that can help in stripping the double quotes.
I also believe the RDS enhanced monitoring logs are unique in the sense that they are in JSON format and using quotation marks for the keys. Other CloudWatch logs might be in plain text which can explain why the Lambda function has no issues sending them to Loggly without any escape characters.
Thanks
Sadeq
The text was updated successfully, but these errors were encountered: