master: 
Usage store is intended to be a data store to track the lifetime of specific resource types. The database structure is basically an entry list of different timeframes where the specific entity was up and running.
Even you can interact as usual with this store through its endpoints
usage.get
usage.del
usage.set
usage.find
the database population is done by listening at events happening on Ernest nats network. Usage store is listening at this events
Creates a new entry for the specific instance starting at the current time
Closes an existing entry
Depending on the field powered [true|false] it will execute the same logic on the previous two, in case powered is not set it will skip any process.
make deps
make install
This repository has integration tests described here, they will be compiled on the repo linked CI. If you want to run them locally, follow instructions described on ernest repo
Please read through our contributing guidelines. Included are directions for opening issues, coding standards, and notes on development.
Moreover, if your pull request contains patches or features, you must include relevant unit tests.
For transparency into our release cycle and in striving to maintain backward compatibility, this project is maintained under the Semantic Versioning guidelines.
Code and documentation copyright since 2015 ernest.io authors.
Code released under the Mozilla Public License Version 2.0.