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

Provide a Way to customize log stream name with Lambda Cloudwatch Logger #26

Open
brcolow opened this issue Sep 19, 2020 · 0 comments
Open

Comments

@brcolow
Copy link

brcolow commented Sep 19, 2020

I apologize that this issue is not strictly on topic for this project. Perhaps it could be forwarded to the right Cloudwatch devs?

I posted this on the AWS Developer Forums but didn't receive any replies.

I have copied it below:

From my understanding anything written to stdout/stderr during the invocation of a Lambda will be written to a log stream corresponding to that invocation and a log group corresponding to what lambda is running.

Currently the format of the default log stream name looks like:

"2020/08/21/($LATEST)579c5fcbef68455492a8a1a034475fdd"

Which is probably some type of template like:

"$DATE/($VERSION)/$HASH"

(For some reason square brackets were being rendered as a URL so I replaced them with parentheses)

It would be super helpful if there was a way, possibly only when using a custom runtime if that makes it easier to implement, that one could specify the log stream name template that the lambda auto-generates during an invocation. I don't think that the async lambda log aggregator/uploader that reads stdout/stderr is open source, so I am not sure how it actually works but maybe it could be configured early on in the custom runtime initialization using something like a system wide environment variable?

When browsing logs it would be so awesome to at-a-glance be able to see certain identifiers in the log stream name to narrow down what I'm looking for.

Another possible way to implement this would be to allow for adding "tags" to a log stream like we can currently do for log groups.

If anyone knows a way to implement something like this currently, let me know. I don't think there is though and so this is more of a feature request.

Thanks very much.

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

No branches or pull requests

1 participant