Exclude criteria for aggregators

A exclude textarea doesn't know what to exclude on? What we should do is expose the operator, and then support IN and a comma separated list?

Might have misread the issue a bit, a generic implementation is not possible but we can use this feature in the dblog and past sensors:

* For those two, add a textfield that says excluded types (for dblog) and excluded machine names for past (past could have two fields, excluded machine names and modules).
* Each line is an entry, you could display a description of known types by collecting them from what's in the database right now (select distinct type... )
* If you have any, exclude in the query you build.

By default, the dblog warning sensor should exclude the 'page not found' type and the error sensor should exclude 'form'. Once we have a php notice sensor, we might also want to exclude php from the notice and warning sensor and track them separately.

As discussed with Miro:

In 8.x, we have a conditions UI, that doesn't exist in 7.x. With conditions, you can have a numbers of <> conditions to achieve this.

in 7.x-1.x, we don't have that and will likely not backport it. So a solution as suggested above should probably be implemented in that branch, which requires custom sensor classes for dblog and past.

Note:

This can be done on 7.x through $conf:

$conf['monitoring_sensor_info']['dblog_event_severity_error']['settings']['conditions'][] = ['field' => 'type', 'value' => 'form', 'operator' => '<>'];

Same for past:

$conf['monitoring_sensor_info']['past_db_event_severity_error']['settings']['conditions'][] = array(
  'field' => 'machine_name',
  'value' => 'form',
  'operator' => '<>',
);

We should probably just add those by default to those two sensors.

Added default conditions to both sensors.

Sorry wrong patch.

Setting conditions just to 'error'.

This is the way.

I checked and fails are related to the commerce module (?)