With Skupper 1.3, a new console is available which allows you to monitor flows across your network.
This console requires a process that is not enabled by default (--enable-flow-collector to enable)
- This is a feature preview and not suitable for deployment in production. The Skupper team are working hard to simplify and improve the experience, expect changes over the next few releases.
To activate the new console, you should skupper init --enable-console --enable-flow-collector on one site only to avoid unnecessary resource usage. The single flow collector has access to data from all connected sites.
To determine the location of the flow collector/console, consider:
- Where are most events located? It might reduce traffic to locate the flow collection on that site.
- Where should the console be accessed from? If you use Skupper to span a DMZ or firewall, you might want to consider where the console users are located.
- Where are the cheapest resources? It might suit you to locate the flow collector and console in the location where resources are cheapest.
The new console provides insights into your exposed services. For example, this screenshot shows individual POSTs from frontend to cartservice, with details about duration, latency, and server instances that can help you better understand your service topology.
NOTE: By default, the console is disabled when you create a new site with Skupper 1.3.
Skupper update will enable flow collector (associated with the new console) if the console was previously enabled.
- This can increase memory usage considerably.
- To avoid issues, recreate the site.