Expose setting logging configuration per method

This is a Feature Proposal

Description

This may be marked as a duplicate of #1918 but I don’t believe it is a duplicate.

I would like to see the ability to specify logging configuration at the http event level. So something like this:

functions:
  api:
    name: ${self:provider.stage}-api
    handler: wsgi.handler
    environment: ${self:custom.env.environment}
    events:
    - http:
        method: GET
        path: /user/{user_id}
        logging:
          level: INFO
          metrics: true
          dataTraceEnabled: false

Similar or dependent issues:

• #1918

[pmuens]

Thanks for the feedback and the description of the use case @briguy202

but could there perhaps be a section within each function block that would allow for platform-specific properties?

Yes, that’s exactly what we’re going to do in the future. We’ll prepend everything with the provider. So e.g. aws-logging.

Generally speaking we’re looking at issues where we got the most feedback and which provide the most value for the largest chunk of users. It’s always the problem of great, new functionality vs. adding technical debt.

However there’s always the possibility to write a plugin which supports the requested functionality. Sometimes in the past we’ve migrated the plugin codebase into core after seeing a widespread adoption and need for the plugin.

[HyperBrain]

I will add this feature (including all other possible stage configurations like throttling, caching, etc.) to the alias plugin. See https://github.com/HyperBrain/serverless-aws-alias/issues/57. Even if you do not make use of aliased deployments, you can benefit from the feature.