Commit Graph
619 Commits
Author SHA1 Message Date
Alfonso Acosta fc4eb85de2 More feedback 2016-11-03 22:27:46 +00:00
Alfonso Acosta b30a9c44b6 Review feedback (and fix metadata bug) 2016-11-03 21:58:54 +00:00
Alfonso Acosta 0884955c95 Extend metadata in details panel for Weave Net nodes 2016-11-03 15:57:23 +00:00
Simon 7e5166e45e Merge pull request #1966 from weaveworks/746-resize-ttys
Resize TTYs
2016-11-03 11:06:16 +01:00
Alfonso Acosta 3af7076f30 Review feedback 2016-11-02 14:46:56 +00:00
Alfonso Acosta 9e378ca4b5 Show image information at the beginning 2016-11-02 13:16:12 +00:00
Alfonso Acosta 216cc0d605 Add image table to container nodes
Also, extend metadata of images with sizes
2016-11-02 13:16:11 +00:00
Alfonso Acosta 9367d95cb0 Allow providing fixed entries in tables 2016-11-02 13:00:15 +00:00
Alfonso Acosta 1cf66419d9 Make linter happy 2016-10-31 14:26:37 +00:00
Alfonso Acosta 253657887c Implement TTY resize for hosts 2016-10-31 12:11:25 +00:00
Alfonso Acosta 6a3910d20a Fix backend tests 2016-10-31 10:15:50 +00:00
Alfonso Acosta 411f8d729e Remove leftover functions 2016-10-31 11:04:41 +01:00
Alfonso Acosta 2443f7a3c5 Implement resize control for docker TTYs 2016-10-31 11:04:40 +01:00
Alfonso Acosta c2f2a90b61 Implement App endpoint /pipe/{id}/resize_tty/{height}/{width} to resize ttys 2016-10-31 11:04:39 +01:00
Alfonso Acosta b458c4c0c8 Merge pull request #1182 from weaveworks/1132-weave-topology
Add the basics for a Weave-specific topology.
2016-10-28 12:23:55 +02:00
Alfonso Acosta f906511ded Add initial metadata in details panel and clarification comments 2016-10-26 09:09:01 +00:00
Jordan Pellizzari 590f0078e7 Merge pull request #1927 from jpellizzari/1866-table-time-format
1866: Improve metadata table 'date' format
2016-10-25 14:31:27 -07:00
Alfonso Acosta e80a01aab9 Filter out docker overlay peers 2016-10-24 17:37:53 +00:00
Jordan Pellizzari 26a1d20f0d Added formatted date strings to table and detail metadata values 2016-10-24 09:22:59 -07:00
Alfonso Acosta 8e4dfd7987 Add Weave peers view 2016-10-24 15:33:30 +00:00
Alfonso Acosta 9881a6b631 Fix tests 2016-10-24 09:41:53 +00:00
Alfonso Acosta 529759b603 Discard short-lived connections to/from Pods in the host net 2016-10-21 14:42:44 +00:00
Alfonso Acosta 43f4da0ecc Fix tests 2016-10-18 17:26:45 +00:00
Alfonso Acosta bd3ececb11 Increase timestamp precision 2016-10-18 15:24:37 +00:00
Paul Bellamy 002770d394 use hashicorp/clean-http to get better http client defaults 2016-10-13 09:45:27 +01:00
Paul Bellamy 28213a00a4 Add timeouts to the probe http client 2016-10-12 17:20:47 +01:00
Tom Wilkie 2a00fd2d78 Allow user to specify URLs on the command line, and use that to allow per-target tokens. (#1901)
Also:
- Parse targets on startup and catch badly formed ones before Scope can start.
- If no port is specified, use default port for scheme; if no scheme is specificed, use 4040.
- Use username as probe token
2016-10-05 10:59:56 -07:00
Simon Howe 0774496102 Remove ContainerImage.imageID in the details panel
It will be re-introduced later as imageIDs
2016-09-28 16:17:14 +02:00
Alfonso Acosta 6ed79a7427 Merge pull request #1897 from weaveworks/stricter-dns-over-tcp-snooping
Be more strict when snooping DNS over TCP traffic
2016-09-27 21:12:35 +02:00
Alfonso Acosta 45a9367d97 Be more strict when snooping DNS over TCP traffic 2016-09-27 12:48:25 +00:00
Tom Wilkie b130f1ba13 Allow users to specify conntrack buffer size. (#1896)
* Allow users to specify conntrack buffer size.

* Fix tests.

* Use a config struct.
2016-09-26 12:08:38 -07:00
Alfonso Acosta 326208c395 Skip DNS length field (only included over TCP) 2016-09-23 13:57:39 +00:00
Alfonso Acosta 6f95d05c59 Add support for snooping DNS over TCP 2016-09-23 12:41:32 +00:00
Alfonso Acosta c5ac315b38 Review feedback 2016-09-20 16:50:29 +00:00
Alfonso Acosta f5ad6a8e97 Minor fixes/refinements 2016-09-19 14:38:59 +00:00
Alfonso Acosta 028ed32b6f Simplify service node matching 2016-09-19 14:38:59 +00:00
Alfonso Acosta 0223b0b385 Implement DNS snooper 2016-09-19 14:38:59 +00:00
Matthias Radestock 9d010fabc8 refactor: extract makeEndpointNode helper 2016-09-02 21:12:23 +01:00
Matthias Radestock 5bc3a9d5ac correctly reverse-resolve source of inbound connections
There were two problems:
- the renderer was looking for reverse names on the destination
- the probe was not annotating source nodes with reverse-resolved names

Fixes #1847
2016-09-02 20:31:03 +01:00
Matthias Radestock 3ebe4a5303 cosmetic: formatting 2016-09-02 08:19:32 +01:00
Alfonso Acosta 7702905bbf Remove unused variable 2016-08-26 14:03:29 +00:00
Alfonso Acosta a904620908 Improve conntrack kernel-support detection for in-kernel compilations 2016-08-26 14:03:29 +00:00
Matthias Radestock fa784140a4 appease linter 2016-08-26 14:50:45 +01:00
Matthias Radestock a5b491dd46 Merge pull request #1833 from weaveworks/simplify-container-stats
use go-dockerclient's Client.Stats

Fixes #1799
2016-08-26 13:07:16 +01:00
Matthias Radestock 3c4833fe97 use go-dockerclient's Client.Stats
...instead of rolling our own.

This also fixes #1799 - a race condition that could result in multiple
stats gatherers for a container.
2016-08-26 12:43:30 +01:00
Alfonso Acosta 7c2e3c87d3 Merge pull request #1832 from weaveworks/1824-wrong-pod-parents
Only consider pod parents living in the same namespace
2016-08-26 11:37:28 +01:00
Matthias Radestock af48c7f240 Merge pull request #1830 from weaveworks/1664-correct-cpu-metrics
correct cpu metrics

Fixes #1664.
2016-08-26 11:18:56 +01:00
Alfonso Acosta 8a7812eab9 Only consider pod parents living in the same namespace 2016-08-25 16:05:01 +00:00
Matthias Radestock e2a80cfa14 correct host cpu metric
The host CPU metric was reported as a percentage of all available CPUs,
but the limit was set to n_cpus * 100%. So on a 4-core machine the
graphs and metrics-on-canvas would never show more than 1/4th usage. Now
the limit is set to 100%.

Fixes #1664.
2016-08-25 16:14:42 +01:00
Matthias Radestock b209d22e08 normalise container CPU metrics to 100%
The container CPU metric was reported in units of 100% = 1 CPU. So the
the ratio was correct, but since we don't show limits in most places it
is hard to interpret that figure. It also makes sorting by CPU usage
highly misleading. So now we normalise everything to 100%. That too can
be misleading, depending on what you are looking for, but it's generally
less surprising.
2016-08-25 16:13:36 +01:00