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

Switchmap-NG new features - Input welcome #129

Open
palisadoes opened this issue Feb 10, 2023 · 4 comments
Open

Switchmap-NG new features - Input welcome #129

palisadoes opened this issue Feb 10, 2023 · 4 comments

Comments

@palisadoes
Copy link
Contributor

I'm working on switchmap-ng v2 with broadly planned features that include:

  1. Storing all data in a MySQL database
  2. Creating an API that allows programmatic queries of the data for use in other dashboards

There would be three daemons:

  1. switchmap_poller: Similar to the existing poller, but it would post data to the API instead of the various YAML files
  2. switchmap_api: The API supporting GraphQL queries
  3. switchmap_dashboard: The existing web UI that would query the API instead of the YAML files

This architecture has these advantages:

  1. The possibility of historically tracking changes in the network. A way to trim the history tables would need to be found. (At the moment I'm only tracking the most recent
  2. Having multiple pollers posting to a central API server over a well known TCP port. This allows pollers to be located in remote sites.

The database poller and GraphQL code is almost complete. I need to figure out how to integrate the dashboard.

Please let me know your thoughts on features that could be added.

@chrisgerman
Copy link

Been monitoring and keeping an eye on this project. You're doing amazing work! It may have been asked, but I will ask as you're adding a DB. Will there be a way to add a login screen to keep this information behind a secure portal? Again, thank you for all your hard work.

@palisadoes
Copy link
Contributor Author

Thanks,

  1. I just pushed the v2 code to the v2 branch. Please test and report any issues with either the documentation or code.
  2. Over the next few weeks I'll be focusing on adding documentation on how to use the GraphQL API for accessing the historical data programmatically.
  3. Login credentials would be a good next step, Any assistance any lurkers want to provide is welcome. We need to diversify the contributor base. I'll add it to the ideas list.

@chrisgerman
Copy link

Sorry for being late on testing, but I have some time to test this out. With v2, what are the steps for installing it correctly and getting it up and running?

@palisadoes
Copy link
Contributor Author

Please check the V2 branch. The instructions are there.

I will make the V2 code the default branch next week.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants