Rajkiran Ramachandran Balasubramanian

@hsiliev The inconsistency will result in incorrectly aggregated values. The side effects depend on the resource. Let's say the accumulator posted an accumulated document, for a runtime event, to the...

How about we create two endpoints in the 3 end points in the provisioning plugin 1 Provision an instance > METHOD: POST > PATH: /v1/provisioning/resource_instances/:org_id/:space_id/:resource_id/:resource_instance_id/:time 2 Report activity on an...

How about having view on every database which can have indexes based on resource instance ids / resource / organizations. For example the collector input and output log database can...

@jmcarp In the current implementation of abacus, the time windows are fixed and do not change. The structure seems to be complicated but it's simply a two-dimensional matrix. The time...

@KRuelY The problem with that approach is there is no consistent 409 error messages. I have seen ``` { 'status' : 409 , 'noretry': true, 'nobreaker' : true }, ```...

If I remember correctly, @betafood was saying that it was to consider the maximum days for a slack window. @hsiliev Can you point me to the code ?

@mxxPark Can you share me the link from where you got schema A. Schema B is valid.

In addition to this we can also specify the minimum window level from which accumulation/aggregation should happen. If we set the level to 'D', then the accumulation/aggregation happens for day,...