Alert Console

The Alert Console feature allows corporate users to view an Alert page showing logged events for replication errors, connectivity errors, application errors, hardware errors, update errors, and version errors.

If you set up email alerts (see To Set Up Critical Alert Email Recipient Addresses), an email with critical alerts details will be sent to the designated recipients. To define severity-level thresholds, see Alert Threshold Settings.

You must have the Alert Console privilege to use this feature.

From the Oracle Retail Xstore Office menu, select Support Tools - Alert Console, or click the Alert Console link in the Support Tools panel.
The initial Alert Console page provides summary-level information at a glance about any issues at the stores in your organization requiring your attention.

The system defaults to the current date and shows the date and time the Alerts Console was last updated.

Figure 10-1 Alert Console Page - Business Date Field

To review alerts from previous dates:
- enter the date in the Date field, or select a date from the calendar,
- or use the Previous Day and Next option.

About Alerts

A background process is responsible for reviewing events published to Xcenter (a part of Oracle Retail Xstore Office) and determining whether to create a new alert, or update an existing alert based on currently configured severity thresholds and rules.

If there are any alerts, the console window will show the following information:

The severity of the event: Critical, High, Medium, Low.
The time the event was logged.
The store where the event occurred.
The type of event.
The number (#) of times the event occurred.

Figure 10-2 Alert Console With Alerts

Replication

Click a logged event in the list to view additional details.

The logged events, "Xstore replication queue errors" and "Xstore replication backlog" and "Xcenter persistence failure" are sourced from Xcenter's rpl_replication_data table.

Figure 10-3 Replication Logged Events Detail

Replication Logged Events

Xcenter persistence failure: A replication request was delivered to Xcenter but could not be persisted to the Xcenter DB. As a result, a record was written to the rpl_replication_data table. Information returned includes replication payload and meta data. (Xcenter)
Xcenter replication crash: These errors are event Log error codes reported by the replication system. (Repl Crash)
Xstore replication queue errors: An error failure occurred during replication. As a result, records are still in the register's replication queue. Information returned includes replication payload and meta data. (RepQ Process)
Xstore replication backlog: There are more than "X" records in the replication queue that have not been tried, indicating a backlog or potential mis-configuration. Information returned includes replication payload and meta data. (RepQ Block)
Xstore replication queue read errors: An error occurred when pulling data from the local replication queue. (RepQ Read)

Connectivity

Click a logged event in the list to view additional details.

The logged events shown here are sourced from Xcenter's ctl_event_log table.

Figure 10-4 Connectivity Logged Events Detail

Connectivity Logged Events

Data source offline: A ping failure or data access error occurred. As a result the data source will not be used. Information returned includes datasource name, scope (WAN/LAN), and cause. (DB Offline)
Payment system offline: A payment systems host (Xpay) could not be reached. Information returned includes the message, stack trace, and destination IP/Host. (Xpay Offline)
Order broker service offline: The order broker host (Oracle Retail Order Broker Cloud Service) could not be reached. Information returned includes the message, stack trace, and destination IP/Host. (Oracle Retail Order Broker Cloud Service Offline)
Order broker service error: An error occurred during the order update process. Information returned includes message and stack trace. (Oracle Retail Order Broker Cloud Service Error)
Service error: An error occurred while calling a web service. Information returned includes message, stack trace, and destination IP/Host. (Service Offline)
Event log reporting error: An error occurred with the end-point Oracle Retail Xenvironment uses to report event log errors to Xcenter/Oracle Retail Xstore Office. (Evtlog Error)

Note:

Oracle Retail Xenvironment uses this end-point to communicate any problems directly to Xcenter.
Xstore register offline: A register (Xcenter client) has not sent a status update in "X" minutes. Information returned includes Store # and Reg #.

About Xcenter Register Offline Alert Data

Xcenter register offline alert data is sourced from the ctl_event_log table as noted above, and also has a technical relationship to the ctl_device_registration table.

There is a process that runs in Oracle Retail Xstore Office which periodically observes the ctl_device_registration table. It notices when registers stop checking-in within certain configurable time limits. When the process notices a register has failed to check in, it adds a record to Xcenter's ctl_event_log (which then gets reported as an alert just like all the other alerts).

The process that observes ctl_device_registration can be configured as follows:

Interval for Checking for Missing Registers - controls how frequently the process inspects ctl_device_registration for missing registers. Default is 15 (minutes).
Time Before Register Is Considered Missing- how much time must elapse since a device last checked in before it is considered missing. Default is 61 (minutes).
Time Before Missing Register Is Ignored - once a device has been missing for the amount of time specified here, it is no longer reported as a problem. Default is 72 (hours, aka 3 days).
See also System Management for more information about Oracle Retail Xstore Office Configuration.

Application

Click a logged event in the list to view additional details.

The logged events shown here are sourced from Xcenter's ctl_event_log table.

Figure 10-5 Application Logged Events Detail

Application Logged Events

Pre-flight error: (Data, ciphers, SSL, and so on) A pre-flight error or errors occurred during application startup. All errors are included in this single message. Information returned includes pre-flight error names and descriptions. (Pre-Flight)
SSL expiration check: An SSL certification used for communication with Xcenter or Xpayor other services is nearing, or has reached, its expiration date. Information returned includes a message. (SSL Cert)
Out of memory error: The JVM ran out of memory, terminating the application. Information returned includes stack trace. (Crash)
Helpdesk error: An unexpected error (helpdesk error) occurred. Information returned includes stack trace. (Helpdesk)
Legal Compliance Exceptions: A number of errors related to country specific issues are notified here. For more details about legal compliance exceptions, see the Oracle Retail Xstore Suite Country Accelerator User Guide and the Oracle Retail Xstore Suite Country Accelerator Technical Guide.
Restart: A mid-day restart was performed. (Restart)
Xenvironment Task: Error message from Oracle Retail Xenvironment related to atoms and chains. (Xenv Task)
Xenvironment Database: Error message from Oracle Retail Xenvironment related to database backups/restores. (Xenv DB)
Xenvironment IPC: Error message from Oracle Retail Xenvironment for IPC errors with the IPC server. For example, when the SSL certificate is nearing expiration. (Xenv IPC)

Hardware

Click a logged event in the list to view additional details.

The logged events shown here are sourced from Xcenter's ctl_event_log table

Figure 10-6 Hardware Logged Events Details

Hardware Logged Events

Hardware device initialization errors: A configured hardware device or devices could not be initialized. Information returned includes device names. (Initialization)
Register disk space: The register's disk is nearing capacity and has less than 10% free. Information returned includes % free remaining. (Low Disk)
JPOS hardware device error: A configured hardware device had a failure. (JPOS Error)

Updates

Click a logged event in the list to view additional details.

The logged events shown here are sourced from Xcenter's ctl_event_log table.

Figure 10-7 Updates Logged Events Details

Updates Logged Events

Update service offline: Cannot reach update service. Information returned includes stack trace. (Update Service)
DataLoader error: A failure occurred while loading a download file. Information returned includes the message. (DataLoader)
Config updates error: A failure occurred while applying updates. (Apply Update)
Xenvironment update error: An error occurred related to Oracle Retail Xenvironment updates. (Xenv Update)

Versioning

Click a logged event in the list to view additional details.

The logged events shown here are sourced from Xcenter's ctl_event_log table.

Figure 10-8 Versioning Logged Events Details

Versioning Logged Events

In store version conflict for Xstore: A single retail location has multiple versions of the Oracle Retail Xstore Point-of-Service application running at the same time. Information returned includes versions by register. (Xstore Conflict)
In store version conflict for Xenvironment: A single retail location has multiple versions of Oracle Retail Xenvironment running at the same time. Information returned includes versions by register. (Xenv Conflict)
In store version conflict for Oracle Retail Xstore Office configs: A single retail location has multiple versions of configs running at the same time. Information returned includes versions by register. (Config Conflict)