Commit Graph

30 Commits

Author SHA1 Message Date
Alfonso Acosta
ebefa5e8f0 Use label "com.amazonaws.ecs.container-name" to render container names 2015-09-07 20:52:13 +00:00
Tom Wilkie
303e11be6a Don't send numeric=true for connections table. 2015-09-07 13:06:13 +00:00
Tom Wilkie
d09a853fb2 Show container image details for containers. 2015-09-03 10:26:13 +00:00
Tom Wilkie
1f6b3d4a45 Move Adjacency info inside the NodeMetadata struct; move pseudo node generation to the probes. 2015-08-28 15:20:27 +00:00
Alfonso Acosta
e1c05012ca Report docker container labels and render them in the details pane 2015-08-26 13:38:53 +00:00
Alfonso Acosta
d1126f911b Desambiguate Container associated to processes in details pane 2015-08-24 21:13:27 +00:00
Alfonso Acosta
807b30bfe3 Figure out whether to show host tags in details pane from context 2015-08-24 18:40:24 +00:00
Alfonso Acosta
75595a5519 Add useful information to table titles in details pane
Title modifications:
* "Origin Process" -> "Process \"name\" (pid)"
* "Origin Container" -> "Container \"name\" (pid)"
* "Origin Host" -> "Host \"name\""
* "Origin Container Image" -> "Container Image \"name\""
2015-08-21 16:37:12 +00:00
Alfonso Acosta
10199737e4 Add host context in the details pane
In situations when the details can refer to entities from multiple hosts
(e.g. container image) make explicit to what host we are referring to.
2015-08-21 15:19:30 +00:00
Alfonso Acosta
37307c26b9 Merge 'Connections' and 'Connection Details' in node details pane
* Now the Connections table appears at the end of the pane

* Connection details are expandable (still not implemented in the UI but backwards
compatible).
2015-08-21 10:11:39 +00:00
Alfonso Acosta
c78f9d812c Add Expandable attribute to detailed-pane rows 2015-08-20 15:26:23 +00:00
Tom Wilkie
6f1f453098 Review feedback 2015-08-19 12:22:28 +00:00
Tom Wilkie
7fb1a98eca Update detail node logic to deal with connection directionality; also correctly merge edge metadata for pseudo nodes. 2015-08-19 10:21:01 +00:00
Tom Wilkie
60d1b503c1 Deal with directed edges in the rest of the codebase. 2015-08-19 10:17:31 +00:00
Tom Wilkie
0cc3dd0eea Merge pull request #367 from weaveworks/323-origin-address
Condense origin address entries into a single table.
2015-08-19 11:16:00 +01:00
Peter Bourgon
a1b0088bf3 Remove (comm) from Name field in detail pane 2015-08-19 11:07:31 +02:00
Tom Wilkie
4efa811ef8 Add test. 2015-08-18 12:16:42 +00:00
Peter Bourgon
0dafad763f Calculate rates in detailed nodes 2015-08-03 16:04:06 +02:00
Peter Bourgon
e1f7752a34 Split PacketCount to Egress and Ingress
Also, 1 packet may be counted in N topologies, so you can't rely on the
sum of all packet counts across topologies having any relation to the
sampling data.
2015-08-03 14:58:41 +02:00
Peter Bourgon
0aadf6447b Revert to correct edge construction
Another implicit invariant in the data model is that edges are always of the
form (local -> remote). That is, the source of an edge must always be a node
that originates from within Scope's domain of visibility. This was evident by
the presence of ingress and egress fields in edge/aggregate metadata.

When building the sniffer, I accidentally and incorrectly violated this
invariant, by constructing distinct edges for (local -> remote) and (remote ->
local), and collapsing ingress and egress byte counts to a single scalar. I
experienced a variety of subtle undefined behavior as a result. See #339.

This change reverts to the old, correct methodology. Consequently the sniffer
needs to be able to find out which side of the sniffed packet is local v.
remote, and to do that it needs access to local networks. I moved the
discovery from the probe/host package into probe/main.go.

As part of that work I discovered that package report also maintains its own,
independent "cache" of local networks. Except it contains only the (optional)
Docker bridge network, if it's been populated by the probe, and it's only used
by the report.Make{Endpoint,Address}NodeID constructors to scope local
addresses. Normally, scoping happens during rendering, and only for pseudo
nodes -- see current LeafMap Render localNetworks. This is pretty convoluted
and should be either be made consistent or heavily commented.
2015-08-03 10:55:59 +02:00
Peter Bourgon
b9afa67ad6 gopacket-based traffic sniffing 2015-08-03 10:55:59 +02:00
Paul Bellamy
cd71f82d4d aggregate connection details table
List Local and Remote endpoints for each TCP connection on the node.
2015-07-02 14:21:16 +01:00
Tom Wilkie
416f56c3cc Only have a single report fixture
- Move render.Rpt to test.Report
- Remove report/report_fixture_test.go; it was unused
- Remove report fixture in app/ and make tests use test.Report
- Move expected outputs into render/expected, so they can be reused
2015-06-24 09:51:29 +00:00
Tom Wilkie
93cf639418 Fix order of tables in details panel to go from most to least granular. 2015-06-23 15:09:20 +00:00
Tom Wilkie
c793e86d5b Expose some more information on containers. 2015-06-19 13:02:07 +00:00
Tom Wilkie
49dae07cca Make render module produce The Internet pseudo node. 2015-06-19 11:09:52 +00:00
Tom Wilkie
25ca0c0eb7 Add ContainerImage topology and use it to build the Container By Image graph.
This makes container image details show the containers (and processes) correctly.

Also:
- introduces a 'test' package, moved Diff function there.
- adds some tests for this new rendered view.
2015-06-18 09:16:20 +00:00
Tom Wilkie
7e021baf3b Add test for MakeDetailedNode. 2015-06-17 17:23:30 +00:00
Tom Wilkie
3de721bb16 Make topologies_test.go pass. 2015-06-17 17:23:24 +00:00
Tom Wilkie
2a4a33f30a Move RenderableNode and DetailedNode into render/ 2015-06-16 15:37:08 +00:00