search

logdna / logdna-cloudwatch

AWS Lambda for logging from CloudWatch into LogDNA
MIT License
12 stars 19 forks source link

It creates a new host in LogDNA Sources for each lambda instance! #5

Closed Jolg42 closed 5 years ago

Jolg42 commented 5 years ago

This is getting crazy:

screenshot 2018-07-23 at 10 51 01

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

Jolg42 commented 5 years ago

Also the name of the host shouldn't be the name of the log but the name of the Lambda?

smusali commented 5 years ago

Hey @Jolg42, thanks for reporting the issue! I can see the problem and I will fix it asap.

smusali commented 5 years ago

@Jolg42, update Lambda function and ZIP file - set the lambda function again in the same way.

As a hostname, we have decided to take instance id which is the last part of logStream - so, for the logs coming from each instance will have separate hostname - you can use LOGDNA_HOSTNAME environment variable while setting the lambda function up if you want the hostname to be stable and the same for all logs sent by the same function.

Again, we are very thankful to you for mentioning this problem.