Ets cluster view #63
Ets cluster view #63
Conversation
Create the skeleton of an OTP application.
- add the epl_ets gen_server module which provides information
about number of ets from observed node
- modify main supervisor to start and supervise epl_ets module
- start epl_ets gen_server, wait until epl app is started, then
subscribe for epl
- provide epl_json:encode/2 with correct args
- improve code style
Add subscribe/0 and unsubscribe/0 to the epl_ets module to make things easier.
Implement necessary callbacks in order to send received ets info throught websocket.
Establish websocket connection between the epl and a web browser and present basic ets information through the browser.
Provide docs and specs for paritcular modules and their public API functions.
Create new epl-ets plugin which is a clone of the existing epl-vizceral one.
Modify epl-ets ui plugin to render nodes with information about ETS count and ETS memory usage on them.
Move and export some useful functions from epl_traffic module to epl_viz_map module. It provides public API for creating and manipulating Vizceral map data structure.
- create epl_ets_viz_map module which provides API for
manipulating Vizceral map in terms of ETS data.
- modify epl_ets module to prepare proper Vizceral map.
Refactor some functions; add specs and docs.
- modify epl_viz_map module - add spec and docs - change license
- change functions calls in epl_ets module - export push_additional_node_info/2
- modify epl_ets module in order to dynamicly create Vizceral
data structure for multiple nodes
- move common functions from epl_traffic to epl_viz_map
- export common fuction from epl module
- periodically check state of the observed nodes (handle_info) - add functions for removing outdated records in Vizceral map - export needed function from epl_viz_map module - improve code style
- change vizceral configuartion in epl-ets React plugin - add additional data structure to Vizceral map - tidy ets related data in Vizceral map
Thanks to this change Traffic view and ETS view do not interfere with each other.
|
|
||
| get_ets_basic_info(Node) -> | ||
| ETSCount = get_all_ets_count(Node), | ||
| ETSMemUsage = get_ets_mem_usage(Node), |
There was a problem hiding this comment.
Maybe instead of calling erlang:memory/0 through epl_tracer:command(), change epl_tracer:handle_info() so that it collects all memory statistics.
|
@mkacper I've conected two nodes together with Why can be that? Am I doing something wrong? EDIT: They are perfectly connected within |
|
It's not related to this PR but previously we were displaying |
|
@baransu This warning is normal :) I haven't figured out yet why it is showed. What does the Here is the proper view: When it comes to displaying Thanks for your engagement! :) EDIT: Something is wrong with ets cluster view when |
|
I have 3 nodes in cluster. Every one connected with
|
|
Thanks for point the issue :) As I said in the previous comment something goes wrong when erlangpl is started from |
|
Sorry, I didn't saw your edit. |
Yes, I did. It seems to work nice :) Please try the |
Make necessary changes to make it work.
This PR introduces ETS cluster view. It appears as a new tab in the web UI. The view shows all nodes in the cluster with basic infromation about ETS tables on a particular node.