anchor.diff:  include::scripts/7-get-alerts.sh[tags=public]
   ----
   
  -NOTE: in the future the `event_id` may become an array of event IDs.
  -
  -NOTE: the `?trigger=id` and `?after=date` query params will soon be provided to make this polling process somewhat more palatable.
  +The query parameter `?triggerId=id` is provided to allow the list to be filtered to only the alerts of interest.
  
positive.code: ----
  {
      "title": "High Severity",
      "condition": {
          "eventtype_ids": ["{{eventtype_id}}"],
          "query": { "query": { "match_all": {} } }
      },
      "job": {
          "userName": "test",
          "jobType": {
              "type": "execute-service",
              "data": {
                  "serviceId": "{{serviceId}}",
                  "dataInputs": {},
                  "dataOutput": [ { "mimeType": "application/json", "type": "text" } ]
              }
          }
      }
  }
  ----
  
  In this example, the job will be executed only when our "US data found" event occurs with the specific problem being that a US bounding box has been found with a severity of 4.
  
  NOTE: the "type" field of the "condition" will likely be removed in the future, as the query DSL allows us to specify the event type directly within it; this would open up the possibility of having a condition based on multiple events.
  
  
negative.code: [source,json]
  ----
  {
      "eventTypeId": "98fc25e8-bd97-4444-a972-c06aa0f0edf1",
      "data": {
          "filename": "dataset-c",
          "severity": 5,
          "code": "PHONE"
      }
  }
  ----
  