Tables

A table is a named set of objects. Table names are identifiers that must be unique within the same application. Compared to other services, the Logging service does not require nor allow fields to be explicitly defined: they are dynamically discovered as data is added. Consequently, a table definition consists only of its name and table-level options. The only option available for Logging tables is automatic data aging, which is defined via the retention-age option as shown below:

{"LogDepot": {

"options": {

"StorageService": "LoggingService"

},

"tables": {

"AppLogs": {

"options": {"retention-age": "3 MONTHS"}

}

}

}}

In this example, the AppLogs table sets its retention-age option to 3 months. Objects are automatically deleted when their Timestamp field value is older than the given age. The retention-age option must be in the form of “N <units>” where N is a positive integer and <units> is any of DAYS, MONTHS, or YEARS or the singular spelling of these mnemonics. When a table enables data aging, a background tasks periodically checks for and deletes expires objects.

When a Logging application defines multiple tables, each table can select data aging independently.