logs: SubscriptionFilter does not provide metric* helpers

[arnab]

The AWS Logs SubscriptionFilter construct should provide metric* methods that CDK resources typically provide. See for example:

• CDK metric objects documentation
• CDK Lambda Function#metrics* methods

Use Case

All SubscriptionFilter metrics (e.g. see ForwardedLogEvents, DeliveryErrors, DeliveryThrottling in the Monitoring AWS Logs with CloudWatch Metrics docs) requires some dimensions to be specified:

• LogGroupName
• DestinationType
• FilterName

The first two are easy to specify since the LogGroupName is also required while creating the construct and DestinationType a service name (e.g. Lambda). However, there appears to be no way to get FilterName using CDK:

• The CDK construct (and the underlying CloudFormation resource: AWS::Logs::SubscriptionFilter) does not let me specify the FilterName - so it can't be directly specified ( and is always dynamically generated).
• There are no properties on the SubscriptionFilter object that will return this.
  • In fact, unlike most other CDK constructs, this one seems pretty bare and returns absolutely no information about the resource.
• The synthesized FilterName is like MyStackName-MyLogicalID29669D87-GCMA0Q4KKALH (in CloudFormation): so it can't directly be specified using a Fn.ref (since the logicalId for CDK constructs is dynamic). Possibly related to: CDK Refactoring Tools aws-cdk-rfcs#162.

Proposed Solution

• Please provide metric* methods on SubscriptionFilter construct.
• Also provide properties on the SubscriptionFilter construct to get references to properties, such as the related logGroup (which is required as a constructor argument), like most CDK constructs.

Other

For more details, see this StackOverflow question.

As shown in the SO post above, a possible workaround is to use the Stack#getLogicalId method.

• 👋 I may be able to implement this feature request
• ⚠️ This feature might incur a breaking change

---

This is a 🚀 Feature Request

[github-actions]

This issue has not received any attention in 1 year. If you want to keep this issue open, please leave a comment below and auto-close will be canceled.

[arnab]

I was away and not watching my email. Not sure why this was auto-closed without any details of the fix.

Can you please re-open this (I don’t seem to be able to)?

[peterwoodworth]

Sorry about this @arnab, we have automation which closes issues if they haven't had any activity in over a year. Thanks for letting us know 🙂