Offer the possibilities to say NOT on a protocol filter criteria

Open
#213 3 comments 0 reactions 0 assignees View on GitHub

Maintainers usually reply within 1 day

Nobody has claimed this yet.

Assessment

Difficulty
4/5
Estimated time
3-5 days
Newbie friendliness
35/100
Issue type
Feature
Clarity
Mostly clear
Activity status
Stale
Tech stack
php
Domain
web-dev

Research direction

No files or tests are named. Start by locating the protocol filter criteria and reading how their selections are applied. Done means each protocol filter can exclude selected hosts or protocols, so users can view remaining flows; the issue does not specify a detailed interaction or test plan.

Written by the indexing model from the issue text.

Description

enhancement

I would love to have a NOT function on the protocol filter part.

When you need to know who is using what globally, it can be helpful to filter the flow except this list of host/protocol.

example:
I have some video server, and I know it's taking my top 50 bandwidth users, but I need to get rid of them, to be able to see the rest.
And that as an option for every protocol filter.
Like a question mark.

Dominant language
PHP
Stars
21
Forks
13
Avg merge
1d 15h
Merged PRs (30d)
13

Getting set up

  • No Dockerfile or Docker Compose file
  • Has a pull request template
  • No contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from Cacti/plugin_flowview

All issues in Cacti/plugin_flowview

Similar issues

More PHP issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.