Marathon Update Release Mar 9, 2023¶
Highlights¶
Revised Event Severities¶
- Event severities have been modified so that only the most important events are directly visible across the application. This will reduce user alarm fatigue by no longer drawing attention to events which are only of interest in aggregate, such as data anomaly events.
- Marathon events will support the following configurable event severities going forward:
- High, shown as orange in the application
- Low, shown as yellow in the application
- None, shown as blue in the application
- Only those events with severity High and Low will be displayed in event count badges, on asset cards and on asset time-series views.
- By default, only events with severity High and Low severities will be displayed in the Events page table. A new filter for severity on the Event page allows users to see the list of events with severity None, if desired.
- The filters on the Events page have been further modified for performance, functionality, and description to improve the experience of users when searching for events they are interested in. This includes the addition of a filter to show events which have been marked as “Thumb Up”.
Investigations Generated from Long-Running Events¶
- Marathon now supports the creation of an Investigation with corresponding resolve workflow for ongoing events which have exceeded some predefined time threshold since their creation. This will allow prescriptive actions to be taken by users in the case that an ongoing event indicates a serious systematic problem with an asset is occurring.
Fixes¶
- Investigation and Event load time performance has been improved.
- Selecting a Favorite which contains a previously visible, but now hidden asset will no longer cause the application to crash.
Known Issues¶
- On application load or browser refresh Events can sometimes take at least one minute to become visible in the application.
- None severity Events are still appearing as colored blue on asset cards.
- In the merged view for time-series with multiple graphs, event overlay colors will show as less transparent than those with a single time-series.
- Generating a comparison from asset search or drag and drop will produce a data loading error if that action causes the application to attempt to render approximately 130 or more time-series charts simultaneously.
- List of prior maintenance records displayed below a failure record may not always correspond directly to the asset of the failure record. A workaround is to be on the specific asset you are exploring the failure event for.
Upgrade Instructions¶
- Marathon updates automatically, so no manual steps are required.
Last update: April 11, 2024