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

Abierto
  • ¿Algo no está bien?
#153 2 comentarios 0 reacciones 0 asignados Ver en GitHub

Los mantenedores suelen responder en 1 día

Nadie ha tomado este issue todavía.

Evaluación

Dificultad
5/5
Tiempo estimado
Más de una semana
Aptitud para principiantes
25/100
Tipo de issue
Nueva funcionalidad
Claridad
Necesita aclaración
Estado de actividad
Estancado
Stack tecnológico
php
Área
databases

Línea de trabajo

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.

Escrito por el modelo de indexación a partir del texto del issue.

Descripción

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.

Lenguaje dominante
PHP
Estrellas
21
Forks
13
Merge medio
1 d 15 h
PR fusionados (30 d)
13

Preparar el entorno

  • Sin Dockerfile ni archivo de Docker Compose
  • Tiene una plantilla de pull request
  • Sin guía de contribución

Primeros pasos

  1. Lee el issue completo y luego la guía de contribución del proyecto.
  2. Comenta en el issue que vas a ocuparte — evita que dos personas hagan lo mismo.
  3. Haz un fork del repositorio y trabaja en una rama.
  4. Abre un pull request que haga referencia al número del issue.

Más de Cacti/plugin_flowview

Todos los issues de Cacti/plugin_flowview

Issues similares

Más issues de PHP

Recibe los nuevos issues en tu correo

Un resumen breve de issues de GitHub para principiantes.