Docs

# Update 2.5 (30.10.2023)

⬇️ Let's take a closer look at the main changes to Acure 2.5:

# Role-Based Signal Model

# Role Settings

In the Workgroup role model settings for the IOps module, a new custom permission setting Signals was added.

When configuring a custom role for Signals, the following types of permissions can be selected:

  • Prohibit: Signals in this Workgroup are not displayed for the user on the Service Model Graph page. Any attempt to modify or request a signal through the API will result in an error.

  • View: Operations related to modification, updating, or deletion of signals are blocked, but viewing signals is allowed.

  • Edit: Full access for any operations with signals.

For standard user roles, the permissions will be as follows:

  • Manager - Edit
  • User - View

For already created roles (non-standard) in the Workgroup, the permission for the "Signals" section will be set to "View."

# Shared Objects

It is now possible to grant access to signals to other Workgroups with not only editing rights but also reading rights.

# CMDB View

  • In the "CMDB" section, customization for tabs within the Configuration Item (CI) card is now available, similar to the tab settings on the "Operations Center" screen.
  • Users can now configure the depth of display for influence links on the Health Graph in the CI card.
  • The display depth can be specified in both directions:
    • For influencing CIs - arrows are directed towards the studied CI.
    • For dependent CIs - arrows are directed away from the studied CI.
  • In the Attributes tab, it is now possible to view CI Attributes in two formats:
    • Structure - the existing representation.
    • JSON - all attributes are compiled into a single JSON code in key-value format, with the ability to copy this code.

# Operations Center

On the "Operations Center" screen, you can now access a context menu for a selected CI in the list, which provides the following actions:

  • Open the CI Parameters tab
  • Open the CI Health tab
  • Open the selected CI in the "Operations Center" screen
  • Open the CI card
  • Archive/Unarchive the CI
  • Delete the CI

On the "Parameters" tab for a selected CI, you can now view Labels, CI Type Attributes, and Space Attributes both in field format and JSON format.

# SM Health Tab

# General Changes

  • The "Health" tab now allows you to view a list of dependent CIs: their health, inflicted damage, and the type of influence from the investigated CI.
  • The display of health for all objects has become more precise and is rounded to two decimal places.
  • In the case of critical component calculations: if there are multiple objects causing the same amount of damage simultaneously, the damage inflicted by them is evenly distributed among them. After one of them is restored, the damage inflicted by the remaining ones is recalculated.
  • Damage from third-level objects (CIs / Signals) is now displayed directly on the investigated CI, not on the higher-level component.
  • Influence settings for the component can now be individually adjusted for each CI:
    • Signal settings are available if Signals do not influence the Component.
    • Influence link settings are available if CIs do not influence the Component.
  • In the case of lacking rights to access Signals, users will be provided with limited information about the signal on the CI health scheme.
  • The "breadcrumbs" have become more compact and no longer stretch across the entire screen.

# Combo Health Calculation Settings for CIs

The health calculation model using the Combo method has changed as follows:

  • The component's health calculation depends on the CIs influencing it in combinations
  • The health of a combination is calculated as the average of the CIs in it, with signals not taken into account, and all influence links being balanced
  • Users have two ways to determine the number of CIs for a combination:
    • Fixed - directly specify the number of CIs to form a combination
    • Calculated - determined by the expression All CIs - N
  • Additionally, in the Combo method, there is now a mandatory setting - the critical health transfer threshold for a combination
  • The Combo settings from the old version have been transferred to the new format without any changes in Combo functionality

# SM Metamodel

Due to changes in health calculation using the Combo method, the method settings have also been changed for CI Types. The changes are similar to those on the Health tab.

# Root Cause Analysis

Users can search for signals that have caused degradation in the health of the investigated CI or component at the business level:

  • Root Cause analysis is available for both CIs and components.
  • The Root Cause analysis table contains essential information about signals and shows the root damage that has been inflicted on the investigated object through the entire chain of links.
  • Information about the signal may be limited if the user does not have access to the signal.
  • There is an option to set a cutoff threshold with a value of root impact. Signals causing damage less than the specified threshold will not be considered in the calculation.
  • Root Cause calculation is performed at the current moment and is not updated in real-time, but users can trigger a manual recalculation.

# Import/Export of Custom Libraries

In the "Automation Settings" section, tools for exporting and importing custom libraries have become available.

Unlike other system entities, when importing a library, there is no option to give it a custom name in the new space. They always inherit their name from the source library.

# Automation

# New Automation Functions

Added functions for working with influence links:

  • UpdateInfluenceLinksBatch - batch update of influence link parameters. All influence link parameters are updated.
  • PartialUpdateInfluenceLinksBatch - batch partial update of influence link parameters. Only the values of influence link parameters passed as input are updated.
  • CreateInfluenceLinksBatch - batch creation of influence links with the specified parameters. Unlike link creation functions, there is no need to specify the type of created links.
  • UpdateLinksBatch - batch update of general parameters for links of any type. All general parameters for links of any type are updated.
  • PartialUpdateLinksBatch - batch partial update of parameters for links of any type. All parameters for links of any type are updated.

Functions for working with components have also been added:

  • UpdateConfigItemComponent - update of all parameters for influencing a component's health on CIs. Only the parameters of the component passed as input are updated.
  • PartialUpdateConfigItemComponent - partial update of a component's influence parameters on CIs. Only the parameters of the component passed as input are updated.
  • UpdateConfigItemComponentsBatch - batch update of all component influence parameters on CIs. All parameters of the component that affect CI health are updated.
  • PartialUpdateConfigItemComponentsBatch - partial batch update of component influence parameters on CIs. Only the parameters of the components passed as input are updated.

Additionally, a function for batch deletion of CIs has been added - DeleteConfigItemsBatch.

# Modification of Existing Automation Functions

# CreateLinksBatch

Input Pins: For the structure ConfigItemLinkPost of the input pin LinkPostModels, the following changes have been implemented:

  • Added the property Labels (Dynamic)
  • Extended the existing property Type by adding a new link type, "Info" (Informational Link)

# FilterConfigItemsExtended

Input Pins: A new input pin, Attributes (Dynamic), has been added.

# CreateSignalsBatch

Input Pins: For the structure SignalPost of the input pin SignalPostModels, the property ConfigItemComponentName (string) has been added.

# CreateSignalExpanded

Input Pins: A new input pin, ConfigItemComponentName (string), has been added.

# BindConfigItemsToSignalsBatch

Input Pins: In the SignalBindConfigItemPostModel, the property ConfigItemComponentName (string) has been added.

# UnbindConfigItemsFromSignalsBatch

Input Pins: In the SignalUnbindConfigItemDeleteModel, the property ConfigItemComponentName (string) has been added.

# UpdateSignal

Input Pins: In the input pin SignalPatch, the property ConfigItemComponentName (string) has been added.

# UpdateSignalExpanded

Input Pins: The property ConfigItemComponentName (string) has been added.

# UpdateSignalsBatch

Input Pins: In the input pin SignalPatchModels, the property ConfigItemComponentName (string) has been added.