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
Transfer Monitoring #359
Comments
Hi @fno2010. Following your comment #301 (comment) Can you please elaborate on the need to add the type for the request? Are you intending to stream all requests and then compute statistics in javascript? |
@rcarpa, I think streaming original requests directly is the easiest way. Just like the current web-ui does for DIDs, RSEs, and Rules. But we don't need to stream all requests. I think we can query the subset of requests on demand, e.g., filtered by request_type, request_state, account, etc. Is there any privacy issue? |
I'm thinking more about the performance issues. The "normal" size of the requests table is a couple million rows. It frequently grows even bigger. I think it's wiser to rely on aggregated statistics which is computed (and, most probably, cached) on server side. |
Ah, good point. What is the scale of the active requests ( |
The order of magnitude between rucio and fts is the same. Considering the visualisation, did you already have an idea in mind on how to represent it ? After speaking with the Operations team, I'm pretty sure that showing the data on a World map is a bad idea. Because of the high density of RSEs in some areas and low density in others. I didn't think it through very much, but something like a |
@rcarpa Sorry about missing your follow-up discussions. As a starting point, I would like to finish the table view first. But I do think about some potential graph views. I agree with you that the RSE-level topology is highly dense. The RSEs from the same organization usually have close geolocations on a world map. I think we can add a group-level topology as an overlay of the RSE-level topology. The group can be based on the site (from the CRIC database), country, or some other meta attributes. The group can be folded/unfolded. Several years ago, we used cisco's next library to realize this effect. Like this demo. But it seems that the next library has no longer been maintained. I see G6 has a similar feature. Maybe cytoscape.js can do a similar thing. I will investigate a little bit. |
Since we discussed the selection of third-party libraries for graph-based visualization, I just investigate a little bit the activity, maintenance, popularity, and performance of some top graph libraries. Although I'm using G6 right now, the front-end development is still in the early stage. Changing the library will not be very painful.
|
@fno2010 thanks for the research. The final option (graphology) seems like the safest bet. I believe that implies using sigma.js in conjunction, which is okay too. |
@maany Thanks for sharing the opinion. I'm not a safety expert. Just wonder how to judge the safety. |
- Components: Add components for transfers and statistics display - App: Add pages for transfers and statistics - api: Add gateway, usecase, feature, controller, presenter for list-transfer-stats and list-transfers Provide E2E feature for rucio#359
- Components: Add components for transfers and statistics display - App: Add pages for transfers and statistics - api: Add gateway, usecase, feature, controller, presenter for list-transfer-stats and list-transfers Provide E2E feature for rucio#359
- Components: Add components for transfers and statistics display - App: Add pages for transfers and statistics - api: Add gateway, usecase, feature, controller, presenter for list-transfer-stats and list-transfers Provide E2E feature for rucio#359
- Components: Add components for transfers and statistics display - App: Add pages for transfers and statistics - api: Add gateway, usecase, feature, controller, presenter for list-transfer-stats and list-transfers Provide E2E feature for rucio#359 Compound: Add components and apis for transfer - Components: Add components for transfers and statistics display - App: Add pages for transfers and statistics - api: Add gateway, usecase, feature, controller, presenter for list-transfer-stats and list-transfers Provide E2E feature for rucio#359
- Components: Add components for transfers and statistics display - App: Add pages for transfers and statistics - api: Add gateway, usecase, feature, controller, presenter for list-transfer-stats and list-transfers Provide E2E feature for rucio#359 Compound: Add components and apis for transfer - Components: Add components for transfers and statistics display - App: Add pages for transfers and statistics - api: Add gateway, usecase, feature, controller, presenter for list-transfer-stats and list-transfers Provide E2E feature for rucio#359
Description
Discussions about the requirements for the WebUI in relation to rucio/rucio#6189
Motivation
No response
Change
No response
Additional Information
The text was updated successfully, but these errors were encountered: