Itron Enterprise Application Center (EAC) events

The device is no longer receiving registration messages from the agent. The event is logged when the alarm is noted and when it is cleared. This event can indicate an issue with the agent, monitor, or container. This event is occasionally logged when a container is restarted during application installation.

Agent data is unsuccessfully removed during Purge Application job on Gen™X devices with ApplicationServices (AppServ) version 1.5.104 or newer. See event code 1131.

Logged whenever a Purge Application job is completed successfully on Gen™X devices with ApplicationServices (AppServ) version 1.5.104 or newer. One event is logged for each agent on the meter (see event code 1131).

Generated at the beginning and end of a user-initiated Disable Agent job. The event summary text will provide more details.

Logged when an agent has been manually disabled by a user through the EAC.

Generated at the beginning and end of a user-initiated Enable Agent job. The event summary text will provide more details.

Agent has faulted.

An agent on the device is not running because it does not have a valid active license. Uninstalling an application, an application license expiring, or a download-only installation job can trigger this event.

Agent reports a CPU alarm. This event is logged when the alarm is both triggered (agent reports above CPU limit for 30 consecutive seconds) and cleared (agent reports below CPU limit for 10 consecutive seconds). The event summary text indicates which agent has the issue.

Agent reports a memory alarm. This event is logged when the alarm is both triggered (agent reports above memory limit for 30 consecutive seconds) and cleared (agent reports below memory limit for 10 consecutive seconds). The event summary text indicates which agent has the issue.

Logged when the monitor for the agent on a device has stopped.

This event is not currently used.

Generated whenever the onboard device monitor detects the agent status on the device is anything other than Running. Possible triggers include the agent crashing unexpectedly or a system restart.

An application encounters an issue when registering. This can include a missing resource.

An error occurred when test signing the agent as part of application version approval work flow. The event summary text will contain additional details.

Agent was not successfully removed.

Agent was successfully removed.

Generated on the device when an agent on the device is forced to restart for any reason.

Attempted restart of the agent failed.

Agent is attempting to restart.

Agent that was stopped has reported as Running.

Agent status is temporarily unavailable.

Agent has reported as stopped. For example, it was manually disabled, the agent registration timed out, or there is a delayed application start.

Logged when an application has been uninstalled from a device. Can be generated by a successful Uninstall Application job.

Generated at the beginning and end of a user-initiated Download Only install job. The event summary text will provide more details.

Application reports as faulted.

Generated at the beginning and end of a user-initiated Install License install job. The event summary text will provide more details.

Generated at the beginning and end of a user-initiated Install Application job. The event summary text will provide more details.

Notifies a user at automatic increments that their application license set is nearing expiration. Generated automatically when a license set has 1, 7, 15, 30, 60 or 90 days until expiring.

Generated when an Itron Admin deletes a license set (Admin is the only role that can perform this action).

Generated when an Itron Admin edits an existing license set (Admin is the only role that can perform this action).

Logged to the individual application history tab whenever a license is requested or issued by a user.

Generated automatically as part of meter replacement when the old meter being replaced has applications installed. Applications that were installed on the old meter are automatically installed on the new one. This event is logged at the start and completion of each app install to the new meter.

Application on the device has transitioned from Stopped to Running as a result of a user-initiated Start Application job. See event code 1102.

Generated at the beginning and end of a user-initiated Start Application job. The event summary text will provide more details.

Generated at the beginning and end of a user-initiated Stop Application job. The event summary text will provide more details.

Application on the device has been stopped. This is typically because the user has executed a Stop Application job against the endpoint. See event code 1103.

Application version has been published by a user.

Application version approval request failed, either manually (via Certifier rejection) or via rejection by the gateway. Application version transitions to a rejected state ("Denied by gateway" or "Denied for store").

Generated as an application transitions through the signing approval process, from creation to final approval and publishing. Many of the states along the way have their own subscribeable events (see event codes 20 - 31).

Generated at the beginning and end of a user-initiated Uninstall Application job. The event summary text will provide more details.

Generated at the beginning and end of a user-initiated Update License job. The event summary text will provide more details.

Generated at the beginning and end of a user-initiated Upgrade Application job. The event summary text will provide more details.

Utility user has approved the application version for installation on their own tenant devices. Logged once the utility user selects "Approve for Installation" on an application in "Pending Utility Review" state.

Utility user has denied the application version for installation on their own tenant devices. Logged when utility user selects "Deny for Installation" on an application in "Pending Utility Review" state.

Logged to the application history tab whenever the visibility of an application is changed and saved.

Generated at the beginning and end of a user-initiated Update AppServ Version job. The event summary text will provide more details.

AppServ version changes on a device as a result of an AppServ update. The summary text contains the from and to versions. AppServ is updated on a device either manually (using the AppServ update job) or automatically during an application install that requires a higher compatible version of AppServ on the meter.

Indicates that an AppServ update failed and the device was forced to rollback to a previous version of AppServ.

Logged if there is a failure during Calculating Config stage of a job (for example, stopping the install job while it is waiting for device interrogation responses).

Communication with the container has been lost. This event is logged when the comms are both lost and regained. The event summary indicates which container has the issue.

Container reports a CPU alarm. This event is logged when the alarm is both triggered (container reports above CPU limits for 30 consecutive seconds) and cleared (container reports below CPU limits for 10 consecutive seconds). The event summary text indicates which container has the issue.

Container reports a memory alarm. This event is logged when the alarm is both triggered (container reports above memory limits for 30 consecutive seconds) and cleared (container reports below memory limits for 10 consecutive seconds). The event summary text indicates which container has the issue.

Container reports it has restarted.

The device has been deprovisioned from the head-end system (for example, OpenWay^® Collection Manager or UtilityIQ^®) and is no longer available for inclusion in jobs. Deprovisioned devices are no longer visible in device groups in the EAC.

A device group has been deleted by a user.

Logged when a device has not responded to interrogations for 48 hours.

Generated on the device when Field Deployment Manager (FDM) Tools is used to disable an agent.

Generated on the device when Field Deployment Manager (FDM) Tools is used to enable an agent.

Generated on the device when Field Deployment Manager (FDM) Tools is used to remove an agent.

Generated on the device when Field Deployment Manager (FDM) Tools is used to restart an agent.

The required agent has been successfully downloaded to the meter as part of the application install job.

The required agent was not successfully downloaded to the meter as part of the application install job. Logged in the case of either failure or user cancellation. Event summary text for each device will contain additional details.

Generated on the device during an application installation job when there is a missing GUID issue with the Agent Global Request call.

Job fails during temp group creation and process is aborted (for example, a timeout expires). The event is logged to each device in the group.

Job fails during group enrollment and process is aborted. The event is logged to each device in the group. The event summary text will contain additional details.

Application install fails because the device has insufficient available resources, such as memory or CPU.

Logged whenever a job is automatically paused by the system due to an unhealthy response from the gateway. All unhealthy synchronous responses from the gateway other than a 400, 404, or 409 will cause the job to enter a paused state. Receiving a synchronous response but no asynchronous response will also cause the job to enter a pause state.

Logged automatically when meter interrogation identifies an active license on a meter that differs from the license the EAC is expecting on the meter. Where it is safe to do so the EAC will automatically reconcile this condition. When this happens, a license for the application is consumed from an existing license set where appropriate.

Generated when license decryption identifies an incorrect format for a valid license

The device was unable to decrypt the application license.

The license set in use by this device for this application has expired (the current date exceeds the expiration date of the license set in use by the device). To continue using the application on the device, the license installed on the device must be updated.

Licensed application version and agent version are not in alignment. For example, after an application was installed, Field Deployment Manager (FDM) Tools was used to force the agent to an incompatible version.

Generated when Itron's library returns a failure. This is not a common scenario.

Interrogation received for a meter not previously in the system.

Generated when a Membership Unknown response from the head-end system is received.

The ProdAbbrev attempted to add a meter to a group, but the meter does not exist in the head-end system (for example, OpenWay^® Collection Manager or UtilityIQ^®).

Generated at the beginning and end of a Purge Application job. The event summary will show the start and end date/time of the job. Purge jobs start automatically on the older meter being replaced in a meter replacement job. They also happen automatically when a deprovisioned device is brought back online. There is no way to manually launch this job.

ESN Not Found response received from Itron systems during the group enrollment phase of an application install job.

Max Group Assignments response received from Itron systems during the group enrollment phase of an application install job.

No Config Group Assigned response received from Itron systems during the group enrollment phase of an application install job.

Invalid ESN response received from Itron systems during the group enrollment phase of an application install job.

Device is removed from a temp group during application installation either naturally or because it is not responding.

When a meter swap is initiated via service bus, this event is logged to the new meter that is being used to replace the old one. The summary text contains the ESN of the old meter that is being replaced.

Minimum required agent outcome data is not being received by the DI App Platform.

After an Outcome Reporting Insufficient (code 4006) event, minimum required agent outcome data is now being received by the DI App Platform.

Logged to the device automatically whenever a Pass-through job does not complete.

Ping job for a device or group of devices times out.

Successful ping of a device or device group.

Triggered when any policy violation occurs. The details of the agent/feature and type of violation are reported in the event summary.

Application version is approved by the signing server and ready to be published by the Certifier user.

Install job is aborted due to an error during staging (for example, firmware with an invalid hash or no response from the server). The event is logged to each device. The event summary text will contain additional details.

Application version has been submitted to the Itron Certifier for review and approval as part of the application approval work flow.

An error occurred that is not mapped to an existing event.

Update Status job times out due to devices not responding.