Specify Log group name for Functions

[dinvlad]

Would it be possible to override Log group name for each function? Currently, CloudFormation creates one with a random suffix according to the Function's name. I don't mind these suffixes in Function names, however if we delete the stack, the log groups remain there and it gets much harder to navigate them (basically, each stack recreation generates a new set of log groups with the same prefix but a different suffix). I'd prefer to log everything into a single group, but just different streams.

Thanks

[dinvlad]

I guess this could be solved by specifying a fixed Function name now. Please re-open if someone still needs custom logging (though I don't think this is supported by AWS::Lambda::Function either).

[kbalakumar]

hi,

I ideally would like to define standards for all log groups, so not able to define the log group for each function or apiGateway is not ideal.

Is there anyway to specific log groups for each of these resources like apiGateway or Lambda function?

Thanks

[kbalakumar]

btw, how do I reopen this issue? @dinvlad

[jfuss]

@kbalakumar What do you mean by 'would like to define standards for all log groups'? Are you wanting to control the name of the log group, the retention period, or something else?

[kbalakumar]

@jfuss yes you are right. The naming and the retention period. Also we may have to retain old versions in some cases, all these scenarios we need to define the log group ourselves. Hope it make sense.

[dinvlad]

Alas we're using GCP now - feel free to keep this issue open

[jfuss]

@kbalakumar Naming for Log Groups for Lambda (not sure on Api Gateway) is not supported. This is the current limitation by the service.

Retention period is being handled in #257.

Closing this as a duplicate of #257.