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

Aberta
  • Algo errado?
#153 2 comentários 0 reações 0 responsáveis Ver no GitHub

Mantenedores costumam responder em até 1 dia

Ninguém assumiu esta issue ainda.

Avaliação

Dificuldade
5/5
Tempo estimado
Mais de uma semana
Facilidade para iniciantes
25/100
Tipo de issue
Funcionalidade
Clareza
Precisa de esclarecimento
Status de atividade
Estagnada
Stack de tecnologia
php
Domínio
databases

Direção de pesquisa

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.

Escrita pelo modelo de indexação a partir do texto da issue.

Descrição

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.

Linguagem predominante
PHP
Estrelas
21
Forks
13
Merge médio
1d 15h
PRs com merge (30d)
13

Preparar o ambiente

  • Sem Dockerfile nem arquivo Docker Compose
  • Tem um modelo de pull request
  • Sem guia de contribuição

Primeiros passos

  1. Leia a issue inteira e depois o guia de contribuição do projeto.
  2. Comente na issue dizendo que vai assumir — evita que duas pessoas façam o mesmo trabalho.
  3. Faça um fork do repositório e trabalhe em uma branch.
  4. Abra um pull request que referencie o número da issue.

Mais de Cacti/plugin_flowview

Todas as issues de Cacti/plugin_flowview

Issues semelhantes

Mais issues de PHP

Receba novas issues na sua caixa de entrada

Um resumo curto de issues do GitHub para quem está começando.