Likely more than one Hit Analyzer has Match Condtions that are matching for that specific Hit. Currently APM only stores a global SLA/OLA violation status which is set if the hit violates the SLA/OLA from any matching hit analyzer. Instead, APM ought to be storing the SLA/OLA violations with the hit analyzer match and allowing for searching hits that violated the SLA/OLA for that specific analyzer. This is being tracked has APMDATA-697: "Search hits that violate SLA for specific hit analyzer".
WORKAROUND
Make the SLAs consistent across all of your Hit Filters. Then it won't matter if multiple hit filters match the Hit.
STATUS
Waiting for fix in a future version of APM
