You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Jun 20, 2024. It is now read-only.
A visual representation of the network would be valuable to ops and dev folks alike. It could be laced with stats, such as traffic and uptimes.
There are actually three types of network here:
The weave network. Weave peers and the connections between them.
The application network. Containers, their MACs, IPs, peer association and communication between them.
The DNS network. WeaveDNS servers, the traffic between them and to external servers.
The information should be exposed through APIs, and the visualiser component itself ought to be a separate component. Eventually we may also want to add monitoring/alerts, which would be a separate component itself.
This issue is an umbrella; it needs to be split up into smaller pieces. #359 is a starting point for APIs. #353 and #430 cover extra metrics.
The text was updated successfully, but these errors were encountered:
A visual representation of the network would be valuable to ops and dev folks alike. It could be laced with stats, such as traffic and uptimes.
There are actually three types of network here:
The information should be exposed through APIs, and the visualiser component itself ought to be a separate component. Eventually we may also want to add monitoring/alerts, which would be a separate component itself.
This issue is an umbrella; it needs to be split up into smaller pieces.
#359 is a starting point for APIs. #353 and #430 cover extra metrics.
The text was updated successfully, but these errors were encountered: