Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Ensure that logs include the function Alias as part of the message so we can correlate activity between different Lambda aliases. #61

Open
mathomas opened this issue Jun 20, 2018 · 1 comment
Assignees
Labels
good first issue Good for newcomers

Comments

@mathomas
Copy link
Contributor

mathomas commented Jun 20, 2018

Perhaps we should use an actual logging package (so long as it has the same end effect as console.log() because that's what Lambda expects to send to CloudWatch).

@mathomas mathomas changed the title Ensure that logs include the Alias as part of the message so we can correlate activity between different Lambda aliases. Ensure that logs include the function Alias as part of the message so we can correlate activity between different Lambda aliases. Jun 20, 2018
@mathomas mathomas added the good first issue Good for newcomers label Jun 20, 2018
@krzysztofwasiak-wipro krzysztofwasiak-wipro self-assigned this Jul 4, 2018
@krzysztofwasiak-wipro
Copy link
Contributor

@mathomas I'd need some clarification here. The alias is already logged as a part of ARN at the beginning of each invocation, which btw has unique UUID, which could be used for corelation - isn't that enough? Would you rather see alias (PROD, TEST, etc.) per each line of log?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
good first issue Good for newcomers
Projects
None yet
Development

No branches or pull requests

2 participants