Mysql CPU alerts and max_execution_time

Once every few weeks, I get an alert on my CPU being at 100% on my DO Managed MYSQL

I manually kill a query from DO logs and queries tab and it gets solved.

I’d like to avoid these in the future so I have tried:

• pool.query timeouts on my app, but that won’t kill the mysql query, it will just stop the execution on the app itself
• improved performance in many queries, but apparently some still trigger these issue once every 5000k executions or so, it has been a bit hard to know exactly when / why using DO logs
• setting max_execution_time but DO blocks me, saying i do not have permission (even with the main DB user)
• used to DO API to get the config values and read the API reference, but I can’t find max_execution_time, only other similar ones like innodb_lock_wait_timeout, net_read_timeout, net_write_timeout, wait_timeout… but according to chatGPT that’s not really the same

So how do I set a max timeout -or- how do i have access to kill queries that are taking too long?

When I was running my own mysql it was easy, but with DO’s limitations I’m a bit lost