currently VMAlert can match all VMRule objects, which makes no sense for rules, that are defined for type, that is not supported by VMAlert datasource.
since it's not planned for VMAlert to support multiple datasource types simultaneously possible solution is to add datasource type to VMRule labels and to VMAlert selectors to prevent such mismatch