Incident Detector Won't Detect ANY incidents

DeanMoiler

Hey Everyone,

 

I'm working with both Test & Production instances of GeoEvent server, of which I'm using an incident detector to fire Started and Ended emails when the statements are evaluated.

 

It's been working fine and had been working with simple statements like:

Opening:

  Status = 'Off'

Closing:

   Status = "On'

With the Off and On valued being generated by the GeoEvent Service itself, so erroneous white spaces aren't a likely culprit here.

 

For some reason these are no longer working in the Production environment, to the point where I cannot get an incident to fire for simple tasks in a newly created GeoEvent Service such as:

 

Opening:

  OBJECTID >0

Closing:

OBJECTID IS NULL

 

I cannot for the life of me figure out how to get the incident detector to detect any incidents at all. I can see in the event sampler that events are hitting the incident detector, but are never meeting an opening condition.

 

Is there anything obvious that I'm missing that could affect the incident detector in such a way?

 

Thanks!

 

Dean

EricIronside

Hey @DeanMoiler  

One thing to check is to make sure your GeoEvent Definition has a field tagged as TRACK_ID.  The Incident Detector will not create any incidents if the GeoEvent Definition doesn't have a TRACK_ID set.  

I know when you create an input and allow it to create the incoming GeoEvent Defintion, it doesn't set the TRACK_ID automatically for you.  You should make a copy of the GeoEvent Definition it created, set the TRACK_ID, TIME_START, and GEOMETRY tags, then switch your input to use that known definition. Once you do that, your Incident Detector should start working.