Astra Wireless Documentation
  • Technical documentation
    • Astra Quanta⁣ Technical User Manual
      • Introduction⁣⁣⁣⁣⁣⁣⁣
        • Key Features⁣⁣⁣⁣⁣
        • Hardware Platform⁣⁣⁣⁣⁣
        • Power Supply⁣⁣⁣⁣⁣⁣
        • Lightning⁣ ⁣protection unit⁣⁣⁣⁣⁣
        • Packing list⁣⁣⁣⁣⁣⁣⁣
      • Planning considerations⁣⁣⁣⁣⁣⁣⁣
      • Link pre-configuration in the lab⁣⁣⁣⁣⁣
      • Installation
      • Operation & Administration⁣⁣⁣⁣⁣
        • Web GUI access⁣⁣⁣⁣
        • Dashboard⁣⁣⁣⁣
        • General settings⁣⁣⁣⁣⁣
        • Security settings⁣⁣⁣⁣
        • Radio settings⁣⁣⁣⁣
        • Network settings⁣⁣⁣⁣⁣
        • Switch Settings
        • SNMP settings⁣⁣⁣⁣
        • Spectrum Analyzer⁣⁣⁣⁣⁣
        • Antenna Alignment Tool⁣⁣⁣⁣⁣
        • Maintenance⁣⁣⁣
        • Instant DFS⁣⁣⁣⁣
        • Graphs⁣⁣⁣⁣
      • Troubleshooting⁣⁣⁣⁣⁣⁣⁣⁣⁣
    • Astra Evolution Technical User Manual
      • Introduction⁣⁣⁣⁣⁣⁣
        • Key Features⁣⁣⁣⁣⁣⁣⁣
        • Hardware Platform⁣⁣⁣⁣⁣⁣⁣⁣
        • Power supply⁣⁣⁣⁣⁣⁣⁣
        • Lightning protection unit⁣⁣⁣⁣⁣⁣⁣⁣⁣⁣⁣
        • Synchronization unit⁣⁣⁣⁣⁣⁣⁣
        • ⁣⁣⁣Packing List
      • Planning considerations⁣⁣⁣⁣⁣⁣⁣⁣⁣
      • Link Pre-configuration in the lab⁣⁣⁣⁣⁣⁣⁣⁣⁣
      • Installation⁣⁣⁣⁣⁣
      • Operation & Administration⁣⁣⁣⁣⁣⁣⁣
        • Web GUI access⁣⁣⁣⁣⁣⁣
        • Device Status⁣⁣
        • Basic Settings⁣⁣⁣⁣⁣
          • System Settings⁣⁣⁣⁣⁣⁣
          • Network Settings⁣⁣⁣⁣⁣⁣⁣
          • Link Settings⁣⁣⁣⁣⁣⁣
          • Static Links⁣⁣⁣⁣⁣
          • MAC Switch⁣ ⁣
          • IP Firewall
          • SNMP
          • QoS Options⁣⁣⁣⁣⁣⁣
          • Traffic Shaping⁣⁣⁣⁣⁣⁣⁣
          • Extra Commands⁣⁣⁣⁣⁣⁣
        • Maintenance
        • Spectrum Analyzer
        • DFS
        • Command Line
      • Troubleshooting⁣⁣⁣⁣⁣⁣
        • No access to the local unit⁣⁣⁣⁣⁣
        • The wireless link cannot be established⁣⁣⁣⁣⁣
        • The wireless link is established, but there is no access to the remote device⁣⁣⁣
        • The wireless link throughput is lower than expected⁣⁣⁣
        • Common errors in configuration⁣⁣⁣⁣
        • Emergence Repair Console⁣⁣
        • Unicast-flood detection⁣⁣⁣⁣
    • AstraFleX⁣ Technical User Manual
      • Getting started with AstraFleX User Manual
      • ⁣⁣IP-address format
      • General Purpose Command Set
      • Layer 2 commands set -PHY and MAC
        • ⁣prf ⁣command
        • ⁣⁣lag command (Link Aggregation )
        • ⁣⁣svi command
        • ⁣⁣ltest (radio link test)
        • macf command (addresses mapping)
        • ⁣⁣arp command (ARP protocol)
        • ⁣⁣switch command
        • ⁣⁣dfs (Dynamic Frequency Selection)
        • ⁣⁣lldp command
        • ⁣⁣mint command
        • ⁣⁣rfconfig command
      • ⁣⁣Layer 3 Command set – IP Networking
        • ⁣⁣Ifconfig command (interfaces configuration)
        • tun command (tunnels building)
        • qm command (QoS configuration)
        • ⁣⁣route command (static routes configuration)
        • ⁣⁣arip command
        • ⁣⁣OSPF command
        • ARDA (Aqua Router DAemon)
        • ⁣⁣netstat command (Network statistics)
        • ⁣⁣ipfw command (IP Firewall)
          • ⁣⁣PCAP-filters
        • ⁣⁣loadm command (load meter)
        • ⁣⁣rpcapd command (Remote Packet Capture)
        • ⁣⁣snmpd command (SNMP daemon)
        • ⁣⁣td command (Telnet daemon)
        • ⁣⁣nat command (Network Address Translation)
        • ⁣⁣trapd command (SNMP Traps support)
        • dhcpd command (DHCP Server)
        • ⁣⁣dhcpr command (DHCP relay)
        • dhcpc command (DHCP Client)
        • ⁣⁣vrrp command (VRRP server)
      • ⁣⁣Other commands
    • ⁣NEXT Monitoring System Technical User Manual
      • Description⁣ and operational principles
      • Installation
      • Configuration⁣⁣ ⁣and⁣ management⁣
        • Wireless⁣ ⁣⁣devices preparation
        • Accounts⁣ and user groups
        • Devices⁣ ⁣and links
        • Incident⁣ ⁣⁣management
        • System⁣⁣ ⁣configuration
      • Monitoring⁣ ⁣and management
        • R⁣ep⁣o⁣⁣rts
        • Devices
        • ⁣⁣Incidents
        • MAP
      • Technical support
  • White⁣ papers
    • MINT ⁣⁣⁣technology
    • Dynamic ⁣⁣Frequency ⁣⁣Selection
    • ⁣⁣RADIUS authentication for admin users
    • Security in Astra Wireless Devices
    • ⁣⁣Performance of the Astra Wireless devices
      • Astra Quanta
        • ⁣⁣Thr⁣⁣⁣oughpu⁣t⁣⁣⁣⁣⁣⁣
        • ⁣Packet ⁣⁣performanc⁣e⁣⁣⁣⁣⁣
      • Astra Evolution
        • H22 platform
          • Packet ⁣⁣⁣perfor⁣mance⁣⁣
          • Throug⁣hput⁣⁣⁣⁣⁣⁣
        • H16 platform
          • Packet⁣⁣ ⁣perfor⁣mance⁣⁣
          • ⁣⁣⁣⁣⁣⁣Throug⁣hput⁣⁣⁣⁣⁣⁣⁣
    • ⁣⁣⁣Link ⁣⁣⁣aggregation, balancing and redundancy
      • Astra Evolution
        • Redundancy ⁣⁣⁣with Failover option
        • Redundancy w/o aggregation and AstraMUX
        • Redundancy⁣⁣⁣ ⁣with aggregation and w/o AstraMUX
        • Redundancy ⁣⁣with AstraMUX
        • Full⁣ Duplex
      • Astra Quanta
        • Aggregation ⁣with redundancy ⁣based on⁣ LACP
        • Redundancy⁣⁣⁣ ⁣based ⁣on STP
        • ⁣Redundancy⁣⁣ based on⁣ OSPF
        • ⁣Redundancy with Evolution
    • Beamforming⁣ ⁣technology
    • ⁣⁣⁣Remote ⁣⁣⁣L2 management of Evolution via CLI
    • ⁣⁣⁣Remote ⁣⁣⁣L2 management of Evolution via Web GUI
    • Connectivity with mobile objects⁣⁣⁣⁣
      • Mining industry⁣⁣⁣
      • Railway transport⁣⁣⁣
      • Transport over the water⁣⁣⁣
      • Configuration example⁣⁣⁣
Powered by GitBook

Astra Wireless Technology © 2024. All rights reserved. For more information about available models, sales and technical support, please proceed to https://astrawireless.net/

On this page
  • Incidents review
  • Incident processing
  • Incidents notifications
  1. Technical documentation
  2. ⁣NEXT Monitoring System Technical User Manual
  3. Monitoring⁣ ⁣and management

⁣⁣Incidents

PreviousDevicesNextMAP

Last updated 1 year ago

An NEXT user can obtain a list of all the incidents for the wireless devices and the links in his visibility area by going at the "Incidents" section.

The section includes two key areas:

  • Incidents list - all incidents for the devices and the links in the user's visibility area are displayed here.

  • Incident profile side view - if this area is open, an incident profile with detailed information will be displayed without hiding the list of incidents. If the area is hidden, then the selected incident profile will be opened, but the list of incidents will be hidden.

For easy operation with the incidents list a filter is available at the top of the page. Besides the standard filter by incident occurrence period, additional filters allows to sort incidents by the following parameters:

  • assignee;

  • status;

  • severity;

  • rule;

  • object.

Incidents review

The incidents list is presented in a table having the following columns:

  • Created - the date and time when incident was created.

  • Incident - it displays the title and severity of the rule according to which the incident was created.

  • Object - the device for which the incident was created.

  • Status - current incident's status. The possible statuses are described in the Incident⁣ ⁣⁣management article.

  • Assignee - user who was assigned for resolving this incident.

  • Updated - the date and time when the rule conditions were met last time.

By default, all incidents are sorted by date, therefore the new incidents will be displayed first.

NOTE

In order to display an incident time correctly, it is necessary to set date and time on the virtual machine where NEXT is installed. Time settings can not be made in the monitoring system.

Incident profile

A profile contains the following detailed information:

  • Description - the device or link for which the incident was generated will be displayed here. Also there is a description from the appropriate rule.

  • Status - current incident status.

  • Assignee - user responsible for handling the incident.

  • Source - rule title.

  • Scheme:

    • Device incident - additional information about the device, including its status, model and IP address.

    • Link incident - additional information about the devices connected to the link for which the incident is generated.

    • There is possibility to switch to the web interface of each device or to manage it via the command line.

  • Comments - comments added by engineers to this incident.

Incident processing

Incident processing - one of the incident's lifecycle stages (see Incident⁣ ⁣⁣management). An incident is processed when a responsible person is assigned to it:

  • Superadmin and Admin users can assign incidents to other users in the visibility area corresponding to the device for which the incident was generated. The Superadmin user can not become an assignee.

  • A user can assign an incident to himself, thereby making himself responsible for eliminating the cause.

To accept an incident, the user must click on the "Take on" button in the incident profile. This will lead to the following changes:

  • The incident's status will change to "In service".

  • The incident will be assigned to the user, which will be reflected in the "Assignee" field.

Incident will be resolved automatically after eliminating the cause. In this case the rule conditions won't be met and incident will be closed with status "Resolved".

Engineers can leave comments in the incident profile that will be visible to other engineers, whose visibility area includes the particular device.

Incidents notifications

The monitoring system users can receive notifications about incidents. To activate notifications, configure the connection to the email server (see System configuration).

NEXT sends notifications containing incidents related to the devices and wireless links in the user's visibility area. Notifications are sent every 30 seconds and include all changes, accumulated during this time period.

Notification settings are available in "Notifications" section of user profile.

Here the user can select the incident severity levels for the notifications he wants to receive.

The "Group" option activates joining of several incidents with the same severity level into one notification. In this case each notification will include incidents with the same severity only.