Hello Adam / Chris -
Thank you Chris for jumping in with advice on this ...
My apologies to those of you who checked the product gallery prior to 22-March-2014, when new processors such as the Track Gap Detector were available in the released product, and could not find tutorial documentation. The tutorials on are updated periodically, as quickly as we can get to them.
In Module 5 of the most recent update to the product introduction tutorial there is an exercise specifically covering the Track Gap Detector.
The fundamental design behind the Track Gap Detector is to listen for events, cache received TRACK_ID values, and when a given track has not reported for a specified period of time - begin broadcasting notification events that expected data is no longer being received. The intended use was for vehicles or other assets in a well-known reporting group. The processor is not setup for monitoring an inbound connector to determine that a data provider itself has gone off-line.
As Chris suggested, you could use a Field Calculator configured with a constant string for the processor's expression and add a generic TRACK_ID to all events from a particular data provider. I would configure the Field Calculator processor to create a new field, of type String, and apply the out-of-the-box TRACK_ID tag to the new field. Remember when working with string values to enclose literal strings in single-quotes in the processor's expression field.
Hope this information helps -
I was doing something similar with Automated Flight Folowing, I ended up writing an application in c# that would send the request again. What Also could be done is you could create your on TCP transport-Adaptor that would be specific to that Port/Service etc-- when It senses the connection has been dropped resend the connection request. To dev your own transport is pretty simple--It's in Java and uses maven but is not too scary
We have just today completed rework to the Notifications tutorial using the 10.3.1 product release and are copy editing the tutorial now. There are some changes to screenshots illustrating how to configure the outbound connectors for notifications, but the existing Notifications tutorial (10.2.x) should be sufficient to help you design e-mail notifications. We should have an updated Notifications tutorial uploaded this week or early next week.
The notifications tutorial covers how to design GeoEvent Services to generate SMTP e-mail notification, SMS Text notification (which also relies on SMTP), as well as XMPP Instant Message. You should not expect to find help on how to configure an e-mail notification output, for example, in the product introduction tutorial. Some topics have to be split out to different tutorials as we work to manage the scope the product introduction tutorial - by far our largest tutorial. A 10.3 revision for the product introduction tutorial was released early February 2015.
The product team works to update the tutorials as quickly as we can get to them. Many of the 10.3 connectors (Twitter, Instagram, etc.) had not been uploaded simply because their tutorial had not been updated so we didn't consider the offering complete. We've recently adjusted our release criteria and at least upload compiled *.jar files on the Gallery even if a revised tutorial is not available.
If we have to release a connector without a tutorial, you'll find a README in the bundle you download indicating that content and exercises in the previous version's documentation should provide sufficient information to get started using the upgraded component ... just be aware minor differences could exist between the content, exercise steps, and screenshots as you are going through it.
Tutorials are available on the ArcGIS GeoEvent Gallery. If the content provided by an earlier release of a tutorial does not answer questions you have, please e-mail the GeoEvent Team at email@example.com and let us know. Please include GeoEvent Tutorial Feedback in the subject of your e-mail. This will help us determine which tutorials are the most important to the user community at large.