-
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
Visualization Service #6
Comments
Highly linked with "Visualization Interface". Need to coordinate tasks |
Νομίζω πρέπει να αποφασίσουμε στο πως θα γίνεται η αποθήκευση απο το Visualization Service και ύστερα η λήψη των εικόνων απο το Visualization Interface (DIASTEMA-UPRC/web-application#31) I see two scenarios:
Food for thought |
Update: Κάνω μια πρόταση για το πως θα μπορούσαμε να δομήσουμε τα 3 services ώστε να παίζουν μεταξύ τους:
@konvoulgaris @karamolegkos ρίξτε του μια ματιά στον χρόνο σας και το συζητάμε. |
Ξαναχρησιμοποιούμε πλέων το παρακάτω node με τα εξής χαρακτηριστικά:
Παρακάτω ένα Flow ενός παραδειγματικού Use Case:
Αν χρειάζεται παραπάνω πληροφορία ο @karamolegkos θα επικοινωνήσει με τον @konvoulgaris.
Κατά την ολοκλήρωση της εφαρμογής στο μέλλον θα τοποθετούνται και metrics (we need more reasearh for that) με τον παρακάτω τρόπο στο ίδιο document:
|
@konvoulgaris waiting for confirmation |
yeah this generally sounds good, im playing around with a library to automatically determine best chart for data. ill be back as soon as i have more info to share |
Workflow has been updated for the Web App and Orchestrator connectivity. |
Autoviz routing finally complete! Moving on to specification synchronicity... |
Needs to be deployed. |
After a lot of debugging this is working. |
It is working good. I suggest to close this issue ✔️. |
Remains open until Spark is integrated. |
Spark Integrated ✔️. |
This issue reffers to the Visualization Service, that is generating images for the Web Application.
This issue is linked with: #3
Bottlenecked by: #4 - We need to know the way that this service can extract information by Prometheus.
The text was updated successfully, but these errors were encountered: