Version v24.07

Changes in v24.07

Monitoring objects. Monitoring Objects added.

Monitoring object (MO) is an entity for which traffic statistics are separately calculated for detection and visualization purposes.

The belonging of the traffic to the monitoring object is determined, among other things, through the parameters in Flow. Traffic can refer to several MOs simultaneously. For example, different MOs describe the AS, the network in it, the host and the service, then the connection traffic to the service can be taken into account in all four MOs. It is possible to obtain information on traffic at the borders of the MO and save it to the database.

Currently, you can create and configure a Monitoring Object via the GRPC API. In the future, full support will appear in MITIGATOR Web interface.

Exporters. Interaction with the Flow exporter via SNMP v3 is supported.

Exporters. Added separation of exporter IP addresses for Flow and SNMP reception.

Now, when configuring the exporter, you can specify different IP addresses for receiving Flow and SNMP.

Exporters. Added Flow receipt termination tracking from the exporter.

Metrics. Added exporter metrics receiving via SNMP and saving them to the database.

Now Collector receives from the exporter metrics of incoming and outgoing traffic in packets and bits per second via Flow and SNMP.

Metrics. Collector performance metrics request changed.

Now, instead of the exporter’s IP address, its ID is entered.

Report. Added the ability to set a filter by AS names as an incomplete or case insensitive string.

Docker. Added support for docker compose v2.

UX. The method of the time interval specifying for graphs and reports requests changed to relative.