KATA integration dashboard

You can use the following methods to monitor the KATA integration status:

• View summary information about the state of the connection to the KATA server on all cluster nodes by checking the KATA Protection information pane in the Nodes section.

  The following statuses are available:

  • Connected means that all cluster nodes are successfully connected and authorized on the KATA server.
  • Errors means that at least one of the following errors occurred on at least one cluster node within the past hour:
    • Connection not authorized.
    • Connection problems.
    • Too many authorization requests.
  • Disabled means that KATA integration is disabled in application settings.
• View detailed information about the state of the connection to the KATA server on each cluster node.

  To do so, on the KATA Protection dashboard, click View details to go to the Settings → External services → KATA Protection → Status section.

  The workspace displays the cluster nodes table containing information about the connection to the KATA server:

  • IP address:port is the IP address and port of the cluster node.
  • Role is the role of the node in the cluster.
  • SHA-256 fingerprint is the server certificate fingerprint.
  • Status is the state of the connection to the KATA server:
    • Connected means that the cluster node is successfully connected and authorized on the KATA server.
    • Connection not authorized means that a connection to the KATA server has been established but the KATA administrator has not yet confirmed the integration request.
    • Connection problems indicates an error connecting to the KATA server.
    • Disabled means that KATA integration is disabled in application settings.
    • Too many authorization requests means that the maximum number of integration requests configured on the KATA server has been exceeded.

      The default value is 50.

  If a connection exists to at least one KATA server, the table displays the successful connection status. If no connection exists with any of the KATA servers, the table displays an error.

• View information about the KATA server connection in the information window of each cluster node.
• Use a script to monitor the connection status of individual KATA servers (when integrating with multiple servers of KATA version 5.0 or later).

  To view connection status for individual KATA servers:

  1. Create the /opt/kaspersky/ksmg/bin/hastat file and add the following lines to it:

     #!/bin/env python3

     import socket

     columns = [ 'pxname', 'svname', 'status' ]

     out_form = '{:<20} | {:<20} | {}'

     out_line = '-' * 68

      

     s = socket.socket(socket.AF_UNIX, socket.SOCK_STREAM)

     s.connect('/var/lib/haproxy/stats')

     s.sendall('show stat\n'.encode())

     response = s.recv(65000)

     s.close()

     rows = response.decode().split('\n')

     headers = rows.pop(0)[2:].strip().split(',')

     indexes = [ headers.index(c) for c in columns ]

     print(out_line)

     print(out_form.format(*columns))

     print(out_line)

      

     for row in rows:

        vals = row.split(',')

        if len(vals) >= len(headers):

            data = [ vals[p] for p in indexes ]

            print(out_form.format(*data))

      

     print(out_line)

  2. Save the file.
  3. Start an operating system command shell on the cluster node to run commands with superuser (system administrator) permissions.
  4. Run the following command:

     python3 /opt/kaspersky/ksmg/bin/hastat

     The connection and connection status table is displayed.

  For example results of running the command, see the figure below:

  

  The last column of the table displays the connection status for individual KATA servers (for example, kata_node1, kata_node2 lines) and the overall connection status (the BACKEND line).

  Possible connection status values:

  • UP means a connection is established.
  • DOWN means a connection is not established.

  If a connection exists with at least one KATA server, the overall connection status is UP.

  The script requests the connection status from the local balancer and outputs it to the console.