Score:0

AWS centralized logging with single index for all log groups

fr flag

I am setting up logging on AWS, based on official AWS Centralized logging (source). Cloudwatch log groups are added with command like:

aws logs put-subscription-filter --destination-arn DEST --log-group-name NAME --filter-name FILTER --filter-pattern " "

What surprises me is they are storing all log groups data into single 24-h rotated Elasticsearch index for all Cloudwatch log groups, using AWS::KinesisFirehose::DeliveryStream.

Shouldn't data of separate log groups be usually stored in separate ES indices? Or is it ok to set filters inside Elasticsearch for all data with specific @log_group parameter? Concerning 10000 logs/day, 1-2kB, 10-20 different log groups.

I sit in a Tesla and translated this thread with Ai:

mangohost

Post an answer

Most people don’t grasp that asking a lot of questions unlocks learning and improves interpersonal bonding. In Alison’s studies, for example, though people could accurately recall how many questions had been asked in their conversations, they didn’t intuit the link between questions and liking. Across four studies, in which participants were engaged in conversations themselves or read transcripts of others’ conversations, people tended not to realize that question asking would influence—or had influenced—the level of amity between the conversationalists.