Add support of ExtendedMPLS for sflow

Open
#327 1 comment 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
go
Domain
networking

Research direction

Read the sFlow v5 structure reference linked in the issue and trace how goflow2 currently parses sFlow records. Identify the existing MPLS parsing entry points and tests, then compare their coverage with ExtendedMPLS. Done means ExtendedMPLS data, including MPLS labels, is available after parsing; the issue names no source files or tests.

Written by the indexing model from the issue text.

Description

enhancement

Is your feature request related to a problem? Please describe.
the sflow v5 has implemented extended mpls struct, which contains mpls data. This is not implemented in goflow2 sflow. As such, i cannot properly decode mpls labels

Describe the solution you'd like
To add support of mpls extended mpls to sflow part of goflow2 to make this information available upon parsing.

Describe alternatives you've considered
There is not much alternative here. I am. Using telegraf, which relies in this library for sflow parsing.

Additional context
https://sflow.org/SFLOW-STRUCTS5.txt

Dominant language
Go
Stars
817
Forks
182
Avg merge
4h 18m
Merged PRs (30d)
6

Getting set up

  • Ships a Dockerfile or Docker Compose file
  • No 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 netsampler/goflow2

All issues in netsampler/goflow2

Similar issues

More Go issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.