Add support for external (REST) host alerts (#7170)

This commit is contained in:
Alfredo Cardigliano 2023-01-26 15:34:54 +01:00
parent 7ce510a914
commit 73af3fa521
17 changed files with 523 additions and 1 deletions

View file

@ -0,0 +1,79 @@
--
-- (C) 2019-23 - ntop.org
--
-- ##############################################
local host_alert_keys = require "host_alert_keys"
local json = require("dkjson")
local alert_creators = require "alert_creators"
-- Import the classes library.
local classes = require "classes"
-- Make sure to import the Superclass!
local alert = require "alert"
-- ##############################################
local host_alert_external_script = classes.class(alert)
-- ##############################################
host_alert_external_script.meta = {
alert_key = host_alert_keys.host_alert_external_script,
i18n_title = "alerts_dashboard.external_script",
icon = "fas fa-fw fa-life-ring",
has_attacker = true,
}
-- ##############################################
-- @brief Prepare an alert table used to generate the alert
-- @param one_param The first alert param
-- @param another_param The second alert param
-- @return A table with the alert built
function host_alert_external_script:init(metric, value, operator, threshold)
-- Call the parent constructor
self.super:init()
self.alert_type_params = alert_creators.createThresholdCross(metric, value, operator, threshold)
end
-- #######################################################
-- @brief Format an alert into a human-readable string
-- @param ifid The integer interface id of the generated alert
-- @param alert The alert description table, including alert data such as the generating entity, timestamp, granularity, type
-- @param alert_type_params Table `alert_type_params` as built in the `:init` method
-- @return A human-readable string
function host_alert_external_script.format(ifid, alert, alert_type_params)
local alert_consts = require "alert_consts"
return i18n("alert_messages.external_script", { message = alert_type_params["message"] } )
end
-- #######################################################
-- @brief Prepare a table containing a set of filters useful to query historical flows that contributed to the generation of this alert
-- @param ifid The integer interface id of the generated alert
-- @param alert The alert description table, including alert data such as the generating entity, timestamp, granularity, type
-- @param alert_type_params Table `alert_type_params` as built in the `:init` method
-- @return A human-readable string
function host_alert_external_script.filter_to_past_flows(ifid, alert, alert_type_params)
local res = {}
local host_key = hostinfo2hostkey({ip = alert["ip"], vlan = alert["vlan_id"]})
-- Filter by client or server, depending on whether this alert is as-client or as-server
if alert["is_client"] == true or alert["is_client"] == "1" then
res["cli_ip"] = host_key
elseif alert["is_server"] == true or alert["is_server"] == "1" then
res["srv_ip"] = host_key
end
return res
end
-- #######################################################
return host_alert_external_script