1 Comment
Oct 2·edited Oct 2

Couldn't agree more - we were spending $100k in cloudwatch logging costs at some point - crazy that our logging costs exceeded compute costs - developers were to blame as well as they were publishing millions of processing records to logs as well - however the near real time nature & indexing of all fields in cloudwatch seem unnecessary for most usecases & the exorbitant price - so we just pushed the logs to S3 and sent to enterprise splunk which we already had and some teams were sending it to Elasticsearch - both options cost us less than using cloudwatch

Expand full comment