Iterate over log events & post them individually

[dgarlitt]

CloudWatch often bundles multiple log events together in the event input
archive that is passed in the lambda's event argument. Since the lambda
was only doing a single post to the collection, that post would in many
cases actually contain multiple logs which would then show up as a
single concatenated log in the collection resulting in incorrect metrics.

This change iterates over the log events in the archive and posts them
individually to the collection.

[duchatran]

Thanks @dgarlitt! I notice the code to extract and include RequestID as a separate field in the JSON to Sumo was removed. Since this was actually requested by some customer, it would be good to have it back. I am thinking about making it optional if not everyone needs it.

[dgarlitt]

@duchatran Good catch, it's updated to include that logic.

[dgarlitt]

@duchatran I just updated this commit again to adjust the formatting on the options object at the top so that they are all in line. It was strictly cosmetic. Let me know if there are any other concerns about this pull request.

[duchatran]

Thanks @dgarlitt. Sorry for not getting back sooner, was caught up with something else. Let me do some test and then I will merge this.

[dgarlitt]

👍 Thanks!

[thoean]

context.fail and context.succeed allow to pass in a string value. Changing your code to this might be a nice optional addition:

if (requestsFailed > 0) {
  context.fail(requestsFailed + " / " + (requestsFailed + requestsSent) + " events failed");
} else {
  context.succeed(requestsSent + " requests sent");
}

[dgarlitt]

@thoean I amended the commit to include the change regarding your suggestion on adding info to context.fail(). Github is having issues right now, so it may be a bit before the "Checking for ability to automatically merge..." status goes away.

[dgarlitt]

@thoean Added info to context.succeed() as well. Good suggestion, btw.