Bryan Boreham c03aeb5d43 Move Counters into Latest ...

The only place Counters are used is in rendering, for the number of
nodes under a topology, so the overhead of holding a unique data
structure in every Node is unwarranted.

Counters are not set in the probe, so we don't need any
backwards-compatibility in report decoding. Similarly they are not set
until after all nodes are merged, so we don't need that logic.

2020-03-10 12:30:05 +00:00

..

censor_test.go

Added some tests for censoring.

2019-02-23 19:30:42 +01:00

censor.go

Added some tests for censoring.

2019-02-23 19:30:42 +01:00

connections.go

ui: include skipped connection count in rendering

2020-01-13 08:53:47 +00:00

links_test.go

Rename :orgId to :instanceId in metrics graph url

2018-12-17 17:57:00 -08:00

links.go

Service metrics: fix naming assumption

2018-02-08 14:13:50 +00:00

node_test.go

Stop render package depending on probe

2019-09-15 17:03:04 +00:00

node.go

performance: Send active controls as a single string per node

2019-11-26 11:29:42 +00:00

parents_test.go

Add more Opentracing detail to the app (#3383)

2018-10-26 11:21:33 +05:30

parents.go

refactor: lift some code out of inner loop

2017-12-27 13:54:30 +00:00

summary_test.go

Stop render package depending on probe

2019-09-15 17:03:04 +00:00

summary.go

Move Counters into Latest

2020-03-10 12:30:05 +00:00

topology_diff_test.go

refactor: extract BasicNodeSummary

2017-12-27 13:54:30 +00:00

topology_diff.go

Reset nodes in frontend when scope-app restarted

2017-07-13 14:28:17 +02:00