Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Historical monitoring #754

Closed
40 tasks done
gsanchietti opened this issue Sep 12, 2024 · 3 comments
Closed
40 tasks done

Historical monitoring #754

gsanchietti opened this issue Sep 12, 2024 · 3 comments
Assignees
Labels
controller The issue is related to the controller verified All test cases were verified successfully

Comments

@gsanchietti
Copy link
Member

gsanchietti commented Sep 12, 2024

Historical monitoring allows the user to see how the firewall is behaving.
Since the firewall does not have enough storage space to retain such data, the statistics are sent to the controller and visible inside Grafana.

Retention: 1 month (configurable if possible)

Below are listed the possible dashboards.

Network Traffic

All Networks

  • Total Daily Traffic Counter
  • Daily Traffic Chart Histogram
  • Traffic by Protocol Table + Graph
  • Traffic by Application Table + Graph
  • Remote Hosts Traffic Table + Graph
  • Local Hosts Traffic Table + Graph

Single Host

  • IP Address
  • Hostname
  • Total Daily Traffic Counter
  • Daily Traffic Chart Histogram
  • Traffic by Protocol Table + Graph
  • Traffic by Application Table + Graph
  • Remote Hosts Traffic Table + Graph

Connectivity

  • List of Connectivities Interface name and device
  • Connectivity Trend Table or equivalent (Connectivity over time)
  • Current Status & Last 3 Downtime Dates

Per Connectivity

  • Daily Traffic Amount
  • Graphs (aligned and with same dimensions for correlation):
    • WAN Traffic Graph
    • Latency Graph to 2 Public Hosts (e.g., 8.8.8.8, 1.1.1.1)
    • Drop Rate Graph to 2 Public Hosts (e.g., 8.8.8.8, 1.1.1.1)

VPN

For Each RW Server:

  • Hourly User Connections Histogram
  • Total VPN-RW Traffic (Traffic per tunrw section)
  • Top Traffic Users (Traffic per tunrw section)
  • Total Client Traffic per Hour
  • Traffic per Client per Hour

Security

  • Total Number of Blocked Packets for the Day
  • Number of Blocked Packets per Hour
  • Malware by Direction Pie Chart (In/Out)
  • Malware by Category Pie Chart
  • Malware Geomap
  • Number of Blocked Attacker IPs per Day
  • List of Most Blocked Attacker IPs
  • Blocked Attacker IPs per Hour Graph
  • Attack Geomap

Other changes:

  • send data to the controller only if a subscription is enabled
  • add documentation to the administrator manual
  • bump controller UI version
  • bump controller version
  • include latest controller version inside ns8-nethsecurity-controller

See also:

@gsanchietti gsanchietti converted this from a draft issue Sep 12, 2024
@gsanchietti gsanchietti added this to the NethSecurity 8.3 milestone Sep 12, 2024
@gsanchietti gsanchietti moved this from Ready ⏯ to In progress 🛠 in NethSecurity Sep 12, 2024
@gsanchietti gsanchietti added the controller The issue is related to the controller label Sep 17, 2024
gsanchietti added a commit to NethServer/nethsecurity-controller that referenced this issue Sep 23, 2024
gsanchietti added a commit to NethServer/ns8-nethsecurity-controller that referenced this issue Sep 24, 2024
gsanchietti added a commit that referenced this issue Sep 26, 2024
Monitoring APIs for realtime and historical data

#756 
#754
@gsanchietti
Copy link
Member Author

gsanchietti commented Sep 27, 2024

Test case

  • On NS8, install the latest version of the controller, follow the test case 1
  • Configure the controller and make sure to set a valid Max Mind license during the configuration phase
  • Install NethSecurity using the image 8-23.05.5-ns.1.2.99-alpha1-29-gadbb0fcc56 or newer
  • On the NethSecurity, execute this command to circumvent the controller version check:
    version=2.0.0; sed -i '/^Package: ns-api$/,/^Version:/ s/^Version: .*/Version: '"$version"'/' /usr/lib/opkg/status
    
  • Register the machine with a valid subscription, make sure the controller has a valid subscription too
  • Connect the NethSecurity to the controller using the "Controller" page
  • Wait at least 15 minutes for the unit to send data to the controller
  • Access Grafana inside the controller, verify that all dashboards are working correctly

@gsanchietti gsanchietti added the testing Packages are available from testing repositories label Sep 27, 2024
gsanchietti added a commit that referenced this issue Oct 1, 2024
Improve historical data sending

#754
Copy link
Contributor

github-actions bot commented Oct 1, 2024

Testing image version: 8-23.05.5-ns.1.2.99-alpha1-35-g294b21145f

@Tbaile
Copy link
Contributor

Tbaile commented Oct 8, 2024

Everything works fine, if the blessing from dpireport comes around

@Tbaile Tbaile added verified All test cases were verified successfully and removed testing Packages are available from testing repositories labels Oct 8, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
controller The issue is related to the controller verified All test cases were verified successfully
Projects
Archived in project
Development

No branches or pull requests

2 participants