Advanced Analytics: Service Disruption

Notices older than 24 hours are automatically closed. If you are experiencing issues, please contact support.

We've finished re-parsing the data. Now that this has completed, if you would like to reprocess the data in Advanced Analytics, kindly file a Sev 1 ticket to notify our Customer Support Team so that they can issue a martini restart (which must be from a point prior to Oct 30, 07:00 UTC). Alternatively you can follow this https://community.exabeam.com/s/article/Restarting-Martini-from-UI to issue a martini restart via UI. Kindly note that a martini restart will cause temporary processing delay until the system catches up to real time processing, which can take up to one day.

A service disruption on between October 30 20:00 UTC and October 31 12:00 UTC may have affected your environment, temporarily preventing Advanced Analytics from properly processing all event types. It has been processing all events as expected since the end of this timeframe. No other services were impacted during this disruption. To fix this, Exabeam is re-parsing data from the event store so that all events will be ready to process within Advanced Analytics as expected. This will require an optional restart, please see below for details on the restart procedure. We anticipate the re-parsing process will take approximately 24 hours. An update will be provided on this page as soon as it is completed. If you would like to reprocess the data in Advanced Analytics after that time, please use one of the following options: a) Self-service: Restart the Exabeam Analytics Engine from the UI by choosing a point prior to Oct 31. Via the UI, follow this path: Admin Operations-> Exabeam Engine -> Exabeam Analytics Engine -> Restart Processing. b) Exabeam Customer Support assisted: File a Sev 1 support case to notify the Customer Support Team to issue a restart of the Exabeam Analytics Engine which must be from a point prior to Oct 31. Please note that the analytics engine restart will cause temporary processing delays until the system catches up to real time processing. Re-processing generally performs at a 3:1 ratio of logs to clock time, however it can perform slower or much faster depending on your system.