Add Objects Command

The Logging service supports a single Add Objects command to add new data. Since data is immutable, existing objects cannot be modified. Objects are automatically deleted when table-level data aging is requested. A batch of new objects is added to a specific table using the following REST command:

POST /{application}/{table}

where {application} is the application name and {table} is the table in which the objects are to be added. The command must include an input entity that contains the objects to be added. An example input message in JSON is shown below:

{"batch": {

"docs": [

{"doc": {

"Timestamp": "2015-03-24 14:05:42.893",

"Level": "INFO",

"Module": "MBeanProvider",

"Message": "Unregistering the ServerManager MXBean”

}},

{"doc": {

"Timestamp": "2015-03-24 14:05:43.403",

"Level": "INFO",

"Module": "MBeanProvider",

"Message": "Unregistering the StorageManager MXBean”

}},

...

]

}}

Notes about adding batches are described below:

•	Only the Timestamp field is required, which contains the object’s timestamp. This value determines how the object is stored and accessed during queries.

•	Objects do not need to be added in time order, and multiple objects can have the same Timestamp value.

•	Logging service objects do not use object IDs, so the _ID field should not be set.

•	Each field name must start with a letter and contain only letters, digits, or underscores.

•	Field values should be simple scalar values: text, numbers, timestamps, etc.

•	Updates are more efficient when objects are loaded in batches. However, small batches can be added and are merged into larger batches by a background task.

If the update request is successful, a 201 Created response is returned with a simple status result message. Example:

{"batch-result": {

"status": "OK"

}}