Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

'Human-readable' BGP communities #173

Closed
ggidofalvy-tc opened this issue Nov 25, 2021 · 1 comment
Closed

'Human-readable' BGP communities #173

ggidofalvy-tc opened this issue Nov 25, 2021 · 1 comment
Labels
accepted Issue is confirmed and will be worked on feature New feature or request fixed-in-next-release Issue has already been fixed in the next release

Comments

@ggidofalvy-tc
Copy link

ggidofalvy-tc commented Nov 25, 2021

Feature Description

I would very much like to see the ability to map BGP communities to human-readable strings, then seeing the BGP communities show up with the human-readable format alongside them. This feature request specifically applies to the structured output, as Hyperglass actually parses up the communities attached to the resulting routes.

Is your feature request related to a problem? Please describe.

As the user of a BGP looking glass, I might use it to check what sort of communities are set on specific routes, for example, when troubleshooting why traffic takes a given path (but not another). At the moment, the BGP communities list in the output can be difficult to parse up/comprehend, especially if the network in question uses a lot of distinct BGP communities for traffic engineering.

Environment & Use Case

I would use this in an environment with network equipment that supports the structured output.

Additional Context

@ggidofalvy-tc ggidofalvy-tc added the feature New feature or request label Nov 25, 2021
@forkwhilefork
Copy link

I second this - I have a script that queries my routers and replaces the communities with human-readable text. I would like to extend this ability to my customers, too.

@thatmattlove thatmattlove added the accepted Issue is confirmed and will be worked on label Dec 14, 2021
@thatmattlove thatmattlove added the fixed-in-next-release Issue has already been fixed in the next release label Dec 14, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
accepted Issue is confirmed and will be worked on feature New feature or request fixed-in-next-release Issue has already been fixed in the next release
Projects
None yet
Development

No branches or pull requests

3 participants