*sigh* InnoDB doesn't allow reset to 1. I tried it on testwiki.

More info: https://stackoverflow.com/questions/8923114/how-to-reset-auto-increment-in-mysql#8923132

Note that you cannot reset the counter to a value less than or equal to any that have already been used. For MyISAM, if the value is less than or equal to the maximum value currently in the AUTO_INCREMENT column, the value is reset to the current maximum plus one. For InnoDB, if the value is less than the current maximum value in the column, no error occurs and the current sequence value is not changed.

One other way to do it is to create a temp table and move it around but that'd be really complicated :/

Here is the thing. It won't run out of value any time soon (probably never) but since it's already pretty high, it'll trigger alerts.

Maybe we can make a way to exclude tables or whitelist them?

yeah but it's dangerous, for example what if the same bug gets re-introduced again and start increasing the value too fast?

Yeah, I see...but the solution is very complex and risky just to keep an alert in green state. I'd rather have the alert in place and then being able to silence this table than having no alert at all :)

Would it be difficult to increase the alert threshold of this value to something like 80% while keeping all other values at the default value?

That sounds good to me.