Updated package neteye-api 1.3.3-1 (NetEye 3.7)
Changelog: – Fixed bug: Installing erizone plugins gives an error: missing perl package (NEAPI-55) – bugfixes and improvements
Read MoreChangelog: – Fixed bug: Installing erizone plugins gives an error: missing perl package (NEAPI-55) – bugfixes and improvements
Read MoreChangelog: – Fixed bug: Installing erizone plugins gives an error: missing perl package (NEAPI-55) – bugfixes and improvements
Read MoreChangelog: – Fixed bug: Monarch commit fails if host-admins contact group is deleted (NSM-2)
Read MoreChangelog: – Fixed bug: Monarch commit fails if host-admins contact group is deleted (NSM-2)
Read MoreChangelog: – Fixed bug: Monarch commit fails if host-admins contact group is deleted (NSM-2)
Read MoreChangelog: – Removed group “dashboard” from default installation DB (NC-16)
Read MoreChangelog: – Removed group “dashboard” from default installation DB (NC-16)
Read MoreChangelog: – Removed group “dashboard” from default installation DB (NC-16)
Read MoreChangelog: – Fixed bug: neteye init script gives error during start about old traphandler (NB-7) – Fixed Clustering: the EXTRA_SERVICES_STATUS status is not check correctly (NB-10)
Read MoreChangelog (since 3.2.8-1): – Added mutt dependency (NSV-8) – fixed bug where log entries were doubled in Elastic (NSV-17) – integrated into NetEye API
Read MoreChangelog (since 3.2.8-1): – Added mutt dependency (NSV-8) – fixed bug where log entries were doubled in Elastic (NSV-17) – integrated into NetEye API
Read MoreChangelog (since 3.2.8-1): – Added mutt dependency (NSV-8) – fixed bug where log entries were doubled in Elastic (NSV-17) – integrated into NetEye API
Read MoreBis vor kurzer Zeit war die Überwachung des Netzwerk Traffics einzig und allein darauf ausgerichtet die Typologie des Traffics und die Anzahl der übertragenen Pakete/Bytes zu ermitteln. Diese Informationen sind wichtig für: die Analyse von Anomalien die Optimierung des Netzwerkverkehrs (Ausgeglichenheit des Traffics) die Dimensionierung der Infrastruktur
Read MoreFino a poco tempo fa, il monitoring del traffico di rete era unicamente finalizzato ad evidenziare la tipologia di traffico e la quantità di pacchetti/byte trasmessi nel tempo. Queste informazioni risultano fondamentali per l’analisi di anomalie, per l’ottimizzazione dei flussi (bilanciamento del traffico) e per il dimensionamento dell’infrastruttura.
Read MoreMonitoring network traffic was initially used only for highlighting the typology of network traffic and the quantity of packages/bites broadcasted. This information are important to analyze anomalies, to optimize flows (balance network traffic) and to size the infrastructure.
Read More