NetFlow v9 parsing errors and SQL column failures

Open
#244 0 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
Bug
Clarity
Mostly clear
Activity status
Stale
Tech stack
php, sql
Domain
backend, database

Research direction

Start by reproducing the reported failure with a NetFlow v9 exporter and check the Cacti log for plugin_flowview_raw column errors; compare the v9 behavior with the working v5 source. Then trace how the Flowview listener handles v9 templates and maps fields to database columns. Done means v9 flows are parsed and displayed without SQL column errors.

Written by the indexing model from the issue text.

Description

bug

Description

Flowview fails to parse NetFlow v9 data correctly, resulting in SQL errors about missing or mismatched columns. The v9 template handling does not properly map all field types, causing INSERT failures when flow records reference fields not present in the database schema.

Symptoms

  • SQL errors: column does not exist for v9 flow template fields
  • Flowview reports "no data" for v9 sources while v5 sources work correctly
  • Errors in Cacti log referencing plugin_flowview_raw table column mismatches

Steps to Reproduce

  1. Configure a NetFlow v9 exporter (router/switch)
  2. Point it at the Cacti Flowview listener
  3. Navigate to Flowview and attempt to view flows
  4. Check Cacti log for SQL errors

Expected: v9 flows are parsed and displayed correctly
Actual: SQL column errors, no flow data displayed

Environment

  • Cacti versions: reported across 1.2.x releases
  • Flowview plugin: multiple versions affected
  • NetFlow v9 sources from various vendors (Cisco, etc.)

Forum Reference

Originally reported at https://forums.cacti.net/viewtopic.php?t=60359

Multiple users confirmed v9 parsing failures while v5 works correctly.

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.