Table of Contents
In ENS Events the current ENS events are displayed.
The following information is displayed for each event:
- Event type
- Processing status
- Added on
- Processed by
|ENS_ENABLED||ENS_was activated in MIDA and the MI Core settings for ENS were saved||None|
|ENS_DISABLED||ENS has been deactivated in MIDA||None|
|ENS_RECONNECT||Try to connect to the MI Core again on port 8883||None|
|ENS_SUBSCRIBE||Event type was subscribed||None|
|ENS_UNSUBSCRIBE||Event type was disabled||None|
|ENS_CHECK_CONNECTION||„Check“ was executed in the ENS settings||None|
|DEVICE_ENROLLED||Device has been registered and activated||Get information (details, labels/ apps) of this device from MI Core and create device in MIDA|
|DEVICE_CHECK_IN||Devices check in||General devices Query data from MI|
|DEVICE_NOT_COMPLIANT||Device not compliant||MI Core has received a „Not compliant“ message for a device. The device is marked accordingly in MIDA.|
With delay the data of the device is read from the MI Core, because MIDA receives the event before it becomes visible in the MI Admin Portal.( mida.ens.compliantHandler.delay)
|DEVICE_COMPLIANT||Devices is compliant again||A non-complaint device was detected as compliant again by the Mi Core and marked in MIDA. With delay the data of the device is read from the MI Core, because MIDA receives the event before it becomes visible in the MI Admin Portal.( mida.ens.compliantHandler.delay)|
|DEVICE_RETIRED||Device deregistered||Remove device from MIDA|
|DEVICE_APP_INVENTORY||Change to the App Inventory of a device||Changing the app inventory of an app. MIDA queries the MI Core for the installed apps on the device|
|DEVICE_CERT_INVENTORY||Change of certificates|
|UNPROCESSED:||Event was received from MIDA and stored in MIDA table|
|PROCESSING||Event is being processed. As a rule, data is requested from the MI Core|
|PROCESSED||Events have been processed. Normally, these successful events are removed from the ENS event table after 3 hours. Therefore, there should be no events in the table that are older than 3 hours|
More detailed information is displayed. For example, for device events the device UUID.
Other information, primarily for error analysis.
- not authorized to connect ENS user / password is not correct.
- MqttException (0) – java.net.UnknownHostException: emm-dev2.ebf.deXX
- Unknown MI Core
Event was entered into the MIDA database.
Event with status Failed can be executed again.
Existing events can be deleted (individually).