Re: Billing & Metering of app usage with Abacus
Piotr Przybylski <piotrp@...>
Hi, I am also looking at runtime submissions for Abacus, worked on it for
Bluemix, couple of points for discussion.
In addition to usage events (start followed by stop), the scaling and
duplicate events need to be handled. The former is a START followed by
START with memory or instance count changed, the latter can be STOP
followed by STOP.
We also encountered a situation where the ordering is correct - START
followed by STOP but the timestamp for the START is later than STOP.
For the running applications - your points #2 and #3 are a working though
it may generate fair amount of traffic, depending on frequency and number
of running applications. Eventually we may want to look at alternatives,
for example enhance metering to allow for time based submissions. Instead
of continually submitting usage, submit the state of application -
(STARTED, memory, instances), the metering could then calculate usage for
that application based on the time passed until application is stopped.
I think handling some of above scenarios requires persistence, even if to
log CF events that were used for submission (or skipped). You may want to
persist state to recovery from application failure or restart, as well as
keep track of running/active applications.
Hristo Iliev <hsiliev(a)gmail.com> wrote on 08/07/2015 08:07:53 AM:
We want to integrate the metrics provided by Cloud Foundry with Abacus.
We plan to create a billing/metering integration layer that:
AFAIK Abacus provides usage reports for the current month only and
The second issue might be solved by reporting small amounts ofusages:
start: 1438945112; end: 1438946000 (current time for the billingintegration)
start: 1438946000 (previous reporting cycle); end: 1438947000
Reporting usage in small steps might require persistence so we cancache.
Is such integration in the scope of Abacus project?