Identify classes of key data that we can use to aggregate raw flow data in order to increase performance

Ouverte
  • Quelque chose ne va pas ?
#153 2 commentaires 0 réactions 0 personnes assignées Voir sur GitHub

Les mainteneurs répondent en général sous 1 jour

Personne n'a encore pris cette issue.

Évaluation

Difficulté
5/5
Temps estimé
Plus d'une semaine
Accessibilité débutants
25/100
Type d'issue
Fonctionnalité
Clarté
À clarifier
Activité
À l'abandon
Stack technique
php
Domaine
databases

Piste de recherche

This issue is a discussion about what FlowView data users want aggregated, not a request naming code files or tests. Start by reviewing the raw flow tables and the existing reporting needs described in the issue; done means identifying which data beyond packet, byte, and flow totals should be aggregated by hour or day.

Rédigé par le modèle d'indexation à partir du texte de l'issue.

Description

enhancement help wanted

Is your feature request related to a problem? Please describe.

It's clear, even from my little home install that data will pile up in the raw tables over time and that for most queries, the tool will become unusable if for example, you want to see the top traffic by source domain over a month, the queries may never complete, even if done in parallel. So, it's important to aggregate key data by day or by day and hour such that the user interface is usable.

In order to do that, we first must hear from users as to what is important to capture for aggregation and high level reporting.

We will use this ticket to start the discussion on that topic.

Describe the solution you'd like

We would like users of FlowView to describe what data is key outside of the totals of packet, bytes, and flows so that we can consolidate that data by hour or day into more analytically focused partitions.

Describe alternatives you've considered

Just parallelizing queries is not enough if this tool is to be more than a nice utility to use for your home network. So, we have to give this topic some thought. We will parallelize, it's just not enough.

Langage dominant
PHP
Étoiles
21
Forks
13
Merge moyen
1 j 15 h
PR mergées (30 j)
13

Préparer son environnement

  • Aucun Dockerfile ni fichier Docker Compose
  • Propose un modèle de pull request
  • Aucun guide de contribution

Par où commencer

  1. Lisez l'issue en entier, puis le guide de contribution du projet.
  2. Signalez en commentaire que vous la prenez — cela évite que deux personnes fassent le même travail.
  3. Forkez le dépôt et travaillez sur une branche.
  4. Ouvrez une pull request qui référence le numéro de l'issue.

Autres issues de Cacti/plugin_flowview

Toutes les issues de Cacti/plugin_flowview

Issues similaires

Plus d'issues PHP

Recevez les nouvelles issues par e-mail

Un résumé court des issues GitHub adaptées aux débutants.