Managing Alerts

catapult is designed to send you precisely the alerts you want in real time in order to achieve this, there is an initial investment required setting up your alerts standard alerts when you managing devices docid\ oj7mhxgiplcn69gfjbfi6 , the device appears on the my devices page opening the device by clicking its name reveals the following alerts aggregate event indicates a change in the current tag list of a device for example, if a door is opened and an rfid tagged item, is removed, this alert will indicate that 1 item has been removed catapult will not include details about which tags or items were removed or added in the alert object event generated by a device when it boots up, once a day, and other various conditions the alert will contain the total number of items that were seen at that time sensor reading event includes readings from all the sensors a device is equipped with device type sensors fridges, freezers, cabinets temperature handhelds, trays none mobile cases signal strength battery level temperature latitude longitude range heartbeat event typically generated once an hour by a device indicating it is still communicating however, this is configurable by the device owner which may result in more or less frequent alerts missing communication a missing communication alert occurs when a device has not communicated for a number of hours this may be due to power loss at its location, poor internet connection, or some other situation the hours field is set to 0 by default this disables the alert from being ever sent to enable this alert, enter the number of hours the device can be out of communication before the alert is sent for example, consider the following scenario the value for a device has been set to 8 a device last communicated at 10am if no communication is seen after 6pm, the alert would be sent however, if the device starts communicating at 4pm, the 8 hour timer would be reset device types missing communication recommendation (hours) fridges, freezers, cabinets, surface read points 2, because these devices should communicate hourly mobile cases 25, because these devices should communicate at least nightly handhelds none, because communication is dependent on users and does not happen at a regular interval communication restore occurs when a device re establishes connection after a missing communication alert has been sent therefore, a missing communication alert must be set up for the device in order to receive communication restore alerts acpowerfailure occurs when a device loses its ac power connection and is running on internal battery back up acpowerrestore occurs when a device has its ac power connection restored temperature occurs when a device goes outside of its set temperature thresholds, either high or low however, temperature thresholds can be set by the device owner to values that would never occur, such as 100°c, thus resulting in you receiving no alerts temperaturerestore occurs when a device returns back to within temperature thresholds, either high or low however, temperature thresholds can be set by the device owner to values that would never occur, such as 100°c, thus resulting in you receiving no alerts adding alerts to enable, simply click on a gray email icon, which will color when enabled we strongly suggest always configuring an alert for the following events, since these will typically only alert when an action should be taken to preserve the function of the device and the integrity of its inventory missing communication (set hours according to the table above) communication restore acpowerfailure acpowerfailurerestore temperature temperaturerestore removing alerts to disable alerts, simply click on the enabled email icon, which will turn gray when disabled last occurrence the "last occurrence" column displays the last time that an alert was sent if the device experienced the event, but no alerts were configured to be sent, the "last occurrence" column will not be updated it is the last occurrence of an alert, not necessarily the event itself adding additional alerts at the bottom left of a device's alerts, there is a box where additional device events can be added and have alerts configured for them there is no limit to the number of logentryevents you can add the additional events you can receive alerts for is highly dependent on the device type go to the jetstream device documentation (linked below) for your device type and browse the logentryevents section to discover which logentryevents your device might send device type countertop cabinet docid\ qylhkyiv aib7jbg7bgtp directional read point docid\ jvvfciraa8j4mlgw4pzi handheld docid\ mwq ucnvczj5cgj upuje mobile case docid\ zfaaxxwarhrs 208ipdcq read point docid 4x9qqj6sajf3vbul1sqg1 rfid enclosures (cabinets, fridges, freezers) docid\ uxzf6ddof1t2zgzzjh9m6 security cabinets docid\ bqe4qp4tfhbc880tsbs1w surface read point docid\ gy rxnn62wfy57d0fsxxr let's say you have reviewed the additional logentryevents for your terso rfid freezer and determined you want an email alert when the dooropen event occurs, so you can quickly close the door and preserve product integrity on the my devices page, open the device you wish to add an alert for enter the logentryevent name exactly in the field at the bottom left it is case sensitive in this example "dooropen" the new event now is added as a row can have email alerts set for it in this example, you should also add the "dooropenrestore" event and set an alert for that as well, to 'close the loop' when the issue is resolved