Great work, everyone!

Do you see the same behavior on a local system? wrote:

When you say the firewall timeouts have been disabled, do you mean TCP timeouts or something else? Do you see the same behavior on a local system? wrote:

there are two problems: 1) certain load balancer versions and configurations have unexpected behavior around tcp timestamps when there is a mix of windows and non-windows clients (really a mix of time

zongwei, i think we are mixing problem and solution here. let's get very clear on exactly the desired user experience before jumping to what components need to change. if the data model remained the s

what specifically did you try and what specifically didn't they like? the more information you provide around your request the more productive the discussion will be. wrote:

zongwei, if they could define multi-org quotas rather than requiring a hierarchical org structure would that meet their needs? b wrote:

zongwei, could you give more detail on the problem you are hoping to solve? multi-level orgs is a solution, but i want to make sure there is clarity on the problem so we can discuss what other solutio

johannes, the problem of upstream schema changes causing downstream change or breakage is the current situation: every addition of a metric type implies a change to the dropsonde-protocol requiring ev

great questions, dwayne. 1) the partition key is intended to be used in a similar manner to partitioners in distributed systems like cassandra or kafka. the specific behavior i would like to make part

All, The existing dropsonde protocol uses a different message type for each event type. HttpStart, HttpStop, ContainerMetrics, and so on are all distinct types in the protocol definition. This require

ETags and a 304 response are specifically intended for that purpose. I'd recommend that over relying on Last-Modified. b wrote:

matt, could you elaborate a bit on what you believe ssh access to instances is for? b wrote:

yes, this is how it should work.

Stephan, That's a lot of skew for ntp synchronized systems. I would expect them to differ by less than a second. The problem you are having could be a result. b wrote:

Stephan, Have you verified the clocks are in sync, perhaps using ntp, across all the systems involved? b wrote: