Mgmt: We need performance metrics' comparison for those 2 tests ASAP, we'll ping you every 5 minutes

AWS Cloudwatch: *unusually slow - takes ~2 minutes to add/remove a metric or change the timeframe*

Me: *fuck*

AWS Autologout: "Let me just intervene here right before you take that screenshot that took you 1.5 hours to filter out..."

ME: *runs a load test for the umpteenth time*

RDS DB: *is slow af: HI contentions*

ME: "dear AWS support, I see the RDS has troubles writing to disk as THIS db exhibits 10x higher W latencies than THAT OTHER db we have. Both are identical, apps are identical."

AWS: "Hello, I hope you have a good day. After the investigation that took us almost 2 weeks, we can confirm that there are 10x higher IO latencies to disks: [CloudWatch link]. We also see a high load average during your tests.

We recommend investigating the high load average and tuning your queries along with the database.

I hope this helps, good day."

ME: *are you seriously calling this PREMIUM support package....?*

The CloudWatch API is an awkward piece of shit.
No convenient way to just ask for the latest value of a metric. Gotta supply a time window and hope metrics were actually reported within that window.

Oh and make sure your timestamps are in ISO 8601 or the request will fail (but the SDK does zero validation so a unit test won’t catch it of course).

Oh and you have to assign an arbitrary ID to each metric query in your request even if you don’t care about mapping the results back to the queries. And the regex for the ID is just fussy enough to be mildly irritating.

I was just playing with Eventbridge for research for a potential project, and I wanted to test setting up a Cloudwatch Logs target. I go to set up my target, click save, and am presented with "Resource limit exceeded".

After some digging in my browser's network inspector, and some googling, I discover that the account has reached its quota of Cloudwatch Logs resource policies, which can't even be viewed in the console, only the API and CLI.

Is network debugging and StackOverflow really the intended method of troubleshooting this issue? What the hell was I supposed to do with "Resource limit exceeded" and no further info?

FUCKING CLOUDWATCH
I'm so close to a mental breakdown.
If I had a penny for every second wasted by its loading spinner, I could already sip cocktails on my own yacht.

Every time I have to use CloudWatch, I feel like I'd be more productive if I shoved glass shards in my eyes.

Every query/filter either returns nothing or errors out because too much is returned.

could anyone help me calculating costs for AWS and Google Colab Services? I find it quite intransparent...

i would like to host 1x Python App which runs once a day or week (API call, enrichment uf JSON, JSON 2 CSV, FTP transfer). runtime is probably a few seconds, something between 1 and 5.

in AWS i created a Lambda function and for scheduling i guess i need CloudWatch. what really grind my gears is the combination of free contingent and paied service - i really don't have an overview right now, so my question here: how could i calculate it and what would be the monthly/yearly costs?

in Google Colab created a notebook and for scheduling i would need Google Cloud Scheduler. as far as i understand the hosting of the notebook is for free and the costs of cloud scheduler is $0.10 per job per project per month. 3 are for free. so 1 project, 1 job = scheduler for free?

Also, i'm open for other services such as digital ocean droplets or similar.

thx in advance for your help!