You can create a web request response status code or a HTTP response status code measure and set the evaluation to not equals or not contains. You should then be able to add this measure to the same incident with the and logic and test to see if it works.
Let me know if that works,
I haven't tested this but it should work.
First in the global AMD settings configure HTTP client errors - category 3 with all the error codes you want to exclude. Such as your 410.
The reason for this is there are four categories of HTTP client errors (4xx). Which are
So by specifying 410 and any others you want in HTTP client errors (category 3) you remove it from HTTP Other (4xx) errors so you can then just alert on that metric. You can also then adjust your availability settings so the 410s are not marked as failures.
Take note : The settings are global, which means that they apply to all analyzers reporting information on HTTP errors: HTTP, Oracle Forms, XML, and SOAP
So to do this
In global AMD settings edit HTTP client errors - category 3 ( i know the name is wrong)
add any codes you want to exclude
Then configure you alert for the metric HTTP Other client errors (4xx)
Hope this helps