-
Notifications
You must be signed in to change notification settings - Fork 0
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
Discovery service implementation #13
Comments
In this branch https://github.com/frees-io/freestyle-opscenter/tree/ep-12-endpoint-microservices you have the endpoint needed. Hitting this endpoint The data is serialized, so you will need fecth the proto files in this endpoint I have to change some implementation details but you can start to work on this with those endpoints. |
To fetch the proto describing metrics structure: To fetch the proto associated with available nodes: |
In this issue, in the JS code and TS definitions generation step, we can go along with two routes, given that there are two JS runtime Protocol Buffers implementations.
Due to our current target of integrating freestyle-opscenter through RPC, the Should any of the advantages offered by the A more detailed comparison between |
* Add a microservices information fetching method, deserializing a meesaged based on the proto associated with that endpoint. * Consume that service on the app main component. * Set an environment variable that points to that microservices and nodes discovery information. This closes #13.
* Add a microservices information fetching method, deserializing a meesaged based on the proto associated with that endpoint. * Consume that service on the app main component. * Set an environment variable that points to that microservices and nodes discovery information. This closes #13.
We need to create a service to get to know which network structure is available to the client to get information from. This would eventually be an endpoint where we connect to get a tree of all the possibles microservices and nodes to show, and then select a specific one to start consuming metrics.
The text was updated successfully, but these errors were encountered: