Skip to content

Add logging functionality #20

Closed
Closed

Description

@jthomerson

Activity

  1. added this to the 1.0.0 milestone on Feb 26, 2019
  2. added a commit that references this issue on Mar 5, 2019
  3. yokuze commented on Mar 5, 2019

    @yokuze
    Contributor

    We decided that the standard log object will include these fields:

    • level
    • msg
    • data

    When the log level is debug, or something more verbose like trace, then these fields are also added:

    • timer - the time, in milliseconds, since the start of the Lambda function request
    • remaining - the time, in milliseconds, left until the Lambda function times out
    • int - Interface. The type of Lambda event that triggered the request. One of APIGW or ALB

    Here are some other fields we considered, but decided were not necessary or that we won't add at this time:

    • time / id - not needed because they’re in the CloudWatch output
    • function - not needed because each function (typically) has its own log stream
    • memory - not needed because it’s logged in the execution report
    • route / method - come back to this later
    • sample - we can revisit when we add sampling (Consider adding support for sampling to logger #26)
  4. added a commit that references this issue on Mar 5, 2019
  5. added 2 commits that reference this issue on Mar 25, 2019
  6. yokuze commented on Mar 25, 2019

    @yokuze
    Contributor

    This was added with #27

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

Labels

No labels
No labels

Type

No type

Projects

No projects

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions