logdna / logdna-cloudwatch Goto Github PK

This is getting crazy:

It's only for one small Lambda, I can't imagine the situation with more intensive Lambda 😅

After finishing #27, the unit and integration tests must be added to have, at least, 90%-95% coverage.

AWS is asking to update runtime nodejs14.x to nodejs16.x
I've just did it and everything seems to work fine. Would be great to update README

Create a CloudFormation template to quickly deploy the lambda

This wasn't mentioned in the README but what do you recommend for these values?
This is a screenshot of the default values:

Hi, are you please planning to upgrade this package to node 16 or later given that Node 14 will be at the end of their security support in about a month? Thanks

Similar to this, terraformize the lambda for easy deploy

Since we have been switching from using CircleCI to using Jenkins, this one should be updated as well.

After finishing resolving all the previous issues (i.e. #1, #26, #27, #28, #29, #30), update docs in all the required places.

Migrating from LogDNA-agent to the Lambda integration, our JSON logs are not properly formatted in the LogDNA web app. The JSON body gets converted to a string, and log lines displayed in the web app as a string.

In the interim, we made our own fork with a hacky fix that would break other use-cases. But we would like the upstream package to have better support for JSON formatted logs so that we do not have to maintain a patch.

Setup:
Follow these instructions (NOTE: The link to the zip file is an old version sitting in an S3 bucket, we downloaded the latest from github). We did port the instructions to Terraform, it is possible that something is different than what the manual instructions would produce, but I could not find a meaningful difference.

Steps to reproduce:

• Run an application with JSON formatted logs, ingest logs using LogDNA agent
• Run the same application, use the Cloudwatch->Lambda->LogDNA integration to ingest

Expected result:
The log lines look the same in the LogDNA web app

Actual result:
The logs lines look different, are not properly parsed as JSON data

Is there a delay before it appears in LogDNA?
My guess from the README was that it should be there just after creating the CW stream and events were sent.

It is required to implement the lambda in a very testable way which requires refactoring and restructuring by using @logdna/logger and eslint-config-logdna

The README is not really clear and should be updated (https://docs.logdna.com/docs/cloudwatch too)

What wasn't clear is:

• 1 - Create a new Lambda function and skip to the Configure function section I guess this was about an old interface? It's impossible to find the Configure Function section see screenshot below
  
• Before I could click on create, I had to create a role (this wasn't mentioned)
• Only after that I was able to click on Upload .zip from the Code entry type select input, and edit the handler see screenshot
  
• And the environment vars below

Hi! This is less of an issue, and more of an FYI. 😄 we created a Terraform module for deploying this lambda and thought you folks might like to check it out. https://github.com/asicsdigital/terraform-aws-logdna-cloudwatch

Hi there!

Thanks for the Lambda code, I think you should publish it on AWS Serverless Application Repository, it would be a lot easier to deploy and maintain ;-)

Is that something planned maybe?

I have replaced with the following line for a temporary fix.

const hostname = config.hostname || payload[0].meta.log.group;

Can you host the file on S3? No need to download the file that way - just copy and paste the URL in Actions->Upload a File from Amazon S3