We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
Currently various traffic patterns are defined as a golang object that the UI and core simulator both know about. And the same for the metrics returned to the UI. This should be defined as a protobuf similar to #58 so that the UI can be more decoupled from the core. This will allow command line / library usage of Skenario core in addition to the UI.
The proto should include an enumerated set of patterns. But also allow for raw data input (e.g. qps over time).
The text was updated successfully, but these errors were encountered:
Is the idea that traffic patterns will live in a separate process communicating with the simulator core?
Sorry, something went wrong.
No, I just want to have clearly defined traffic shape which the simulator will implement. So the UI can be decoupled from the simulator.
josephburnett
No branches or pull requests
Currently various traffic patterns are defined as a golang object that the UI and core simulator both know about. And the same for the metrics returned to the UI. This should be defined as a protobuf similar to #58 so that the UI can be more decoupled from the core. This will allow command line / library usage of Skenario core in addition to the UI.
The proto should include an enumerated set of patterns. But also allow for raw data input (e.g. qps over time).
The text was updated successfully, but these errors were encountered: