Docs

# Signals

This section of the documentation contains information about Signals and how to work with them.

A signal is a dynamic alarm that has a start time and an end time. It provides information about the exit of any parameter from the regular state and is mainly intended for deduplication of primary events. Since the signal has a beginning and an end of its existence, therefore it is impossible to reopen the signal after it is closed, it is necessary to open a new signal.

The signal has the following properties:

  • ID - system-wide signal identifier
  • Start time - signal creation time
  • End time - signal close time
  • Criticality (priority) - the level of importance of the signal (an immutable property of the signal).
  • Associated CIs - configuration items associated with the signal
  • Associated Primary Events - signal-related events from external sources (signal open, acknowledge, or close events)
  • Labels - special fields that expand the possibilities of signal classification and filtering
  • Custom tags - additional fields for signal categorization
  • Owner - the workgroup that owns the signal

Signal management - the creation of a signal, the connection of a signal with CI, the enrichment with labels and tags and the closing of signals - is carried out in automation scenarios.

Additionally, in the signal management interface, there is the possibility of manually controlling the signal:

  • Closing an open signal
  • Linking configuration items to a signal
  • Add or remove tags

# Signals control screen

To work with the Signals entity Signals tab has been implemented in the interface for working with maps of the Service model. Image

When switching to the Signals tab, the user has access to all signals that meet the filtering conditions and for which the user has rights. By default, signals are filtered within the selected SM map and signals associated with configuration items.

On the Signals tab, the loaded results for signals are presented in the form of a table, where signal properties are displayed as fields. The information in the table is automatically updated using WebSockets technology.

# Signal table

The table shows the following signal properties:

# Signal criticality

Criticality is the main attribute of a signal that determines its importance. This attribute cannot be changed after the signal has been created.

The criticality model is represented by 6 degrees in different color differentiation:

  • 1 Fatal
  • 2 Critical
  • 3 Major
  • 4 Warning
  • 5 Info
  • 6 Unknown (set if the criticality attribute is not included in the interval from 1 to 5 when creating a signal)

# Signal status

  • Status is a required signal attribute
  • The status model consists of values Open and Closed
  • An open signal can be forced closed via the API or manually in the interface
  • A closed signal cannot be reopened

# Signal name

  • Name - required signal property
  • Is not unique
  • Assigned when the signal is created and remains unchanged

# Signal description

  • Name - optional signal property
  • Is not unique
  • Assigned when the signal is created and remains unchanged

# Date of creation

  • Creation date is set automatically when creating a signal

# Closing date

  • The closing date is set automatically when the signal closes

# Duration

  • Duration - the lifetime of the signal from the date of creation to the date of closing, if the signal is already closed or until the current time, if the signal is still open

# Workgroup signal owner

  • The owner of the signal is a required attribute assigned when creating the signal and remains unchanged.
  • Related CIs - optional signal attribute
  • An unlimited number of configuration items can be attached to a signal
  • Configuration items can be bound when the signal is created or throughout the lifetime of the signal
  • Configuration items can only be linked if the CI owner and the signal owner are the same Workgroup
  • Related Events - optional signal attribute
  • The signal table displays information about the number of linked events
  • You can view linked events in the signal card
  • An event can be attached both at the stage of creating a signal, and during the lifetime of this signal
  • Events can only be bound using the signals API
  • The associated event model consists of:
    • Event body
    • Event binding date
    • Event source (route node)
    • Event type (Opening, Confirming, Closing)
  • You can't unbind an event from a signal
  • Labels - optional signal attribute
  • Signal labels are set via Signals API methods
  • Tag management via user interface is not available
  • In the tabular representation of the signals, the labels are only informational in nature.
  • Tags - optional signal attribute
  • Tag - a system-wide object within the entire user space, available for specifying as a signal attribute
  • Tags associated with one signal must be unique

You can bind and untie an existing one, or create a new tag for a signal in the corresponding field of the signal table

# Filtering and searching for signals

On the signal management tab, a form for filtering signals by main attributes is available.

  • Filtering by EC
  • Filtering by signal status
  • Filtering by signal severity
  • Filtering signals by last modified time
  • Filtering by signal duration
  • Filtering by signal owner
  • Filtering by tags
  • Displaying signals not associated with KE
  • Search for signals by name, description and signal ID

# Creation and Closing of Signals

The creation of signals is implemented using automation scripts and special function blocks that work with the Signals public API.

For example, the creation of a signal is carried out using the function CreateSignalExpanded:

Image

Warning!

Manual creation of signals is not provided by the concept of working with Signals.

The required parameters when creating a signal are:

  • Signal name (string)
  • SIgnal owner (string)

Optional parameters of the signal during creation can be:

  • Criticality (integer)
  • Description (string)
  • Tags (object)
  • Related CIs (array CI IDs)
  • Tags (array of tag models)
  • Related events (array of event models)

To close an open signal, you need to use the signal filtering function FilterSignalExpanded to find the required signal and get its identifier. To directly close the signal, the corresponding function used is CloseSignal, to which a parameter is passed - the signal identifier.

A complete description of the existing functions for working with signals is available in the documentation section Automation - Functions

# Manual signal creation

To create a Signal manually, go to the Signals management screen and click the Create - Signal button in the upper right corner.

Fill in the creation form values:

Image

And press the Create Signal button.

After creating the Signal, select the required configuration item in the CI list. If the Signal was created without reference to the CI, set up the filter for displaying Signals without CI accordingly.

# Signal card

To view detailed information about a Signal, go to the Signal card by double-clicking on the corresponding signal in the table.

The modal window will load the information of the selected Signal:

Image

In the signal card, the user can:

  • Bind/unbind configuration items
  • Close signal

And also view information about the following Signal objects:

  • Signal ID
  • Current status
  • Severity level
  • Duration
  • Related configuration items
    • Title
    • Current status
    • Health Information
    • Life cycle stage
    • Owner
  • Related Primary Events
    • Event type ( Opening , Confirmed , Closing )
    • Event time
    • Event content
  • Signal labels - in JSON format
  • Related activities
    • Rule
    • Action
    • Notification method
    • Notification text