You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
It would be super useful and more flexible to add the ability to tell the subscriber exactly which log groups to subscribe to by adding a tag name to the CFT parameters. Then the presence of that tag on a log group would indicate that a subscription should occur for the ingester.
This is easy to filter on for the auto subscriber lambda, you just add an eventName of TagLogGroup. Luckily, these two events have the exact same structure (they both include the list of tags and their values in the same place) so the body of the lambda doesn't have to change much at all there, just the addition of the filter logic.
The backfiller lambda though will require a little work as tags don't get passed back as a result of the describe_log_groups() call. Thus, for each log group, a call to list_tags_log_group() will need to be made for each log group. Once known tags are retrieved, then the loop for each log group would need to be adjusted to:
Determine if the log group should be subscribed to.
Determine if the log group is already subscribed to.
If the log group should be subscribed to but isn't, then subscribe to it.
If the log group should not be subscribed to but is, then delete the subscription.
If the log group should be subscribed to but is by a different lambda arn but the name ends in "-humio_ingester", then delete/create the subscription.
The text was updated successfully, but these errors were encountered:
It would be super useful and more flexible to add the ability to tell the subscriber exactly which log groups to subscribe to by adding a tag name to the CFT parameters. Then the presence of that tag on a log group would indicate that a subscription should occur for the ingester.
This is easy to filter on for the auto subscriber lambda, you just add an
eventName
ofTagLogGroup
. Luckily, these two events have the exact same structure (they both include the list of tags and their values in the same place) so the body of the lambda doesn't have to change much at all there, just the addition of the filter logic.The backfiller lambda though will require a little work as tags don't get passed back as a result of the
describe_log_groups()
call. Thus, for each log group, a call tolist_tags_log_group()
will need to be made for each log group. Once known tags are retrieved, then the loop for each log group would need to be adjusted to:The text was updated successfully, but these errors were encountered: