search

adrianco / spigo

Simulate Protocol Interactions in Go
Apache License 2.0
1.12k stars 111 forks source link

Generate deeper hierarchy for containers and sysdig #29

Closed adrianco closed 8 years ago

adrianco commented 9 years ago

Sysdig https://github.com/draios/sysdig interfaces to Sysdig Cloud which has a zoomable service view that can show machines, vms, containers and processes https://dl.dropboxusercontent.com/u/16649518/2015-06-11-monitorama.pptx

To model this in spigo, need to expand the "service" to instance + container + process for cloud, and machine + VM + container + process for on prem models.

hubayirp commented 9 years ago

Nice find - good to add. On Wed, Jun 17, 2015 at 11:18 AM Adrian Cockcroft notifications@github.com wrote:

Sysdig https://github.com/draios/sysdig has a zoomable service view that can show machines, vms, containers and processes https://dl.dropboxusercontent.com/u/16649518/2015-06-11-monitorama.pptx

To model this in spigo, need to expand the "service" to instance + container + process for cloud, and machine + VM + container + process for on prem models.

— Reply to this email directly or view it on GitHub https://github.com/adrianco/spigo/issues/29.

adrianco commented 9 years ago

First phase done, names package now has definitions for container and process, and new MakeContainer function. Need to change architecture package next to allow containers to be specified.

adrianco commented 9 years ago

Names now extended to include container hierarchy as default, with configurable filter to hide the extra levels when not being used. All json output files have been re-generated with the new naming scheme.

hubayirp commented 9 years ago

Good it's cofigurable - CIFS will have a problem On Sun, Jun 21, 2015 at 1:23 AM Adrian Cockcroft notifications@github.com wrote:

Names now extended to include container hierarchy as default, with configurable filter to hide the extra levels when not being used. All json output files have been re-generated with the new naming scheme.

— Reply to this email directly or view it on GitHub https://github.com/adrianco/spigo/issues/29#issuecomment-113875909.

adrianco commented 9 years ago

The filter is just for what gets sent to the json file for visualization, the simulation can have as much detail as it needs for generating monitoring output for a specific tool.

adrianco commented 9 years ago

Filtering and naming is managed in names.go Filtering occurs centrally in edda.go before calling graphjson.go to log the node or edge

adrianco commented 9 years ago

architecture format updated, new simple container architecture created, build.sh and run.sh used to regenerate all the output files. Code synced.