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

health: resolve interface names for traffic and packets #428

Closed
fichtner opened this issue Oct 11, 2015 · 2 comments
Closed

health: resolve interface names for traffic and packets #428

fichtner opened this issue Oct 11, 2015 · 2 comments

Comments

@fichtner
Copy link
Member

Is this easily possible in the drop down menu?

via: https://forum.opnsense.org/index.php?topic=1452.0

@fichtner fichtner added the feature Adding new functionality label Oct 11, 2015
@fichtner fichtner added this to the 16.1 milestone Oct 11, 2015
@AdSchellevis
Copy link
Member

From an architecture point of view, this should be handled by the process collecting the data. The module using the data (health) has no knowledge of the items it's processing other then what's statically defined in the view definitions.
Unfortunately the collector part is still legacy code, so without glueing everything together from all different angles, there is no easy fix for this one at the moment.
I will assign this to myself, this needs some more thinking I guess.

@fichtner
Copy link
Member Author

If not it can be ditched. Consider this nice to have only. Thanks for your thoughts. :)

@fichtner fichtner removed this from the 16.1 milestone Feb 4, 2016
@fichtner fichtner removed the feature Adding new functionality label Feb 4, 2016
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Development

No branches or pull requests

3 participants